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

[Helm] Update nodeSelector and tolerations #3296

Closed
wants to merge 1 commit into from

Conversation

atsai1220
Copy link
Contributor

What type of PR is this?

/kind feature

What this PR does / why we need it:

This allows the cloud-controller-manager to start on nodes with etcd taints by default. Additionally, allows configuration for additional taints if the user chooses. Currently this customization is not available at all.

Additionally allows configuration for nodeSelector. This is similar to how the cloud-provider-aws configures their Helm chart. https://github.com/kubernetes/cloud-provider-aws/blob/5db84490841ebd1eede368d03eb03c27dc556233/charts/aws-cloud-controller-manager/values.yaml#L16

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Thank you!

Does this PR introduce a user-facing change?

- Add tolerations in values for cloud-controller-manager in Helm chart
- Add nodeSelector in values for cloud-controller-manager in Helm chart

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


@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. labels Feb 7, 2023
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: atsai1220
Once this PR has been reviewed and has the lgtm label, please assign lzhecheng for approval by writing /assign @lzhecheng in a comment. 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

@netlify
Copy link

netlify bot commented Feb 7, 2023

Deploy Preview for kubernetes-sigs-cloud-provide-azure canceled.

Name Link
🔨 Latest commit 79fbf0c
🔍 Latest deploy log https://app.netlify.com/sites/kubernetes-sigs-cloud-provide-azure/deploys/63e28f9ff6e03d0009ddb5b6

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Feb 7, 2023
@k8s-ci-robot
Copy link
Contributor

Hi @atsai1220. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

@atsai1220 atsai1220 changed the title Update nodeSelector and tolerations [Helm] Update nodeSelector and tolerations Feb 7, 2023
@k8s-ci-robot k8s-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Feb 7, 2023
Copy link
Member

@andyzhangx andyzhangx left a comment

Choose a reason for hiding this comment

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

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Feb 8, 2023
@k8s-ci-robot
Copy link
Contributor

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

Test name Commit Details Required Rerun command
pull-cloud-provider-azure-check 79fbf0c link true /test pull-cloud-provider-azure-check

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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/test-infra repository. I understand the commands that are listed here.

@atsai1220
Copy link
Contributor Author

I'm not sure if I understand the failing test. The PR is adding the change for the values and templates of the Helm chart and the test seems like it's failing because there is a difference. @andyzhangx

@andyzhangx
Copy link
Member

I'm not sure if I understand the failing test. The PR is adding the change for the values and templates of the Helm chart and the test seems like it's failing because there is a difference. @andyzhangx

@lzhecheng could you help? thanks.

@feiskyer
Copy link
Member

feiskyer commented Feb 9, 2023

LGTM, but the chart validation failed. I think the validation failure means the yaml after rendering is not same as latest version under repo/.

@lzhecheng could you confirm?

@lzhecheng
Copy link
Contributor

Will check

@lzhecheng
Copy link
Contributor

I think you missed one part: Update version in helm/cloud-provider-azure/Chart.yaml. Make it something like 1.26.4+20230210 and then make update-helm.

@lzhecheng
Copy link
Contributor

Also, could you please update doc as well?

@lzhecheng
Copy link
Contributor

@atsai1220 could you please update the PR? Thanks.

@atsai1220
Copy link
Contributor Author

I'm not sure how to proceed. Could you provide some hand holding? Thank you.

@lzhecheng
Copy link
Contributor

I'm not sure how to proceed. Could you provide some hand holding? Thank you.

My suggestion is to:

  1. Rebase your PR
  2. Update the version here to something like 1.26.4+20230215:
  3. Run make update-helm
  4. Update the README doc about your changes

@lzhecheng
Copy link
Contributor

/close
@atsai1220 I have merged your commit with another PR. Thank you for the effort!

@k8s-ci-robot
Copy link
Contributor

@lzhecheng: Closed this PR.

In response to this:

/close
@atsai1220 I have merged your commit with another PR. Thank you for the effort!

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. 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.

None yet

5 participants