-
Notifications
You must be signed in to change notification settings - Fork 70
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
Set vttablet init container resource requests and limits #256
Set vttablet init container resource requests and limits #256
Conversation
Sets the resource requirements on each of the default vttablet init containers to the same request and limit values as the vttablet container itself. This fixes the issue reported in planetscale#212 where pods would fail to be created on clusters with strict quota requirements because no limit was set on the init containers. ## History This is a reimplementation of planetscale#216 with the change that it no longer sets a default resource _limit_. This fixes the issue reported in planetscale#240 and discussed in planetscale#244 where the vttablet pod would fail to be created when the user sets a request larger than the default limit without also setting a larger limit. The user's nil limit would not override the default value because `update.ResourceRequirements(dst, src)` won't update `dst` with a nil `src` ([for good reasons](https://github.com/planetscale/vitess-operator/blob/da7efd4c945193864f5996cb793055449c4de97a/pkg/operator/update/podspec.go#L201-L203)). With this change, users can once again increase the request by itself. If a cluster requires a limit, the user will already need to have set it on for vttablet so we can use the same value to override the init containers' default nil limit. fixes planetscale#212 fixes planetscale#240 Signed-off-by: J. Brandt Buckley <brandt@runlevel1.com>
@brandt There are others better suited for the review, but I just wanted to say THANK YOU for the contribution! It's really nice to see non-PlanetScale contributors to the operator. ❤️ |
@mattlord My pleasure! |
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.
Other than this, everything else looks good to me. Merging main might be required for running the workflows which are marked required but didn't exist when the PR was created
defaultInitCPURequestMillis = 100 | ||
defaultInitMemoryRequestBytes = 32 * (1 << 20) // 32 MiB |
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.
Default values live here https://github.com/planetscale/vitess-operator/blob/main/pkg/apis/planetscale/v2/defaults.go, and so should these.
@brandt Are you still working on this? We would like to get this change in before we do the next release. |
Closed in favour of #370 |
Sets the resource requirements on each of the default vttablet init containers to the same request and limit values as the vttablet container itself.
This fixes the issue reported in #212 where pods would fail to be created on clusters with strict quota requirements because no limit was set on the init containers.
History
This is a reimplementation of #216 with the change that it no longer sets a default resource limit.
This fixes the issue reported in #240 and discussed in #244 where the vttablet pod would fail to be created when the user sets a request larger than the default limit without also setting a larger limit. The user's nil limit would not override the default value because
update.ResourceRequirements(dst, src)
won't updatedst
with a nilsrc
(for good reasons).With this change, users can once again increase the request by itself. If a cluster requires a limit, the user will already need to have set it on for vttablet so we can use the same value to override the init containers' default nil limit.
fixes #212
fixes #240
Signed-off-by: J. Brandt Buckley brandt@runlevel1.com