This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2022-09-28 04:23
Elapsed20m51s
Revisionmaster

Test Failures


kubetest2 Up 15m54s

exit status 1
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 166 lines ...
I0928 04:24:47.558432    6110 http.go:37] curl https://storage.googleapis.com/kops-ci/markers/release-1.24/latest-ci-updown-green.txt
I0928 04:24:47.560430    6110 http.go:37] curl https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.24.4+v1.24.3-10-g984e1362af/linux/amd64/kops
I0928 04:24:48.079241    6110 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io/id_ed25519
I0928 04:24:48.087708    6110 up.go:44] Cleaning up any leaked resources from previous cluster
I0928 04:24:48.087842    6110 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/2c3f4407-3ee5-11ed-9d09-ee6fcf89e9cd/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0928 04:24:48.087868    6110 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/2c3f4407-3ee5-11ed-9d09-ee6fcf89e9cd/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0928 04:24:48.567868    6110 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0928 04:24:48.567920    6110 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/2c3f4407-3ee5-11ed-9d09-ee6fcf89e9cd/kops delete cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io --yes
I0928 04:24:48.567934    6110 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/2c3f4407-3ee5-11ed-9d09-ee6fcf89e9cd/kops delete cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io --yes
I0928 04:24:48.588029    6140 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io" not found
I0928 04:24:49.036350    6110 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/09/28 04:24:49 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
I0928 04:24:49.052159    6110 http.go:37] curl https://ip.jsb.workers.dev
I0928 04:24:49.159497    6110 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/2c3f4407-3ee5-11ed-9d09-ee6fcf89e9cd/kops create cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.15 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-amd64-server-20220912 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 35.224.73.140/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large
I0928 04:24:49.159575    6110 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/2c3f4407-3ee5-11ed-9d09-ee6fcf89e9cd/kops create cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.15 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-amd64-server-20220912 --channel=alpha --networking=cilium-etcd --container-runtime=docker --admin-access 35.224.73.140/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large
I0928 04:24:49.181919    6149 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0928 04:24:49.211463    6149 create_cluster.go:864] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io/id_ed25519.pub
I0928 04:24:49.680854    6149 new_cluster.go:1168]  Cloud Provider ID = aws
... skipping 570 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 master 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
W0928 04:25:41.064679    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:25:51.110365    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:26:01.149460    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:26:11.194486    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:26:21.252520    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:26:31.295277    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:26:41.338327    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:26:51.380812    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:27:01.413110    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:27:11.453432    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:27:21.489724    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:27:31.535758    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:27:41.583734    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:27:51.636304    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:28:01.677905    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:28:11.732297    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:28:21.783934    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:28:31.816456    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:28:41.854275    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:28:51.906626    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:29:02.097853    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:29:12.138251    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:29:22.175172    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:29:32.228456    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:29:42.275874    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

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 master 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
W0928 04:29:52.314995    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 15 lines ...
Pod	kube-system/coredns-autoscaler-6fccfff6b-g9wdv		system-cluster-critical pod "coredns-autoscaler-6fccfff6b-g9wdv" is pending
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k		system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is pending
Pod	kube-system/ebs-csi-node-rpw25				system-node-critical pod "ebs-csi-node-rpw25" is pending
Pod	kube-system/ebs-csi-node-wcg2x				system-node-critical pod "ebs-csi-node-wcg2x" is pending
Pod	kube-system/ebs-csi-node-zp4hc				system-node-critical pod "ebs-csi-node-zp4hc" is pending

Validation Failed
W0928 04:30:06.679319    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 18 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k		system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is pending
Pod	kube-system/ebs-csi-node-9sqdv				system-node-critical pod "ebs-csi-node-9sqdv" is pending
Pod	kube-system/ebs-csi-node-rpw25				system-node-critical pod "ebs-csi-node-rpw25" is pending
Pod	kube-system/ebs-csi-node-wcg2x				system-node-critical pod "ebs-csi-node-wcg2x" is pending
Pod	kube-system/ebs-csi-node-zp4hc				system-node-critical pod "ebs-csi-node-zp4hc" is pending

Validation Failed
W0928 04:30:19.623464    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 20 lines ...
Pod	kube-system/ebs-csi-node-9sqdv				system-node-critical pod "ebs-csi-node-9sqdv" is pending
Pod	kube-system/ebs-csi-node-rpw25				system-node-critical pod "ebs-csi-node-rpw25" is pending
Pod	kube-system/ebs-csi-node-wcg2x				system-node-critical pod "ebs-csi-node-wcg2x" is pending
Pod	kube-system/ebs-csi-node-zbnqh				system-node-critical pod "ebs-csi-node-zbnqh" is pending
Pod	kube-system/ebs-csi-node-zp4hc				system-node-critical pod "ebs-csi-node-zp4hc" is pending

Validation Failed
W0928 04:30:32.631821    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 18 lines ...
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is pending
Pod	kube-system/ebs-csi-node-rpw25			system-node-critical pod "ebs-csi-node-rpw25" is pending
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is pending
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is pending
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is pending

Validation Failed
W0928 04:30:45.617738    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 13 lines ...
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is pending
Pod	kube-system/ebs-csi-node-rpw25			system-node-critical pod "ebs-csi-node-rpw25" is pending
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is pending
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is pending
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is pending

Validation Failed
W0928 04:30:58.634593    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 12 lines ...
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is pending
Pod	kube-system/ebs-csi-node-rpw25			system-node-critical pod "ebs-csi-node-rpw25" is pending
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is pending
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is pending
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is pending

Validation Failed
W0928 04:31:11.685090    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is pending
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is pending

Validation Failed
W0928 04:31:24.558266    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)

Validation Failed
W0928 04:31:37.590148    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)

Validation Failed
W0928 04:31:50.538289    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)

Validation Failed
W0928 04:32:03.596012    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)

Validation Failed
W0928 04:32:16.566372    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:32:30.345652    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)

Validation Failed
W0928 04:32:43.368459    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)

Validation Failed
W0928 04:32:56.317615    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)

Validation Failed
W0928 04:33:09.264533    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)

Validation Failed
W0928 04:33:22.254902    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:33:35.263575    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:33:48.231261    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:34:01.752017    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:34:14.960640    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)

Validation Failed
W0928 04:34:27.977887    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)

Validation Failed
W0928 04:34:40.929073    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)

Validation Failed
W0928 04:34:53.769848    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)

Validation Failed
W0928 04:35:06.819518    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)

Validation Failed
W0928 04:35:19.710510    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)

Validation Failed
W0928 04:35:32.636830    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:35:45.824033    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:35:58.668963    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:36:11.663969    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:36:24.600270    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:36:37.596579    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:36:50.713562    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:37:03.603579    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:37:16.624700    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:37:29.657583    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:37:42.610830    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:37:56.090333    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:38:09.063724    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)

Validation Failed
W0928 04:38:21.960677    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)

Validation Failed
W0928 04:38:34.880859    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)

Validation Failed
W0928 04:38:47.883007    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:39:00.871994    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:39:13.898161    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:39:26.862875    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 9 lines ...
KIND	NAME						MESSAGE
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:39:39.744659    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5b7f7db4db-hf96c		system-cluster-critical pod "coredns-5b7f7db4db-hf96c" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:39:52.706127    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:40:05.752849    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:40:18.796642    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-2a	Master	c5.large	1	1	ap-southeast-2a
nodes-ap-southeast-2a	Node	t3.medium	4	4	ap-southeast-2a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-controller-79ccbd7ff7-87h2k	system-cluster-critical pod "ebs-csi-controller-79ccbd7ff7-87h2k" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-9sqdv			system-node-critical pod "ebs-csi-node-9sqdv" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-wcg2x			system-node-critical pod "ebs-csi-node-wcg2x" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zbnqh			system-node-critical pod "ebs-csi-node-zbnqh" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-zp4hc			system-node-critical pod "ebs-csi-node-zp4hc" is not ready (ebs-plugin)

Validation Failed
W0928 04:40:31.780413    6189 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0928 04:40:41.787531    6110 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/2c3f4407-3ee5-11ed-9d09-ee6fcf89e9cd/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0928 04:40:41.787630    6110 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/2c3f4407-3ee5-11ed-9d09-ee6fcf89e9cd/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0928 04:41:46.487635    6110 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/2c3f4407-3ee5-11ed-9d09-ee6fcf89e9cd/kops get cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io -o yaml
I0928 04:41:46.487748    6110 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/2c3f4407-3ee5-11ed-9d09-ee6fcf89e9cd/kops get cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io -o yaml
I0928 04:41:47.002730    6110 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/2c3f4407-3ee5-11ed-9d09-ee6fcf89e9cd/kops get instancegroups --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io -o yaml
I0928 04:41:47.002757    6110 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/2c3f4407-3ee5-11ed-9d09-ee6fcf89e9cd/kops get instancegroups --name e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io -o yaml
... skipping 333 lines ...
route-table:rtb-0476394b2cf529910	ok
vpc:vpc-015b3babd1490ffbc	ok
dhcp-options:dopt-0914682f69a2db3d0	ok
Deleted kubectl config for e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io

Deleted cluster: "e2e-e2e-kops-grid-cilium-etcd-u2204-k22-ko24-docker.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace