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

WIP UPSTREAM: <carry>: add minimumkubeletversion package #2104

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

haircommander
Copy link
Member

What type of PR is this?

/kind feature

What this PR does / why we need it:

Adds an additional admission feature that verifies all kubelets are above a certain version. WIP, TODOs inline

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?


Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Oct 4, 2024
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 4, 2024
@openshift-ci-robot
Copy link

@haircommander: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 4, 2024
Copy link

openshift-ci bot commented Oct 4, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: haircommander
Once this PR has been reviewed and has the lgtm label, please assign bertinatto for approval. For more information see the Kubernetes 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

@openshift-ci-robot
Copy link

@haircommander: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Oct 9, 2024
@openshift-ci-robot
Copy link

@haircommander: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci-robot
Copy link

@haircommander: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

Signed-off-by: Peter Hunt <pehunt@redhat.com>
@openshift-ci-robot
Copy link

@haircommander: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci-robot
Copy link

@haircommander: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

MinimumKubeletVersion is a way for an admin to declare that nodes any older than the
minimum version cannot authorize with the apiserver. This effectively prevents them from joining.

Doing so means the apiservers can trust newer features are usable on clusters with version skews

Signed-off-by: Peter Hunt <pehunt@redhat.com>
Signed-off-by: Peter Hunt <pehunt@redhat.com>
Signed-off-by: Peter Hunt <pehunt@redhat.com>
@openshift-ci-robot
Copy link

@haircommander: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

Copy link

openshift-ci bot commented Oct 19, 2024

@haircommander: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/verify-commits fc3cbb0 link true /test verify-commits
ci/prow/e2e-aws-ovn-cgroupsv2 fc3cbb0 link true /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-agnostic-ovn-cmd fc3cbb0 link false /test e2e-agnostic-ovn-cmd
ci/prow/k8s-e2e-gcp-ovn fc3cbb0 link true /test k8s-e2e-gcp-ovn
ci/prow/e2e-aws-crun-wasm fc3cbb0 link true /test e2e-aws-crun-wasm
ci/prow/integration fc3cbb0 link true /test integration
ci/prow/e2e-gcp fc3cbb0 link true /test e2e-gcp
ci/prow/e2e-aws-ovn-runc fc3cbb0 link true /test e2e-aws-ovn-runc
ci/prow/k8s-e2e-gcp-serial fc3cbb0 link true /test k8s-e2e-gcp-serial
ci/prow/e2e-aws-ovn-serial fc3cbb0 link true /test e2e-aws-ovn-serial
ci/prow/k8s-e2e-aws-ovn-serial fc3cbb0 link false /test k8s-e2e-aws-ovn-serial
ci/prow/e2e-aws-csi fc3cbb0 link false /test e2e-aws-csi
ci/prow/e2e-gcp-ovn-upgrade fc3cbb0 link true /test e2e-gcp-ovn-upgrade
ci/prow/k8s-e2e-conformance-aws fc3cbb0 link true /test k8s-e2e-conformance-aws
ci/prow/verify fc3cbb0 link true /test verify
ci/prow/e2e-aws-ovn-crun fc3cbb0 link true /test e2e-aws-ovn-crun
ci/prow/e2e-aws-ovn-fips fc3cbb0 link true /test e2e-aws-ovn-fips
ci/prow/unit fc3cbb0 link true /test unit

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/feature Categorizes issue or PR as related to a new feature. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants