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

How does bare metal machine use token #7892

Closed
WIZARD-CXY opened this issue May 7, 2015 · 3 comments
Closed

How does bare metal machine use token #7892

WIZARD-CXY opened this issue May 7, 2015 · 3 comments
Labels
kind/support Categorizes issue or PR as a support question.

Comments

@WIZARD-CXY
Copy link
Contributor

@erictune
As #5470 and #5921 said. I agreed with your idea to use secret to enhance the security of the internal cluster.But the secret are created for gke using saltstack . I don't know how to generate it for a bare metal ubuntu cluster.Now when I want to deploy skydns with 0.16.0 k8s, it complains it can't find a token. I want to integrate this feature to the ubuntu k8s deployment .Please tell me how. Thanks a lot

@mbforbes mbforbes added kind/support Categorizes issue or PR as a support question. priority/support labels May 7, 2015
@mbforbes
Copy link
Contributor

mbforbes commented May 7, 2015

+cc @roberthbailey

@roberthbailey
Copy link
Contributor

/cc @cjcullen

Today this requires basically manually replicating what salt is doing on GCE (generate a bearer token and add it to a csv file that is loaded by the apiserver). If you give it the same name as we do on GCE, the line in your csv file should look like:

RANDOM_TOKEN_STRING,system:dns,system:dns

Then you should be able to use the dns pod as is.

We are hoping that the service account PR (#7101) will allow us to use service accounts in the system namespace to replace this token generation.

@WIZARD-CXY
Copy link
Contributor Author

thanks for the reply.I will wait for #7101 to land

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question.
Projects
None yet
Development

No branches or pull requests

3 participants