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

[Question] should we support adding roles to worker node ? #881

Closed
jichenjc opened this issue Apr 9, 2019 · 10 comments
Closed

[Question] should we support adding roles to worker node ? #881

jichenjc opened this issue Apr 9, 2019 · 10 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@jichenjc
Copy link
Contributor

jichenjc commented Apr 9, 2019

This actually comes from kubernetes-sigs/cluster-api-provider-openstack#298
but I think it's applicable to cluster-api

should we add this into yaml so that user is able to set role during cluster-api creation stage or guide user to change the role after cluster is up?

Describe the solution you'd like
[A clear and concise description of what you want to happen.]

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 9, 2019
@gyliu513
Copy link
Contributor

gyliu513 commented Apr 9, 2019

/cc @vincepri @detiber

Thanks @jichenjc , +1 for this.

@detiber
Copy link
Member

detiber commented Apr 9, 2019

In the AWS provider we started setting the worker node role to node. I do like the idea of being able to specify the role, though.

@vincepri
Copy link
Member

vincepri commented Apr 9, 2019

Hopefully the role can be offered, in the fullness of time, as a top level configuration parameter and default to node as @detiber mentioned.

@vincepri vincepri added this to the Next milestone Apr 9, 2019
@vincepri vincepri added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Apr 9, 2019
@jichenjc
Copy link
Contributor Author

@detiber can you tell me where's the place to add role in aws provider? just want to refer to .. thanks

@jichenjc
Copy link
Contributor Author

/assign

I can take a look and see how we can achieve this

@jichenjc
Copy link
Contributor Author

@tashimi thanks for the comments ~

@jichenjc
Copy link
Contributor Author

#493 seems addressed this issue ...

@ncdc
Copy link
Contributor

ncdc commented May 31, 2019

Closing this as a duplicate of #493.
/close

@k8s-ci-robot
Copy link
Contributor

@ncdc: Closing this issue.

In response to this:

Closing this as a duplicate of #493.
/close

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
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

7 participants