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

[release-4.15] OCPBUGS-33875: Use kubelet-ca.crt from ControllerConfig when certs rotate #2175

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #2167

/assign sebsoto

/cherrypick release-4.14 release-4.13 release-4.12

This commit changes how WMCO determines the expected state of the
kubelet-ca.crt file on Windows nodes.

The previous functionality had WMCO using the kubelet-ca.crt file
present in the worker MachineConfig as the initial state. When WMCO
reconciles the ConfigMap containing the
kube-apiserver-to-kubelet-client-ca, WMCO would then replace the
kubelet-ca.crt file with a combination of the clusters initial
kube-apiserver-to-kubelet-client-ca and the latest version.

With this commit, when the CA is changed in the cluster, WMCO will
instead look at the machine-config-controller ControllerConfig for the
new version of the kubelet-ca.crt. This way WMCO is consistent in
how it is sourcing the expected state with Linux Nodes, as the
Machine Config Daemon does the same. This stops WMCO from repeating work
that is already being done, and also ensures that we are including any
other certs that should be present within kubelet-ca.crt.
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-22237 has been cloned as Jira Issue OCPBUGS-33875. Will retitle bug to link to clone.
/retitle [release-4.15] OCPBUGS-33875: Use kubelet-ca.crt from ControllerConfig when certs rotate

In response to this:

This is an automated cherry-pick of #2167

/assign sebsoto

/cherrypick release-4.14 release-4.13 release-4.12

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 openshift-ci bot changed the title [release-4.15] OCPBUGS-22237: Use kubelet-ca.crt from ControllerConfig when certs rotate [release-4.15] OCPBUGS-33875: Use kubelet-ca.crt from ControllerConfig when certs rotate May 17, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 17, 2024
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-33875, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
  • expected dependent Jira Issue OCPBUGS-22237 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #2167

/assign sebsoto

/cherrypick release-4.14 release-4.13 release-4.12

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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label May 17, 2024
@mtnbikenc
Copy link
Member

/jira refresh

@openshift-ci-robot
Copy link

@mtnbikenc: This pull request references Jira Issue OCPBUGS-33875, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

@sebsoto
Copy link
Contributor

sebsoto commented May 28, 2024

/jira refresh

@openshift-ci-robot
Copy link

@sebsoto: This pull request references Jira Issue OCPBUGS-33875, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

@sebsoto
Copy link
Contributor

sebsoto commented May 28, 2024

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 28, 2024
@openshift-ci-robot
Copy link

@sebsoto: This pull request references Jira Issue OCPBUGS-33875, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.z) matches configured target version for branch (4.15.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-22237 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-22237 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
  • bug has dependents

Requesting review from QA contact:
/cc @rrasouli

In response to this:

/jira refresh

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.

@sebsoto
Copy link
Contributor

sebsoto commented May 28, 2024

/test remaining-required

@openshift-ci openshift-ci bot requested a review from rrasouli May 28, 2024 12:49
@sebsoto
Copy link
Contributor

sebsoto commented May 29, 2024

/approve

@sebsoto
Copy link
Contributor

sebsoto commented May 29, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 29, 2024
Copy link
Contributor

openshift-ci bot commented May 29, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, sebsoto

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

The pull request process is described 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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 29, 2024
@sebsoto
Copy link
Contributor

sebsoto commented May 29, 2024

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD a5da9a0 and 2 for PR HEAD 5d03dea in total

@sebsoto
Copy link
Contributor

sebsoto commented May 30, 2024

/retest-required

1 similar comment
@sebsoto
Copy link
Contributor

sebsoto commented Jun 4, 2024

/retest-required

Copy link
Contributor

openshift-ci bot commented Jun 4, 2024

@openshift-cherrypick-robot: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit 09c3894 into openshift:release-4.15 Jun 4, 2024
17 checks passed
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-33875: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-33875 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #2167

/assign sebsoto

/cherrypick release-4.14 release-4.13 release-4.12

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants