e2e-kops-aws-cni-calico-deb11 #1639386557183954944
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 1 succeeded |
| Started | |
| Elapsed | 20m18s |
| Revision | master |
exit status 1
from junit_runner.xml
Filter through log files | View test history on testgrid
kubetest2 Down
... skipping 137 lines ... I0324 22:01:41.493467 6160 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt I0324 22:01:41.531564 6160 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.27.0-alpha.2+v1.27.0-alpha.1-492-gf2f28e4cde/linux/amd64/kops I0324 22:01:44.128281 6160 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io/id_ed25519 I0324 22:01:44.135493 6160 up.go:44] Cleaning up any leaked resources from previous cluster I0324 22:01:44.135609 6160 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/31be6b9a-ca8f-11ed-acd1-d671b1981921/kops toolbox dump --name e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io/id_ed25519 --ssh-user admin I0324 22:01:44.135630 6160 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/31be6b9a-ca8f-11ed-acd1-d671b1981921/kops toolbox dump --name e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io/id_ed25519 --ssh-user admin Error: Cluster.kops.k8s.io "e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io" not found W0324 22:01:44.635389 6160 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0324 22:01:44.635437 6160 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/31be6b9a-ca8f-11ed-acd1-d671b1981921/kops delete cluster --name e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io --yes I0324 22:01:44.635450 6160 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/31be6b9a-ca8f-11ed-acd1-d671b1981921/kops delete cluster --name e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io --yes Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io" not found I0324 22:01:45.095259 6160 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2023/03/24 22:01:45 failed to get external ip from metadata service: http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip returned 404 I0324 22:01:45.107594 6160 http.go:37] curl https://ip.jsb.workers.dev I0324 22:01:45.198177 6160 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/31be6b9a-ca8f-11ed-acd1-d671b1981921/kops create cluster --name e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.28.0-alpha.0.5+0c62b122c02bff --ssh-public-key /tmp/kops/e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=136693071363/debian-11-amd64-20230124-1270 --channel=alpha --networking=calico --discovery-store=s3://k8s-kops-prow/discovery --admin-access 35.192.168.24/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2d --master-size c5.large I0324 22:01:45.198216 6160 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/31be6b9a-ca8f-11ed-acd1-d671b1981921/kops create cluster --name e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/k8s-release-dev/ci/v1.28.0-alpha.0.5+0c62b122c02bff --ssh-public-key /tmp/kops/e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io/id_ed25519.pub --set cluster.spec.nodePortAccess=0.0.0.0/0 --image=136693071363/debian-11-amd64-20230124-1270 --channel=alpha --networking=calico --discovery-store=s3://k8s-kops-prow/discovery --admin-access 35.192.168.24/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2d --master-size c5.large I0324 22:01:45.246933 6205 create_cluster.go:882] Using SSH public key: /tmp/kops/e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io/id_ed25519.pub I0324 22:01:45.703899 6205 new_cluster.go:1347] Cloud Provider ID: "aws" I0324 22:01:47.158008 6205 subnets.go:185] Assigned CIDR 172.20.32.0/19 to subnet ap-northeast-2d ... skipping 577 lines ... NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:02:30.009458 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:02:40.045066 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:02:50.093188 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:03:00.124976 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:03:10.170548 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:03:20.204083 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:03:30.236058 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:03:40.271426 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:03:50.304143 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:04:00.337496 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:04:10.373136 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:04:20.407810 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:04:30.440859 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:04:40.475243 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:04:50.521377 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:05:00.568325 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:05:10.822779 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:05:20.855948 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:05:30.890796 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:05:40.923990 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:05:50.955416 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:06:00.987089 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:06:11.046065 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:06:21.080781 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:06:31.111258 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:06:41.165790 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:06:51.222328 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node to start, dns-controller to launch, and DNS to propagate. The protokube container and dns-controller deployment logs may contain more diagnostic information. Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start. Validation Failed W0324 22:07:01.257889 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:07:15.467600 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:07:28.330498 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:07:41.139218 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:07:53.917935 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:08:06.770018 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:08:19.556800 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:08:32.308647 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:08:45.100807 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:08:57.943174 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:09:10.845850 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:09:23.825318 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:09:36.787331 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:09:49.556285 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:10:02.381272 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:10:15.247248 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:10:28.148558 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:10:40.911228 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:10:53.742277 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:11:07.190799 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:11:19.967678 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:11:32.784910 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:11:45.617589 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:11:58.430576 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:12:11.261266 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:12:24.131152 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:12:37.028621 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:12:49.916268 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:13:02.793742 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:13:15.656531 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:13:28.474836 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:13:41.374544 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:13:54.149507 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:14:07.083620 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:14:19.848710 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:14:32.626457 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:14:45.432670 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:14:58.799869 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:15:11.809830 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:15:24.633369 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:15:37.592614 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:15:50.352905 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:16:03.231615 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:16:16.059211 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:16:28.887678 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:16:41.656699 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:16:54.505665 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:17:07.304596 6244 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-2d ControlPlane c5.large 1 1 ap-northeast-2d nodes-ap-northeast-2d Node t3.medium 4 4 ap-northeast-2d ... skipping 9 lines ... Machine i-0fce0797e009cbbeb machine "i-0fce0797e009cbbeb" has not yet joined cluster Pod kube-system/coredns-745bddcfbb-mbcwq system-cluster-critical pod "coredns-745bddcfbb-mbcwq" is pending Pod kube-system/coredns-autoscaler-8495f5575-9np25 system-cluster-critical pod "coredns-autoscaler-8495f5575-9np25" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ccghm system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ccghm" is pending Pod kube-system/ebs-csi-controller-5d4b66d68d-ggngb system-cluster-critical pod "ebs-csi-controller-5d4b66d68d-ggngb" is pending Validation Failed W0324 22:17:20.024442 6244 validate_cluster.go:232] (will retry): cluster not yet healthy Error: validation failed: wait time exceeded during validation I0324 22:17:30.034220 6160 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/31be6b9a-ca8f-11ed-acd1-d671b1981921/kops toolbox dump --name e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io/id_ed25519 --ssh-user admin I0324 22:17:30.034304 6160 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/31be6b9a-ca8f-11ed-acd1-d671b1981921/kops toolbox dump --name e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io/id_ed25519 --ssh-user admin 2023/03/24 22:17:54 Dumping node i-084c45d95c008f703 2023/03/24 22:18:05 error dumping node i-084c45d95c008f703: error executing command "sysctl -a": Process exited with status 127 2023/03/24 22:18:05 dumping node not registered in kubernetes: 3.38.130.206 2023/03/24 22:18:05 Dumping node 3.38.130.206 2023/03/24 22:18:13 error dumping node 3.38.130.206: error executing command "sysctl -a": Process exited with status 127 2023/03/24 22:18:13 dumping node not registered in kubernetes: 3.39.244.155 2023/03/24 22:18:13 Dumping node 3.39.244.155 2023/03/24 22:18:21 error dumping node 3.39.244.155: error executing command "sysctl -a": Process exited with status 127 2023/03/24 22:18:21 dumping node not registered in kubernetes: 15.165.43.133 2023/03/24 22:18:21 Dumping node 15.165.43.133 2023/03/24 22:18:28 error dumping node 15.165.43.133: error executing command "sysctl -a": Process exited with status 127 2023/03/24 22:18:28 dumping node not registered in kubernetes: 3.35.200.212 2023/03/24 22:18:28 Dumping node 3.35.200.212 2023/03/24 22:18:36 error dumping node 3.35.200.212: error executing command "sysctl -a": Process exited with status 127 I0324 22:18:36.636163 6160 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/31be6b9a-ca8f-11ed-acd1-d671b1981921/kops get cluster --name e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io -o yaml I0324 22:18:36.636221 6160 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/31be6b9a-ca8f-11ed-acd1-d671b1981921/kops get cluster --name e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io -o yaml I0324 22:18:37.148715 6160 dumplogs.go:79] /home/prow/go/src/k8s.io/kops/_rundir/31be6b9a-ca8f-11ed-acd1-d671b1981921/kops get instancegroups --name e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io -o yaml I0324 22:18:37.148749 6160 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/31be6b9a-ca8f-11ed-acd1-d671b1981921/kops get instancegroups --name e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io -o yaml I0324 22:18:37.949492 6160 dumplogs.go:98] kubectl cluster-info dump --all-namespaces -o yaml --output-directory /logs/artifacts/cluster-info I0324 22:18:37.949548 6160 local.go:42] ⚙️ kubectl cluster-info dump --all-namespaces -o yaml --output-directory /logs/artifacts/cluster-info ... skipping 267 lines ... route-table:rtb-0f08a141e9207aa36 ok vpc:vpc-0b0badbd250ef1163 ok dhcp-options:dopt-055392b1b8275cc8a ok Deleted kubectl config for e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io Deleted cluster: "e2e-e2e-kops-aws-cni-calico-deb11.test-cncf-aws.k8s.io" Error: exit status 1 + EXIT_VALUE=1 + set +o xtrace