Hot answers tagged

2

kops delete secret --name cluster-1.dev.transein.com sshpublickey admin 2c:yy


1

I loaded the kubeconfig before and the error disappeared. $ export KUBECONFIG=~/workspace/myrepo/_kube/dev/kubeconfig $ AWS_ACCESS_KEY_ID=<my_legit_key> AWS_SECRET_ACCESS_KEY=<my_legit_secret_key> kops validate cluster --wait 10m --state="s3://<my_bucket_name>" --name=<my_cluster_name> ## And it worked If the kubeconfig ...


1

I solved this temporarily with not the safest solution, but is working When creating secret with kops named admin, can use that to generate user field in exported kops config by adding also --admin in the export command


Only top voted, non community-wiki answers of a minimum length are eligible