Closed TonyApuzzo closed 5 years ago
Thanks for the report.
Does this work? Note: it will replace your config completely so back it up.
doctl k8s cluster config show cluster-id > ~/.kube/config
Yes, using doctl k8s cluster config show cluster-id > ~/.kube/config
worked fine.
Thank you!
Think this was fixed and saving behavior works as expected. Please reopen if not.
I'm still seeing this issue with version 1.20.0-release
. I would be fine inputting my username and password but I have no idea what it is and several iterations I've tried don't work. doctl
is installed through homebrew for me.
Here's the command I'm using:
doctl k8s cluster config save <cluster-name>
And here's the config that gets saved:
apiVersion: v1
clusters:
- cluster:
certificate-authority-data: <cert-data>
server: <server-url>
name: do-nyc1-<cluster-name>
contexts:
- context:
cluster: do-nyc1-<cluster-name>
user: do-nyc1-<cluster-name>-admin
name: do-nyc1-<cluster-name>
current-context: do-nyc1-<cluster-name>
kind: Config
preferences: {}
users:
- name: do-nyc1-<cluster-name>-admin
user:
exec:
apiVersion: client.authentication.k8s.io/v1beta1
args:
- kubernetes
- cluster
- kubeconfig
- exec-credential
- --version=v1beta1
- <uuid?>
command: doctl
env: null
Output from doctl k8s cluster config show <cluster-name>
:
apiVersion: v1
clusters:
- cluster:
certificate-authority-data: <cert-data>
server: <server-url>
name: do-nyc1-<cluster-name>
contexts:
- context:
cluster: do-nyc1-<cluster-name>
user: do-nyc1-<cluster-name>-admin
name: do-nyc1-<cluster-name>
current-context: do-nyc1-<cluster-name>
kind: Config
preferences: {}
users:
- name: do-nyc1-<cluster-name>-admin
user:
client-certificate-data: <cert-data>
client-key-data: <key-data>
> doctl version
doctl version 1.20.0-release
If I use the kubernetes config downloaded by doctl, I can't subsequently use
kompose
but if I download the config file from the GUI it works fine.Download k8s config
Use it
But
kompose
fails:... remove ~/.kube/config and replace with one downloaded from the Web GUI ...