This job view page is being replaced by Spyglass soon. Check out the new job view.
PRReillyBrogan: Add bidirectional BPF mount for Cilium >= 1.9.10 or >= 1.10.4
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-09-24 19:01
Elapsed24m48s
Revision9c6bf83c93a6af0b913e0a8d04e1f1d222153703
Refs 12394

No Test Failures!


Error lines from build-log.txt

... skipping 548 lines ...
Operation completed over 1 objects/153.0 B.                                      
I0924 19:06:15.644889    4851 copy.go:30] cp /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops /logs/artifacts/bee27473-1d69-11ec-8a3f-cace5e8e15e8/kops
I0924 19:06:15.790670    4851 up.go:43] Cleaning up any leaked resources from previous cluster
I0924 19:06:15.790723    4851 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0924 19:06:15.805563   12473 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 19:06:15.805976   12473 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io" not found
W0924 19:06:16.243344    4851 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0924 19:06:16.243400    4851 down.go:48] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops delete cluster --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --yes
I0924 19:06:16.258560   12481 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 19:06:16.258646   12481 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io" not found
I0924 19:06:16.701408    4851 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/24 19:06:16 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
I0924 19:06:16.708952    4851 http.go:37] curl https://ip.jsb.workers.dev
I0924 19:06:16.793692    4851 up.go:144] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops create cluster --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.2 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=099720109477/ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20210907 --channel=alpha --networking=weave --container-runtime=containerd --node-size=t3.large --admin-access 34.68.37.186/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-2a --master-size c5.large
I0924 19:06:16.810449   12490 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 19:06:16.811248   12490 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0924 19:06:16.831728   12490 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0924 19:06:17.273673   12490 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

I0924 19:06:44.943533    4851 up.go:181] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops validate cluster --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I0924 19:06:44.958987   12511 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 19:06:44.959070   12511 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io

W0924 19:06:46.416744   12511 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
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.large	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
W0924 19:06:56.450557   12511 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.large	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
W0924 19:07:06.478341   12511 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.large	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
W0924 19:07:16.522591   12511 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.large	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
W0924 19:07:26.568955   12511 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.large	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
W0924 19:07:36.596316   12511 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.large	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
W0924 19:07:46.627701   12511 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.large	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
W0924 19:07:56.656812   12511 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.large	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
W0924 19:08:06.703209   12511 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.large	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
W0924 19:08:16.736487   12511 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.large	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
W0924 19:08:26.779719   12511 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.large	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
W0924 19:08:36.807526   12511 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.large	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
W0924 19:08:46.849460   12511 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.large	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
W0924 19:08:56.879961   12511 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.large	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
W0924 19:09:06.922536   12511 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.large	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
W0924 19:09:16.953282   12511 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.large	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
W0924 19:09:26.988940   12511 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.large	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
W0924 19:09:37.018118   12511 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.large	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
W0924 19:09:47.060734   12511 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.large	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
W0924 19:09:57.091424   12511 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.large	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
W0924 19:10:07.124714   12511 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.large	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
W0924 19:10:17.151888   12511 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.large	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
W0924 19:10:27.182352   12511 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.large	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
W0924 19:10:37.210664   12511 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.large	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
W0924 19:10:47.256750   12511 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.large	4	4	ap-northeast-2a

... skipping 7 lines ...
Machine	i-088bf27f47c35085f				machine "i-088bf27f47c35085f" has not yet joined cluster
Machine	i-0ae7e66a38139a678				machine "i-0ae7e66a38139a678" has not yet joined cluster
Machine	i-0f8e15b5e6df30784				machine "i-0f8e15b5e6df30784" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-mhs4s		system-cluster-critical pod "coredns-5dc785954d-mhs4s" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-xqzdx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-xqzdx" is pending

Validation Failed
W0924 19:11:01.436537   12511 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.large	4	4	ap-northeast-2a

... skipping 16 lines ...
Pod	kube-system/ebs-csi-node-stpzw				system-node-critical pod "ebs-csi-node-stpzw" is pending
Pod	kube-system/ebs-csi-node-xkzcx				system-node-critical pod "ebs-csi-node-xkzcx" is pending
Pod	kube-system/weave-net-h664q				system-node-critical pod "weave-net-h664q" is pending
Pod	kube-system/weave-net-l577w				system-node-critical pod "weave-net-l577w" is pending
Pod	kube-system/weave-net-wdzgk				system-node-critical pod "weave-net-wdzgk" is pending

Validation Failed
W0924 19:11:14.081984   12511 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.large	4	4	ap-northeast-2a

... skipping 11 lines ...
Pod	kube-system/coredns-autoscaler-84d4cfd89c-xqzdx	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-xqzdx" is pending
Pod	kube-system/ebs-csi-node-2chtt			system-node-critical pod "ebs-csi-node-2chtt" is pending
Pod	kube-system/ebs-csi-node-stpzw			system-node-critical pod "ebs-csi-node-stpzw" is pending
Pod	kube-system/ebs-csi-node-xkzcx			system-node-critical pod "ebs-csi-node-xkzcx" is pending
Pod	kube-system/weave-net-l577w			system-node-critical pod "weave-net-l577w" is not ready (weave)

Validation Failed
W0924 19:11:26.713385   12511 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.large	4	4	ap-northeast-2a

... skipping 14 lines ...
Pod	kube-system/ebs-csi-node-stpzw						system-node-critical pod "ebs-csi-node-stpzw" is pending
Pod	kube-system/kube-proxy-ip-172-20-48-197.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-48-197.ap-northeast-2.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-62-108.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-62-108.ap-northeast-2.compute.internal" is pending
Pod	kube-system/weave-net-96vvq						system-node-critical pod "weave-net-96vvq" is pending
Pod	kube-system/weave-net-l577w						system-node-critical pod "weave-net-l577w" is not ready (weave)

Validation Failed
W0924 19:11:39.408872   12511 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.large	4	4	ap-northeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is pending
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is pending

Validation Failed
W0924 19:11:52.025833   12511 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.large	4	4	ap-northeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s					system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt						system-node-critical pod "ebs-csi-node-2chtt" is pending
Pod	kube-system/kube-proxy-ip-172-20-53-251.ap-northeast-2.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-53-251.ap-northeast-2.compute.internal" is pending

Validation Failed
W0924 19:12:04.598330   12511 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.large	4	4	ap-northeast-2a

... skipping 6 lines ...
ip-172-20-62-108.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)

Validation Failed
W0924 19:12:18.355738   12511 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.large	4	4	ap-northeast-2a

... skipping 6 lines ...
ip-172-20-62-108.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)

Validation Failed
W0924 19:12:31.069788   12511 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.large	4	4	ap-northeast-2a

... skipping 6 lines ...
ip-172-20-62-108.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)

Validation Failed
W0924 19:12:43.741451   12511 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.large	4	4	ap-northeast-2a

... skipping 6 lines ...
ip-172-20-62-108.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)

Validation Failed
W0924 19:12:56.379975   12511 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.large	4	4	ap-northeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:13:09.027967   12511 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.large	4	4	ap-northeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:13:21.658042   12511 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.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:13:34.367090   12511 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.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)

Validation Failed
W0924 19:13:47.100943   12511 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.large	4	4	ap-northeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)

Validation Failed
W0924 19:13:59.691302   12511 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.large	4	4	ap-northeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)

Validation Failed
W0924 19:14:12.274907   12511 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.large	4	4	ap-northeast-2a

... skipping 6 lines ...
ip-172-20-62-108.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)

Validation Failed
W0924 19:14:24.934656   12511 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.large	4	4	ap-northeast-2a

... skipping 6 lines ...
ip-172-20-62-108.ap-northeast-2.compute.internal	node	True

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)

Validation Failed
W0924 19:14:37.531038   12511 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.large	4	4	ap-northeast-2a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:14:50.635385   12511 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.large	4	4	ap-northeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:15:03.518832   12511 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.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:15:16.096064   12511 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.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:15:28.672419   12511 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.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:15:41.314691   12511 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.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:15:54.364335   12511 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.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)

Validation Failed
W0924 19:16:07.066604   12511 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.large	4	4	ap-northeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)

Validation Failed
W0924 19:16:19.715813   12511 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.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:16:32.481700   12511 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.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:16:45.257144   12511 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.large	4	4	ap-northeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:16:57.896916   12511 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.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:17:10.722969   12511 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.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:17:23.323489   12511 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.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:17:35.962648   12511 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.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:17:48.738772   12511 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.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:18:01.339748   12511 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.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:18:13.963914   12511 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.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:18:26.584454   12511 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.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:18:39.282219   12511 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.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:18:52.564903   12511 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.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:19:05.357525   12511 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.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)

Validation Failed
W0924 19:19:18.036339   12511 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.large	4	4	ap-northeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)

Validation Failed
W0924 19:19:30.727292   12511 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.large	4	4	ap-northeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)

Validation Failed
W0924 19:19:43.353983   12511 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.large	4	4	ap-northeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:19:56.081641   12511 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.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:20:08.793406   12511 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.large	4	4	ap-northeast-2a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:20:21.334903   12511 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.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:20:33.989603   12511 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.large	4	4	ap-northeast-2a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:20:46.634180   12511 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.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:20:59.236198   12511 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.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:21:11.869404   12511 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.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:21:24.473764   12511 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.large	4	4	ap-northeast-2a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-mhs4s	system-cluster-critical pod "coredns-5dc785954d-mhs4s" is not ready (coredns)
Pod	kube-system/ebs-csi-node-2chtt		system-node-critical pod "ebs-csi-node-2chtt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-ps4cz		system-node-critical pod "ebs-csi-node-ps4cz" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-stpzw		system-node-critical pod "ebs-csi-node-stpzw" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xkzcx		system-node-critical pod "ebs-csi-node-xkzcx" is not ready (ebs-plugin)

Validation Failed
W0924 19:21:37.095087   12511 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0924 19:21:47.101281    4851 dumplogs.go:40] /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops toolbox dump --name e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ubuntu
I0924 19:21:47.118859   12524 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 19:21:47.119162   12524 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/24 19:21:58 Dumping node ip-172-20-43-186.ap-northeast-2.compute.internal
2021/09/24 19:22:08 Dumping node ip-172-20-48-197.ap-northeast-2.compute.internal
2021/09/24 19:22:15 Dumping node ip-172-20-53-251.ap-northeast-2.compute.internal
... skipping 1437 lines ...
route-table:rtb-0f837cd5b9982eda3	ok
vpc:vpc-00222307e672d8523	ok
dhcp-options:dopt-02e5e603949a0b932	ok
Deleted kubectl config for e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io

Deleted cluster: "e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
Cleaning up after docker
Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die.
... skipping 3 lines ...