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

Labeling the Controle plane nodes before start applying addons and Helm releases #3544

Merged
merged 1 commit into from
Jan 30, 2025

Conversation

mohamed-rafraf
Copy link
Member

@mohamed-rafraf mohamed-rafraf commented Jan 29, 2025

What this PR does / why we need it:
Kube-OVN, as the CNI, requires specific node labels, but these labels are applied only after CCM ensures the nodes. However, CCM isn’t deployed because the CNI is unhealthy, creating a deadlock.

To resolve this, we label control-plane nodes before applying addons and Helm releases, ensuring a smooth bootstrap process. 🚀
Which issue(s) this PR fixes:

Fixes #

What type of PR is this?

/kind bug

Special notes for your reviewer:

Does this PR introduce a user-facing change? Then add your Release Note here:

Label the control plane nodes before applying addons and Helm charts to allow addons and Helm charts to utilize the label selectors

Documentation:

NONE

@kubermatic-bot kubermatic-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/bug Categorizes issue or PR as related to a bug. docs/none Denotes a PR that doesn't need documentation (changes). do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. labels Jan 29, 2025
@kubermatic-bot
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@mohamed-rafraf mohamed-rafraf marked this pull request as ready for review January 29, 2025 14:21
@kubermatic-bot kubermatic-bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Jan 29, 2025
@mohamed-rafraf
Copy link
Member Author

/assign

@xmudrii
Copy link
Member

xmudrii commented Jan 30, 2025

/release-note-edit

Label the control plane nodes before applying addons and Helm charts to allow addons and Helm charts to utilize the label selectors

Copy link
Member

@xmudrii xmudrii left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label Jan 30, 2025
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 39551dcc5786822f9cf2e80662148b30439c5d73

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xmudrii

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

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 30, 2025
@xmudrii
Copy link
Member

xmudrii commented Jan 30, 2025

/remove-kind bug
/kind feature

@kubermatic-bot kubermatic-bot added kind/feature Categorizes issue or PR as related to a new feature. and removed kind/bug Categorizes issue or PR as related to a bug. labels Jan 30, 2025
@xmudrii
Copy link
Member

xmudrii commented Jan 30, 2025

/retest

@kubermatic-bot kubermatic-bot merged commit fb30721 into kubermatic:main Jan 30, 2025
13 checks passed
@kubermatic-bot kubermatic-bot added this to the KubeOne 1.10 milestone Jan 30, 2025
xmudrii pushed a commit that referenced this pull request Jan 30, 2025
kubermatic-bot pushed a commit that referenced this pull request Jan 30, 2025
…branch (#3547)

* feat: add flag to skip TLS verification (#3522)

* feat: add flag to skip TLS verification

Signed-off-by: Stephan <[email protected]>

* Update addons/backups-restic/backups-restic.yaml

Co-authored-by: Artiom Diomin <[email protected]>
Signed-off-by: Stephan <[email protected]>

---------

Signed-off-by: Stephan <[email protected]>
Co-authored-by: Artiom Diomin <[email protected]>

* fix cloud config defaulting before terraform config apply (#3534)

* Make sure no slash at the end of vcenterPrefix (#3537)

Signed-off-by: Artiom Diomin <[email protected]>

* Fix kubevirt csi addon template (#3529)

* fix kubevirt csi addon template

* update internal images in template

* update internal images in template

* fix labels

* update addons

* update addons sa

* fix toleration (#3545)

* update Machine controller image (#3546)

* update Machine controller image

Signed-off-by: Mohamed Rafraf <[email protected]>

* update go.mod

---------

Signed-off-by: Mohamed Rafraf <[email protected]>

* labeling control-plane before (#3544)

---------

Signed-off-by: Stephan <[email protected]>
Signed-off-by: Artiom Diomin <[email protected]>
Signed-off-by: Mohamed Rafraf <[email protected]>
Co-authored-by: Stephan <[email protected]>
Co-authored-by: Artiom Diomin <[email protected]>
Co-authored-by: Mohamed Rafraf <[email protected]>
Co-authored-by: Artiom Diomin <[email protected]>
@xmudrii
Copy link
Member

xmudrii commented Feb 5, 2025

/cherrypick release/v1.8

@kubermatic-bot
Copy link
Contributor

@xmudrii: new pull request created: #3553

In response to this:

/cherrypick release/v1.8

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.

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. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. docs/none Denotes a PR that doesn't need documentation (changes). kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants