[release-0.24] fix(e2e): Clear stale bootstrap IP annotation in bare metal API upgrade flow#10668
Conversation
…de flow The CLI-generated config file is written before the bootstrap-to-management cluster pivot, so it retains the tinkerbell-bootstrap-ip annotation. When the test re-applies this config via kubectl apply, the annotation gets re-added to the Cluster CR, causing the controller to regenerate machine templates with the bootstrap IP instead of the tinkerbellIP. This creates a template diff that triggers unintended rollouts, blocking reconciliation.
|
Hi @eks-distro-pr-bot. Thanks for your PR. I'm waiting for a aws member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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/test-infra repository. |
eks-distro-bot
added
needs-ok-to-test
size/XS
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rahulbabu95 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
3 participants
This is an automated cherry-pick of #10651
/assign rahulbabu95