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

master:worker nodes enablement for nfd-worker #37

Merged
merged 1 commit into from
Nov 13, 2020

Conversation

ArangoGutierrez
Copy link
Contributor

After #31 three node cluster, where all nodes will have the master and worker(or node for vanilla clusters) labels are just getting the nfd-master daemonset deployed. Since they have the master label, the NFD workers will not be scheduled.

This Patch fix that adding support for master:worker type of nodes, being used in edge deployments

Signed-off-by: Carlos Eduardo Arango Gutierrez carangog@redhat.com

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Nov 13, 2020
@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Nov 13, 2020
@ArangoGutierrez
Copy link
Contributor Author

@rmkraus FYI

@ArangoGutierrez
Copy link
Contributor Author

Discussion started in a downstream distribution of NFD: openshift/cluster-nfd-operator#109

@ArangoGutierrez
Copy link
Contributor Author

/assign @marquiz

Copy link
Contributor

@marquiz marquiz left a comment

Choose a reason for hiding this comment

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

Thanks @ArangoGutierrez ! The change ooks good.

My only gripe is about the commit message which is very minimal and confusing. E.g. in the description of this PR there is somewhat good background information which could be used (almost as is) in the commit message

After kubernetes-sigs#31 three node cluster, where all nodes will have the master and
worker(or node for vanilla clusters) labels are just getting the
nfd-master daemonset deployed. Since they have the master label, the NFD
workers will not be scheduled.

Discussion started in a downstream distribution of NFD:
openshift/cluster-nfd-operator#109

This Patch fix that, by adding support for master:worker type of nodes,
modifying the nodeAffinity rules on the nfd-worker daemonSet to allow any node with the "node" label
(independent if it is a master also) to get scheduled

Signed-off-by: Carlos Eduardo Arango Gutierrez <carangog@redhat.com>
Copy link
Contributor

@marquiz marquiz left a comment

Choose a reason for hiding this comment

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

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 13, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ArangoGutierrez, marquiz

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:
  • OWNERS [ArangoGutierrez,marquiz]

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 merged commit 298629a into kubernetes-sigs:master Nov 13, 2020
@ArangoGutierrez ArangoGutierrez mentioned this pull request Dec 4, 2020
14 tasks
@ArangoGutierrez ArangoGutierrez deleted the rmkraus branch March 13, 2023 10:32
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. lgtm "Looks good to me", indicates that a PR is ready to be merged. 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