Skip to content

OCPBUGS-80958: Kube apiserver node replace#371

Open
bhperry wants to merge 2 commits into
openshift:masterfrom
bhperry:kube-apiserver-node-replace
Open

OCPBUGS-80958: Kube apiserver node replace#371
bhperry wants to merge 2 commits into
openshift:masterfrom
bhperry:kube-apiserver-node-replace

Conversation

@bhperry

@bhperry bhperry commented Apr 24, 2026

Copy link
Copy Markdown
Contributor

Support new NodeUID status field in NodeStatusApplyConfiguration to allow controllers to record the UID of nodes they observe.

Related PRs:

openshift/api#2821
openshift/library-go#2178
openshift/cluster-kube-apiserver-operator#2199

TODO:

  • Remove go.mod replace once the api PR merges

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 24, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@bhperry: This pull request references Jira Issue OCPBUGS-80958, which is invalid:

  • expected the bug to target the "5.0.0" version, but no target version was set

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.

Details

In response to this:

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.

@bhperry bhperry marked this pull request as draft April 24, 2026 15:55
@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 Apr 24, 2026
@openshift-ci openshift-ci Bot requested review from JoelSpeed and deads2k April 24, 2026 15:56
@openshift-ci

openshift-ci Bot commented Apr 24, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details 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

@bhperry

bhperry commented Apr 27, 2026

Copy link
Copy Markdown
Contributor Author

/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 Apr 27, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@bhperry: This pull request references Jira Issue OCPBUGS-80958, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
Details

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.

@bhperry bhperry force-pushed the kube-apiserver-node-replace branch 2 times, most recently from 784a419 to 439d308 Compare April 30, 2026 17:16
@bhperry bhperry force-pushed the kube-apiserver-node-replace branch from 439d308 to 1a282f3 Compare June 16, 2026 15:17
@bhperry bhperry force-pushed the kube-apiserver-node-replace branch 4 times, most recently from d6ed281 to b5b680e Compare July 1, 2026 17:25
@bhperry bhperry force-pushed the kube-apiserver-node-replace branch 2 times, most recently from 07f92d6 to 5f1c3f0 Compare July 8, 2026 14:58
@bhperry bhperry marked this pull request as ready for review July 8, 2026 20:56
@bhperry bhperry changed the title WIP: OCPBUGS-80958: Kube apiserver node replace OCPBUGS-80958: Kube apiserver node replace Jul 8, 2026
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 8, 2026
@openshift-ci openshift-ci Bot requested a review from bertinatto July 8, 2026 20:57
@bhperry

bhperry commented Jul 8, 2026

Copy link
Copy Markdown
Contributor Author

/hold

depends on api change

@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 Jul 8, 2026
@bhperry bhperry force-pushed the kube-apiserver-node-replace branch from 5f1c3f0 to a8b452b Compare July 9, 2026 15:16
@openshift-ci

openshift-ci Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

@bhperry: 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-deps a8b452b link true /test verify-deps
ci/prow/verify a8b452b link true /test verify

Full PR test history. Your PR dashboard.

Details

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

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants