-
Notifications
You must be signed in to change notification settings - Fork 14
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
Client-Cert Error #64
Comments
Same error, on ubuntu 16.04, how to fix that ?! |
Can you share the structure (but certainly not the secrets) of your kubeconfig file? What credentials do you have for accessing this cloud? Support for this kind of credentials will probably need to be added to txkube (upon which kubetop is based). |
I'm having the same issue with a gcloud GKE setup. This is my redacted kubeconfig: apiVersion: v1
clusters:
- cluster:
certificate-authority-data: XXX=
server: https://XXX
name: gke_XXX
contexts:
- context:
cluster: gke_XXX
user: gke_XXX
name: prod
current-context: prod
kind: Config
preferences: {}
users:
- name: gke_XXX
user:
auth-provider:
config:
access-token: XXX
cmd-args: config config-helper --format=json
cmd-path: /home/ray/google-cloud-sdk/bin/gcloud
expiry: XXX
expiry-key: '{.credential.token_expiry}'
token-key: '{.credential.access_token}'
name: gcp
|
Any workaround for this problem? |
Had the same problem, probably it's about having RBAC enabled on the cluster. A workaround would be using admin credentials (Note#1), but surely access tokens should be supported as well. Note#1: Be aware that it isn't a good idea to use admin credentials against an RBAC enabled cluster. |
I already have a setup for gcloud & kube. Please explain how to generate this certificate & how to configure otherwise?
The text was updated successfully, but these errors were encountered: