Ask questionsInstanceGroup not found (for etcd ap-southeast-2a/main): "ap-southeast-2a"

1. What kops version are you running? The command kops version, will display this information.

Version 1.14.0 (git-d5078612f)

2. What Kubernetes version are you running? kubectl version will print the version if a cluster is running or provide the Kubernetes version specified as a kops flag.

Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.3", GitCommit:"2d3c76f9091b6bec110a5e63777c332469e0cba2", GitTreeState:"clean", BuildDate:"2019-08-19T11:13:54Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"darwin/amd64"}

3. What cloud provider are you using?


4. What commands did you run? What is the simplest way to reproduce this issue?

./kops-api-example -registry s3://liuxun-cluster.k8s.local-state.ym -name kops.api.example.k8s.local -zones ap-southeast-2a,ap-southeast-2b

5. What happened after the commands executed?

error from apply: error building tasks: InstanceGroup not found (for etcd ap-southeast-2a/main): "ap-southeast-2a"

6. What did you expect to happen?

kops create cluster

7. Please provide your cluster manifest. Execute kops get --name -o yaml to display your cluster manifest. You may want to remove your cluster name and other sensitive information.

error reading cluster configuration "kops.api.example.k8s.local": error parsing s3://liuxun-cluster.k8s.local-state.ym/kops.api.example.k8s.local/config: no kind "Cluster" is registered for version "" in scheme ""

8. Please run the commands with most verbose logging by adding the -v 10 flag. Paste the logs into this report, or in a gist and provide the gist link here.

9. Anything else do we need to know?

Before execute the ./kops-api-example command, what preparations do you need to do on aws?

Answer questions xunliu

After debugging the code, I found this problem, probably because the example did not use the latest code and processing flow of kops.


Related questions

Unable to use a local filesystem state store hot 2
Kops 1.12-beta.2 won't/can't bring up etcd server, manager or kube-api hot 1
kube controller manager refuses to connect after upgrading from 1.10.6 to 1.11.7 hot 1
Missing kops controller support for cloudproviders hot 1
Rolling-update fails due to calico-node with 1.12.0-beta.2 hot 1
Kubelet Unable To Apply Reserved Cgroup Limits because Cgroup does not exist hot 1
etcd3 and kube-apiserver fail on terraform apply after terraform destroying w/ kops generated config hot 1
Upgrade from Kops 1.11 to 1.12 has failed. hot 1
Couldn't find key etcd_endpoints in ConfigMap kube-system/calico-config hot 1
Protokube has sustained cpu usage above 100% hot 1
Allow just one instance type in mixedInstancesPolicy hot 1
kubectl command: Unable to connect to the server: EOF hot 1
DNS record for public API address not updated hot 1
etcd3 and kube-apiserver fail on terraform apply after terraform destroying w/ kops generated config hot 1
Issues encountered deploying to OpenStack hot 1
Github User Rank List