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

Replace nodelocaldns label #9745

Merged
merged 1 commit into from
Feb 2, 2023

Conversation

stelucz
Copy link
Contributor

@stelucz stelucz commented Feb 1, 2023

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change

/kind bug

/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
Replace label k8s-app: nodelocaldns in DaemonSet template by k8s-app: node-local-dns. Label in template should match upstream DaemonSet definition as other projects/deployments can rely on it.

Which issue(s) this PR fixes:

Fixes #9717

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Replace nodelocaldns label to `k8s-app: node-local-dns`

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Feb 1, 2023
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Feb 1, 2023

CLA Signed

The committers listed above are authorized under a signed CLA.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Feb 1, 2023
@k8s-ci-robot
Copy link
Contributor

Welcome @stelucz!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Feb 1, 2023
@k8s-ci-robot
Copy link
Contributor

Hi @stelucz. 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.

@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Feb 1, 2023
@stelucz
Copy link
Contributor Author

stelucz commented Feb 1, 2023

/easycla

@liupeng0518
Copy link
Member

/lgtm
/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 2, 2023
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 2, 2023
Copy link
Member

@floryut floryut left a comment

Choose a reason for hiding this comment

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

@stelucz Thank you for the PR 🚀

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: floryut, stelucz

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 2, 2023
@floryut
Copy link
Member

floryut commented Feb 2, 2023

Could you please check CLA though ?

@stelucz
Copy link
Contributor Author

stelucz commented Feb 2, 2023

Could you please check CLA though ?

I signed that when PR was submited.

@stelucz
Copy link
Contributor Author

stelucz commented Feb 2, 2023

/easycla

@floryut
Copy link
Member

floryut commented Feb 2, 2023

Did you sign it using your commit email ? (l*.s*@eset.com)

@stelucz
Copy link
Contributor Author

stelucz commented Feb 2, 2023

Did you sign it using your commit email ? (l*.s*@eset.com)

Thanks for pointing it out. Can I change commit email somehow?

@floryut
Copy link
Member

floryut commented Feb 2, 2023

Did you sign it using your commit email ? (l*.s*@eset.com)

Thanks for pointing it out. Can I change commit email somehow?

You can always amend your commit : git commit --amend --author="John Doe <john@doe.org>" then push force your branch and voilà 👍

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed lgtm "Looks good to me", indicates that a PR is ready to be merged. cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Feb 2, 2023
@stelucz
Copy link
Contributor Author

stelucz commented Feb 2, 2023

Did you sign it using your commit email ? (l*.s*@eset.com)

Thanks for pointing it out. Can I change commit email somehow?

You can always amend your commit : git commit --amend --author="John Doe <john@doe.org>" then push force your branch and voilà 👍

thanks a lot!

@oomichi
Copy link
Contributor

oomichi commented Feb 2, 2023

Thanks for submitting this @stelucz

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 2, 2023
@k8s-ci-robot k8s-ci-robot merged commit 9247137 into kubernetes-sigs:master Feb 2, 2023
HoKim98 pushed a commit to ulagbulag/kubespray that referenced this pull request Mar 8, 2023
nolimitkun pushed a commit to nolimitkun/kubespray that referenced this pull request Mar 19, 2023
@yankay yankay mentioned this pull request May 15, 2023
pedro-peter pushed a commit to pedro-peter/kubespray that referenced this pull request May 8, 2024
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

NodeLocal DNS pod label
5 participants