-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Save entry list compressed in extension state #416
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work!
I'm excited to have this extension state compression in so that the control plane migration problem would only occur in much larger workloads.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Thank you!
How to categorize this PR?
/area control-plane
/area control-plane-migration
/kind enhancement
What this PR does / why we need it:
The
DNSEntries
of the shoot must be stored in the.status.state
of theExtension
resource for resurrection after control plane migration.If a shoot has about 2000 entries, this state becomes so big, that the request size limit of etcd (1.5MB) is hit (
etcdserver: request is too large
).To shift the maximum number of DNS entries which can be supported, the state is now compressed with the
brotli
algorithm. We expect to see compression ratios >= 6, so the limit should now be beyond 10,000 entries.Which issue(s) this PR fixes:
Fixes #413
Special notes for your reviewer:
Release note: