This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2022-09-13 22:00
Elapsed20m35s
Revisionmaster

Test Failures


kubetest2 Up 15m55s

exit status 1
				from junit_runner.xml

Filter through log files


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 166 lines ...
I0913 22:01:17.735784    6142 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0913 22:01:17.738160    6142 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.25.0-beta.2+v1.25.0-beta.1-71-g280a4a94ad/linux/amd64/kops
I0913 22:01:18.383131    6142 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519
I0913 22:01:18.396461    6142 up.go:44] Cleaning up any leaked resources from previous cluster
I0913 22:01:18.396583    6142 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/563f70b9-33af-11ed-9c39-9af7702f072d/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0913 22:01:18.396614    6142 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/563f70b9-33af-11ed-9c39-9af7702f072d/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0913 22:01:18.957797    6142 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0913 22:01:18.957862    6142 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/563f70b9-33af-11ed-9c39-9af7702f072d/kops delete cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --yes
I0913 22:01:18.957876    6142 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/563f70b9-33af-11ed-9c39-9af7702f072d/kops delete cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --yes
I0913 22:01:18.995020    6175 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io" not found
I0913 22:01:19.490625    6142 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/09/13 22:01:19 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
I0913 22:01:19.505860    6142 http.go:37] curl https://ip.jsb.workers.dev
I0913 22:01:19.670299    6142 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/563f70b9-33af-11ed-9c39-9af7702f072d/kops create cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.24.4 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.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=containerd --admin-access 35.202.151.134/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large
I0913 22:01:19.670528    6142 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/563f70b9-33af-11ed-9c39-9af7702f072d/kops create cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.24.4 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.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=containerd --admin-access 35.202.151.134/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-2a --master-size c5.large
I0913 22:01:19.705208    6185 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0913 22:01:19.726015    6185 create_cluster.go:843] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519.pub
I0913 22:01:20.239565    6185 new_cluster.go:1277]  Cloud Provider ID = aws
... skipping 575 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
W0913 22:02:12.343472    6222 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
W0913 22:02:22.403943    6222 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
W0913 22:02:32.462542    6222 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
W0913 22:02:42.519033    6222 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
W0913 22:02:52.565448    6222 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
W0913 22:03:02.624932    6222 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
W0913 22:03:12.664581    6222 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
W0913 22:03:22.746812    6222 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
W0913 22:03:32.802063    6222 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
W0913 22:03:42.862819    6222 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
W0913 22:03:52.934223    6222 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
W0913 22:04:02.990811    6222 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
W0913 22:04:13.036684    6222 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
W0913 22:04:23.088496    6222 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
W0913 22:04:33.137628    6222 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
W0913 22:04:43.197839    6222 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
W0913 22:04:53.272944    6222 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
W0913 22:05:03.342865    6222 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
W0913 22:05:13.396924    6222 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
W0913 22:05:23.758382    6222 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
W0913 22:05:34.770811    6222 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
W0913 22:05:44.839127    6222 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
W0913 22:05:54.898028    6222 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 21 lines ...
Pod	kube-system/ebs-csi-node-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is pending
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is pending
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is pending
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is pending
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is pending

Validation Failed
W0913 22:06:09.242561    6222 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 22 lines ...
Pod	kube-system/ebs-csi-node-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is pending
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is pending
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is pending
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is pending
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is pending

Validation Failed
W0913 22:06:22.287441    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is pending
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is pending
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is pending
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is pending
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is pending

Validation Failed
W0913 22:06:35.350280    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is pending
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is pending
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is pending
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is pending
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is pending

Validation Failed
W0913 22:06:48.377797    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is pending
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is pending
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is pending
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is pending
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is pending

Validation Failed
W0913 22:07:01.343828    6222 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-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is pending
Pod	kube-system/ebs-csi-node-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is pending
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is pending
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is pending
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is pending

Validation Failed
W0913 22:07:14.324194    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is pending

Validation Failed
W0913 22:07:27.337986    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)

Validation Failed
W0913 22:07:40.266158    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)

Validation Failed
W0913 22:07:53.292904    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)

Validation Failed
W0913 22:08:06.175683    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)

Validation Failed
W0913 22:08:19.131409    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)

Validation Failed
W0913 22:08:32.325038    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)

Validation Failed
W0913 22:08:45.303883    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:08:58.358001    6222 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-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:09:11.373958    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)

Validation Failed
W0913 22:09:24.415034    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)

Validation Failed
W0913 22:09:37.426939    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)

Validation Failed
W0913 22:09:50.400316    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)

Validation Failed
W0913 22:10:03.991259    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)

Validation Failed
W0913 22:10:17.028967    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:10:30.083738    6222 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-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:10:43.067439    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:10:56.207537    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:11:09.288833    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:11:22.311935    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:11:35.323171    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:11:48.433540    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)

Validation Failed
W0913 22:12:01.509889    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)

Validation Failed
W0913 22:12:14.544777    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:12:27.507565    6222 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-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:12:40.451710    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:12:53.447821    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:13:06.532265    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:13:19.550248    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:13:32.638149    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:13:45.787595    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:14:00.108112    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:14:13.096327    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:14:26.088228    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:14:39.063015    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:14:52.055566    6222 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-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:15:05.065321    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)

Validation Failed
W0913 22:15:18.078934    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)

Validation Failed
W0913 22:15:31.093947    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)

Validation Failed
W0913 22:15:44.198136    6222 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-5c44b6cf7d-bcsmq		system-cluster-critical pod "coredns-5c44b6cf7d-bcsmq" is not ready (coredns)
Pod	kube-system/ebs-csi-controller-5b9566744f-v84wk	system-cluster-critical pod "ebs-csi-controller-5b9566744f-v84wk" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:15:57.210989    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:16:10.290013    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:16:23.353843    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:16:36.526861    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:16:49.722641    6222 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-7glkt			system-node-critical pod "ebs-csi-node-7glkt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-86jt8			system-node-critical pod "ebs-csi-node-86jt8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-k6gc8			system-node-critical pod "ebs-csi-node-k6gc8" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-mdm97			system-node-critical pod "ebs-csi-node-mdm97" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xf9sd			system-node-critical pod "ebs-csi-node-xf9sd" is not ready (ebs-plugin)

Validation Failed
W0913 22:17:02.686212    6222 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0913 22:17:12.692689    6142 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/563f70b9-33af-11ed-9c39-9af7702f072d/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0913 22:17:12.692746    6142 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/563f70b9-33af-11ed-9c39-9af7702f072d/kops toolbox dump --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0913 22:18:26.318239    6142 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/563f70b9-33af-11ed-9c39-9af7702f072d/kops get cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io -o yaml
I0913 22:18:26.318318    6142 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/563f70b9-33af-11ed-9c39-9af7702f072d/kops get cluster --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io -o yaml
I0913 22:18:26.914370    6142 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/563f70b9-33af-11ed-9c39-9af7702f072d/kops get instancegroups --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io -o yaml
I0913 22:18:26.914534    6142 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/563f70b9-33af-11ed-9c39-9af7702f072d/kops get instancegroups --name e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io -o yaml
... skipping 277 lines ...
route-table:rtb-0a29b85e58024cb27	ok
vpc:vpc-00c33179e6b4ad8ec	ok
dhcp-options:dopt-0bcb0eae667fe2015	ok
Deleted kubectl config for e2e-e2e-kops-grid-cilium-etcd-u2204-k24-containerd.test-cncf-aws.k8s.io

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