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

Hyperkube image requires root certificates to work with cloud-providers (at least AWS) #7750

Closed
viklas opened this issue May 4, 2015 · 5 comments
Labels
priority/backlog Higher priority than priority/awaiting-more-evidence. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.

Comments

@viklas
Copy link

viklas commented May 4, 2015

Testing hyperkube deployment (upgraded to v0.16.1) and I ran into an issue where controller-manager couldn't connect to the nominated cloud-provider (AWS in this instance) and threw lots of errors: "X509: failed to load system roots and no roots provided".

Tried mounting host /etc/ssl/certs into kubelet and controller-manager pods...no good. Fixed by adding 'ca-certificates' to the apt-get command in the hyperkube dockerfile: https://github.com/GoogleCloudPlatform/kubernetes/blob/master/cluster/images/hyperkube/Dockerfile

Happy to raise a PR for this if needed.

-Luke

@roberthbailey
Copy link
Contributor

/cc @brendandburns

@roberthbailey
Copy link
Contributor

@viklas - sorry for the trouble; the hyperkube binary hasn't been tested much outside of the single and multi-node local docker getting started scenarios.

PRs are certainly welcome!

@roberthbailey roberthbailey added priority/backlog Higher priority than priority/awaiting-more-evidence. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. labels May 5, 2015
@viklas
Copy link
Author

viklas commented May 5, 2015

Log file entry from controller-manager container for future reference.

E0504 05:04:37.047853       1 nodecontroller.go:175] Error syncing cloud: 
Get https://ec2.ap-southeast-2.amazonaws.com/?AWSAccessKeyId=XXX&Action=DescribeInstances&SecurityToken=XXX&SignatureMethod=HmacSHA256&SignatureVersion=2&Timestamp=2015-05-04T05%3A04%3A37Z&Version=2014-06-15: x509: failed to load system roots and no roots provided

brendandburns added a commit that referenced this issue May 5, 2015
FIX: Issue #7750 - Hyperkube docker image needs certificates to connect to cloud-providers
@viklas
Copy link
Author

viklas commented May 8, 2015

This issue can be closed - PR merged successfully

@roberthbailey
Copy link
Contributor

Fixed by #7755.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/backlog Higher priority than priority/awaiting-more-evidence. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
Development

No branches or pull requests

2 participants