This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 1 succeeded
Started2022-07-10 16:29
Elapsed21m17s
Revisionmaster

Test Failures


kubetest2 Up 15m56s

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 ...
I0710 16:31:06.776805    5938 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt
I0710 16:31:06.778965    5938 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.25.0-alpha.2+v1.25.0-alpha.1-61-g85c172ba32/linux/amd64/kops
I0710 16:31:08.121485    5938 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io/id_ed25519
I0710 16:31:08.135696    5938 up.go:44] Cleaning up any leaked resources from previous cluster
I0710 16:31:08.135798    5938 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/64f17518-006d-11ed-9fb7-3e7cb3b25c5e/kops toolbox dump --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0710 16:31:08.135825    5938 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/64f17518-006d-11ed-9fb7-3e7cb3b25c5e/kops toolbox dump --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0710 16:31:08.760955    5938 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0710 16:31:08.761012    5938 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/64f17518-006d-11ed-9fb7-3e7cb3b25c5e/kops delete cluster --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io --yes
I0710 16:31:08.761027    5938 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/64f17518-006d-11ed-9fb7-3e7cb3b25c5e/kops delete cluster --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io --yes
I0710 16:31:08.821389    5971 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io" not found
I0710 16:31:09.336197    5938 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/07/10 16:31:09 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
I0710 16:31:09.348823    5938 http.go:37] curl https://ip.jsb.workers.dev
I0710 16:31:09.458070    5938 up.go:159] /home/prow/go/src/k8s.io/kops/_rundir/64f17518-006d-11ed-9fb7-3e7cb3b25c5e/kops create cluster --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.11 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-calico-u2004-k22-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-focal-20.04-amd64-server-20220706 --channel=alpha --networking=calico --container-runtime=containerd --admin-access 34.71.153.193/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I0710 16:31:09.458114    5938 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/64f17518-006d-11ed-9fb7-3e7cb3b25c5e/kops create cluster --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.11 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-calico-u2004-k22-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-focal-20.04-amd64-server-20220706 --channel=alpha --networking=calico --container-runtime=containerd --admin-access 34.71.153.193/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I0710 16:31:09.496282    5981 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0710 16:31:09.534129    5981 create_cluster.go:862] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io/id_ed25519.pub
I0710 16:31:10.121182    5981 new_cluster.go:1168]  Cloud Provider ID = aws
... skipping 535 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
W0710 16:32:01.496023    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:32:11.535998    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:32:21.591633    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:32:31.640960    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:32:41.680763    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:32:51.714512    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:33:01.758975    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:33:11.808569    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:33:21.859179    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:33:31.908780    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:33:41.945584    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:33:51.992088    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:34:02.031455    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:34:12.074836    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:34:22.127891    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:34:32.170129    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:34:42.210605    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:34:52.266730    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:35:02.309446    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:35:12.354551    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:35:22.411015    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:35:32.458167    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:35:42.501835    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-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
W0710 16:35:52.552279    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 13 lines ...
Pod	kube-system/calico-node-hv7v4				system-node-critical pod "calico-node-hv7v4" is pending
Pod	kube-system/calico-node-szp62				system-node-critical pod "calico-node-szp62" is pending
Pod	kube-system/calico-node-v46g5				system-node-critical pod "calico-node-v46g5" is pending
Pod	kube-system/coredns-5fcc7b6498-c6x9m			system-cluster-critical pod "coredns-5fcc7b6498-c6x9m" is pending
Pod	kube-system/coredns-autoscaler-6bdc79bb85-gmfth		system-cluster-critical pod "coredns-autoscaler-6bdc79bb85-gmfth" is pending

Validation Failed
W0710 16:36:06.651120    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 16 lines ...
Pod	kube-system/calico-node-szp62				system-node-critical pod "calico-node-szp62" is pending
Pod	kube-system/calico-node-v46g5				system-node-critical pod "calico-node-v46g5" is pending
Pod	kube-system/calico-node-z5t9m				system-node-critical pod "calico-node-z5t9m" is pending
Pod	kube-system/coredns-5fcc7b6498-c6x9m			system-cluster-critical pod "coredns-5fcc7b6498-c6x9m" is pending
Pod	kube-system/coredns-autoscaler-6bdc79bb85-gmfth		system-cluster-critical pod "coredns-autoscaler-6bdc79bb85-gmfth" is pending

Validation Failed
W0710 16:36:19.542454    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 18 lines ...
Pod	kube-system/calico-node-tf2xr				system-node-critical pod "calico-node-tf2xr" is pending
Pod	kube-system/calico-node-v46g5				system-node-critical pod "calico-node-v46g5" is pending
Pod	kube-system/calico-node-z5t9m				system-node-critical pod "calico-node-z5t9m" is pending
Pod	kube-system/coredns-5fcc7b6498-c6x9m			system-cluster-critical pod "coredns-5fcc7b6498-c6x9m" is pending
Pod	kube-system/coredns-autoscaler-6bdc79bb85-gmfth		system-cluster-critical pod "coredns-autoscaler-6bdc79bb85-gmfth" is pending

Validation Failed
W0710 16:36:32.423975    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 18 lines ...
Pod	kube-system/calico-node-tf2xr				system-node-critical pod "calico-node-tf2xr" is pending
Pod	kube-system/calico-node-v46g5				system-node-critical pod "calico-node-v46g5" is pending
Pod	kube-system/calico-node-z5t9m				system-node-critical pod "calico-node-z5t9m" is pending
Pod	kube-system/coredns-5fcc7b6498-c6x9m			system-cluster-critical pod "coredns-5fcc7b6498-c6x9m" is pending
Pod	kube-system/coredns-autoscaler-6bdc79bb85-gmfth		system-cluster-critical pod "coredns-autoscaler-6bdc79bb85-gmfth" is pending

Validation Failed
W0710 16:36:45.297382    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 18 lines ...
Pod	kube-system/calico-node-tf2xr				system-node-critical pod "calico-node-tf2xr" is pending
Pod	kube-system/calico-node-v46g5				system-node-critical pod "calico-node-v46g5" is pending
Pod	kube-system/calico-node-z5t9m				system-node-critical pod "calico-node-z5t9m" is pending
Pod	kube-system/coredns-5fcc7b6498-c6x9m			system-cluster-critical pod "coredns-5fcc7b6498-c6x9m" is pending
Pod	kube-system/coredns-autoscaler-6bdc79bb85-gmfth		system-cluster-critical pod "coredns-autoscaler-6bdc79bb85-gmfth" is pending

Validation Failed
W0710 16:36:58.258774    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 19 lines ...
Pod	kube-system/calico-node-v46g5				system-node-critical pod "calico-node-v46g5" is pending
Pod	kube-system/calico-node-z5t9m				system-node-critical pod "calico-node-z5t9m" is pending
Pod	kube-system/coredns-5fcc7b6498-c6x9m			system-cluster-critical pod "coredns-5fcc7b6498-c6x9m" is pending
Pod	kube-system/coredns-autoscaler-6bdc79bb85-gmfth		system-cluster-critical pod "coredns-autoscaler-6bdc79bb85-gmfth" is pending
Pod	kube-system/ebs-csi-controller-746687b845-f2css		system-cluster-critical pod "ebs-csi-controller-746687b845-f2css" is pending

Validation Failed
W0710 16:37:11.190053    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 19 lines ...
Pod	kube-system/calico-node-v46g5				system-node-critical pod "calico-node-v46g5" is pending
Pod	kube-system/calico-node-z5t9m				system-node-critical pod "calico-node-z5t9m" is pending
Pod	kube-system/coredns-5fcc7b6498-c6x9m			system-cluster-critical pod "coredns-5fcc7b6498-c6x9m" is pending
Pod	kube-system/coredns-autoscaler-6bdc79bb85-gmfth		system-cluster-critical pod "coredns-autoscaler-6bdc79bb85-gmfth" is pending
Pod	kube-system/ebs-csi-controller-746687b845-f2css		system-cluster-critical pod "ebs-csi-controller-746687b845-f2css" is pending

Validation Failed
W0710 16:37:24.080873    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:37:36.967332    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:37:49.837334    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:38:02.887500    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:38:15.847550    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:38:28.705702    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:38:41.542737    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:38:54.622384    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:39:07.477604    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:39:20.528788    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:39:33.360324    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:39:46.235383    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:39:59.747378    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:40:12.604629    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:40:25.539409    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:40:38.507995    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:40:51.441691    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:41:04.315279    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:41:17.247193    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:41:30.226544    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:41:43.170469    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:41:56.105713    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:42:08.946127    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:42:21.896962    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:42:34.783487    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:42:47.557546    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:43:00.424474    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:43:13.308045    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:43:26.275668    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 24 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:43:39.073249    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 21 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:43:52.640605    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 20 lines ...
Pod	kube-system/ebs-csi-node-7wnrb				system-node-critical pod "ebs-csi-node-7wnrb" is pending
Pod	kube-system/ebs-csi-node-8dfcj				system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-l2x6k				system-node-critical pod "ebs-csi-node-l2x6k" is pending
Pod	kube-system/ebs-csi-node-m8krs				system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq				system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:44:05.583550    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 11 lines ...
Pod	kube-system/coredns-5fcc7b6498-c6x9m		system-cluster-critical pod "coredns-5fcc7b6498-c6x9m" is pending
Pod	kube-system/ebs-csi-controller-746687b845-f2css	system-cluster-critical pod "ebs-csi-controller-746687b845-f2css" is pending
Pod	kube-system/ebs-csi-node-8dfcj			system-node-critical pod "ebs-csi-node-8dfcj" is pending
Pod	kube-system/ebs-csi-node-m8krs			system-node-critical pod "ebs-csi-node-m8krs" is pending
Pod	kube-system/ebs-csi-node-zd5nq			system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:44:18.631004    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/ebs-csi-controller-746687b845-f2css	system-cluster-critical pod "ebs-csi-controller-746687b845-f2css" is pending
Pod	kube-system/ebs-csi-node-zd5nq			system-node-critical pod "ebs-csi-node-zd5nq" is pending

Validation Failed
W0710 16:44:31.468791    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 21 lines ...
ip-172-20-61-85.ap-northeast-2.compute.internal		master	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5fcc7b6498-4jtb4	system-cluster-critical pod "coredns-5fcc7b6498-4jtb4" is pending

Validation Failed
W0710 16:44:57.195392    6020 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-2a	Master	c5.large	1	1	ap-northeast-2a
nodes-ap-northeast-2a	Node	t3.medium	4	4	ap-northeast-2a

... skipping 124 lines ...
ip-172-20-56-129.ap-northeast-2.compute.internal	node	True
ip-172-20-59-167.ap-northeast-2.compute.internal	node	True
ip-172-20-61-85.ap-northeast-2.compute.internal		master	True

Your cluster e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io is ready
I0710 16:46:53.632053    6020 validate_cluster.go:220] (will retry): cluster passed validation 9 consecutive times
Error: Validation failed: wait time exceeded during validation
I0710 16:47:03.638606    5938 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/64f17518-006d-11ed-9fb7-3e7cb3b25c5e/kops toolbox dump --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0710 16:47:03.638757    5938 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/64f17518-006d-11ed-9fb7-3e7cb3b25c5e/kops toolbox dump --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0710 16:48:07.992829    5938 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/64f17518-006d-11ed-9fb7-3e7cb3b25c5e/kops get cluster --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io -o yaml
I0710 16:48:07.992896    5938 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/64f17518-006d-11ed-9fb7-3e7cb3b25c5e/kops get cluster --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io -o yaml
I0710 16:48:08.527805    5938 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/64f17518-006d-11ed-9fb7-3e7cb3b25c5e/kops get instancegroups --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io -o yaml
I0710 16:48:08.527843    5938 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/64f17518-006d-11ed-9fb7-3e7cb3b25c5e/kops get instancegroups --name e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io -o yaml
... skipping 321 lines ...
route-table:rtb-0bcc15c138a8000a3	ok
vpc:vpc-03e1920eaf769bc33	ok
dhcp-options:dopt-079a4f1fd93d277be	ok
Deleted kubectl config for e2e-e2e-kops-grid-calico-u2004-k22-containerd.test-cncf-aws.k8s.io

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