Skip to content
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

Add support for OpenShift management workload partitioning #61

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

andreaskaris
Copy link

@andreaskaris andreaskaris commented May 7, 2024

Add annotations for OpenShift management workload partitioning. The feature is opt-in. Administrators can opt into the feature by annotating the namespace with workload.openshift.io/allowed: management. Otherwise, these annotations will have no effect.

For further details, see:

In earlier versions of OpenShift (notably 4.14), management workload partitioning does not support pods with both limits and requests set: https://github.com/openshift/kubernetes/blob/fd36fb9acf9a99270f4fca3f5817fd52c8bc58b4/openshift-kube-apiserver/admission/autoscaling/managementcpusoverride/admission.go#L258
This only changed very recently (for not yet released OpenShift 4.16) with: openshift/kubernetes#1902
Therefore, when running on these older versions, the operator pod itself will still be skipped for management workload partitioning:

     workload.openshift.io/warning: skip pod CPUs requests modifications because
        pod container has both CPU limit and request

Implements: #62

@andreaskaris andreaskaris marked this pull request as draft May 7, 2024 10:48
Add annotations for OpenShift management workload partitioning.
Administrators can opt into the feature by annotating the namespace
with workload.openshift.io/allowed: management. Otherwise, these
annotations will have no effect.

Signed-off-by: Andreas Karis <ak.karis@gmail.com>
@andreaskaris andreaskaris force-pushed the management-workload-partitioning branch from 1ccb60f to 3084403 Compare May 7, 2024 18:25
@andreaskaris andreaskaris marked this pull request as ready for review May 7, 2024 18:26
@andreaskaris andreaskaris reopened this Jun 4, 2024
@andreaskaris
Copy link
Author

@MouliBurla can you check if this is something that would make sense? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant