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

Running on EKS results in client-ca-file failure #6

Closed
gavinbunney opened this issue Mar 25, 2020 · 2 comments
Closed

Running on EKS results in client-ca-file failure #6

gavinbunney opened this issue Mar 25, 2020 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@gavinbunney
Copy link

gavinbunney commented Mar 25, 2020

We run our kubernetes cluster on EKS (currently against v1.12.10). When running the wavefront adapter, we get the following error from the deployment:

I0325 18:33:30.747018       1 provider.go:37] wavefrontProvider prefix: kubernetes, listInterval: 900000000000
I0325 18:33:30.747077       1 main.go:108] starting wavefront adapter...
I0325 18:33:31.102882       1 serving.go:273] Generated self-signed cert (/etc/ssl/certs/apiserver.crt, /etc/ssl/certs/apiserver.key)
F0325 18:33:31.301466       1 main.go:110] unable to run custom metrics adapter: cluster doesn't provide client-ca-file

Looking at the aws-containers roadmap, it looks like there is requirement for the client-go libraries to use the v1.10 version of the libraries, otherwise the authentication flow fails: aws/containers-roadmap#152 (comment)

Is it possible to update the kubernetes client-go libraries, or provide another way to obtain the client-ca? Thanks!

Sidenote - whilst searching for solutions, I noticed cert-manager had the same issue, and fixed by bumping the kubernetes go-client libraries cert-manager/cert-manager#1220 (comment)

@vikramraman
Copy link
Contributor

Thanks for raising the issue. We'll look into this and get back soon.

@vikramraman vikramraman self-assigned this Mar 26, 2020
@vikramraman vikramraman added the bug Something isn't working label Mar 26, 2020
@vikramraman
Copy link
Contributor

Fixed: 9b4f2aa

Confirmed offline that this addressed the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants