This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2022-07-21 13:41
Elapsed20m21s
Revisionmaster

Test Failures


kubetest2 Up 16m4s

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 159 lines ...
I0721 13:42:39.759903    5944 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0721 13:42:39.762148    5944 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.25.0-alpha.2+v1.25.0-alpha.1-105-gea32e12ce7/linux/amd64/kops
I0721 13:42:40.626886    5944 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519
I0721 13:42:40.634511    5944 up.go:44] Cleaning up any leaked resources from previous cluster
I0721 13:42:40.634657    5944 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/c1d1b516-08fa-11ed-9a3b-664c144f8066/kops toolbox dump --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
I0721 13:42:40.634678    5944 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c1d1b516-08fa-11ed-9a3b-664c144f8066/kops toolbox dump --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
W0721 13:42:41.161727    5944 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0721 13:42:41.161779    5944 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/c1d1b516-08fa-11ed-9a3b-664c144f8066/kops delete cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --yes
I0721 13:42:41.161791    5944 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c1d1b516-08fa-11ed-9a3b-664c144f8066/kops delete cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --yes
I0721 13:42:41.187120    5976 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io" not found
I0721 13:42:41.660313    5944 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/07/21 13:42:41 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
I0721 13:42:41.670714    5944 http.go:37] curl https://ip.jsb.workers.dev
I0721 13:42:41.766154    5944 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/c1d1b516-08fa-11ed-9a3b-664c144f8066/kops create cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.12 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=309956199498/RHEL-8.5.0_HVM-20211103-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium --container-runtime=docker --admin-access 34.134.227.164/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-1a --master-size c5.large
I0721 13:42:41.766191    5944 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c1d1b516-08fa-11ed-9a3b-664c144f8066/kops create cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.12 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=309956199498/RHEL-8.5.0_HVM-20211103-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium --container-runtime=docker --admin-access 34.134.227.164/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-1a --master-size c5.large
I0721 13:42:41.786857    5986 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0721 13:42:41.814035    5986 create_cluster.go:862] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub
I0721 13:42:42.414725    5986 new_cluster.go:1168]  Cloud Provider ID = aws
... skipping 519 lines ...

I0721 13:43:32.665656    5944 up.go:243] /home/prow/go/src/k8s.io/kops/_rundir/c1d1b516-08fa-11ed-9a3b-664c144f8066/kops validate cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0721 13:43:32.665723    5944 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c1d1b516-08fa-11ed-9a3b-664c144f8066/kops validate cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0721 13:43:32.690557    6027 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Validating cluster e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io

W0721 13:43:34.447913    6027 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:43:44.505564    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:43:54.542698    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:44:04.583312    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:44:14.622128    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:44:24.661185    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:44:34.699029    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:44:44.740416    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:44:54.776758    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:45:04.830221    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:45:14.871591    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:45:24.913411    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:45:34.956656    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:45:45.001520    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:45:55.039433    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:46:05.084643    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:46:15.126163    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:46:25.169786    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:46:35.218597    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:46:45.261694    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:46:55.299561    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:47:05.339587    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:47:15.383728    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:47:25.432334    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
W0721 13:47:35.476819    6027 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:47:45.519056    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:47:55.572635    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:48:05.606467    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

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
W0721 13:48:15.658888    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Node	ip-172-20-32-215.ap-southeast-1.compute.internal	node "ip-172-20-32-215.ap-southeast-1.compute.internal" of role "master" is not ready
Pod	kube-system/ebs-csi-controller-7f79b4694f-2pc45		system-cluster-critical pod "ebs-csi-controller-7f79b4694f-2pc45" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:48:30.673575    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 15 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:48:44.163217    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:48:57.436701    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:49:10.733201    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:49:24.027626    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:49:37.612718    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:49:50.937950    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:50:04.463809    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:50:17.825218    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:50:31.156365    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:50:44.547749    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:50:58.028663    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:51:11.430140    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:51:25.440944    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:51:38.740748    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:51:53.088551    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:52:06.338148    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:52:20.287452    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:52:33.579445    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:52:46.802663    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:53:00.089554    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:53:13.417705    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:53:26.787084    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:53:40.129888    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:53:53.428306    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:54:06.911712    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:54:20.172424    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:54:33.425883    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:54:46.734724    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:55:00.318192    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:55:13.640906    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:55:26.924005    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:55:40.281145    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:55:53.691127    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:56:07.145101    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:56:21.237656    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:56:34.607684    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:56:47.890329    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:57:01.118465    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:57:14.401089    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:57:27.727183    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:57:41.027829    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:57:54.293307    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:58:07.588904    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:58:21.006281    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-6db7z				system-node-critical pod "ebs-csi-node-6db7z" is pending
Pod	kube-system/ebs-csi-node-7vmt8				system-node-critical pod "ebs-csi-node-7vmt8" is pending
Pod	kube-system/ebs-csi-node-hprpj				system-node-critical pod "ebs-csi-node-hprpj" is pending
Pod	kube-system/ebs-csi-node-n6bgs				system-node-critical pod "ebs-csi-node-n6bgs" is pending
Pod	kube-system/ebs-csi-node-xtjkv				system-node-critical pod "ebs-csi-node-xtjkv" is pending

Validation Failed
W0721 13:58:34.285790    6027 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0721 13:58:44.295284    5944 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/c1d1b516-08fa-11ed-9a3b-664c144f8066/kops toolbox dump --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
I0721 13:58:44.295362    5944 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c1d1b516-08fa-11ed-9a3b-664c144f8066/kops toolbox dump --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user
I0721 13:59:51.747623    5944 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/c1d1b516-08fa-11ed-9a3b-664c144f8066/kops get cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io -o yaml
I0721 13:59:51.747673    5944 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c1d1b516-08fa-11ed-9a3b-664c144f8066/kops get cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io -o yaml
I0721 13:59:52.319808    5944 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/c1d1b516-08fa-11ed-9a3b-664c144f8066/kops get instancegroups --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io -o yaml
I0721 13:59:52.319846    5944 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/c1d1b516-08fa-11ed-9a3b-664c144f8066/kops get instancegroups --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io -o yaml
... skipping 257 lines ...
route-table:rtb-0a6d8e54120468c02	ok
vpc:vpc-073a7e1a7e117a2c6	ok
dhcp-options:dopt-07c3daa792c83be4a	ok
Deleted kubectl config for e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io

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