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

OCPNODE-3029: user namespaces: add required minimum kubelet version #1766

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

Conversation

haircommander
Copy link
Member

This feature allows a feature gate author to programatically declare the minimum kubelet version that must be set to allow this feature to be turned on.

@haircommander
Copy link
Member Author

cc @JoelSpeed

@haircommander haircommander changed the title user namespaces: add required minimum kubelet version OCPNODE-3029: user namespaces: add required minimum kubelet version Mar 11, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 11, 2025

@haircommander: This pull request references OCPNODE-3029 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

This feature allows a feature gate author to programatically declare the minimum kubelet version that must be set to allow this feature to be turned on.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 11, 2025
Comment on lines 422 to 434
Then, the featuregate controller in the cluster-config-operator will be extended to filter features from the Enabled set if the minimum kubelet version isn't set old enough.
This will give openshift feature developers a mechansim to programatically declare a feature requires a certain version of the kubelet. This will be used for user namespaces,
and the corresponding version for user namespaces and related feature gates will be "1.30.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you describe what will happen when two feature gates declare different minimum versions?

How will the feature gate controller know what version it should allow?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added a blurb describing, if there are multiple versions then the feature gate controller will only filter the features that have a version higher than the defined one

Copy link
Contributor

@JoelSpeed JoelSpeed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

/hold anyone else need to review this?

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 12, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 12, 2025
@haircommander
Copy link
Member Author

I can think of @deads2k having some input. Also: @JoelSpeed you're on the list of owners of https://github.com/openshift/cluster-config-operator/blob/master/OWNERS are you the person I should annoy about reviewing those updates when they're ready? if not that person should probably also have a look

@JoelSpeed
Copy link
Contributor

David or I can approve the feature gate controller update

@haircommander
Copy link
Member Author

MCO rollback piece POC: openshift/machine-config-operator#4929

Copy link
Contributor

openshift-ci bot commented Mar 19, 2025

New changes are detected. LGTM label has been removed.

Copy link
Contributor

openshift-ci bot commented Mar 19, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from joelspeed. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link
Contributor

openshift-ci bot commented Mar 19, 2025

@haircommander: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Copy link
Contributor

@JoelSpeed JoelSpeed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Aside from finessing the API PR, I'm ok with this update, thanks

Let me know if you want me to tag this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants