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 16:21
Elapsed24m58s
Revision9c6bf83c93a6af0b913e0a8d04e1f1d222153703
Refs 12394

No Test Failures!


Error lines from build-log.txt

... skipping 547 lines ...
Operation completed over 1 objects/153.0 B.                                      
I0924 16:25:58.655946    4856 copy.go:30] cp /home/prow/go/src/k8s.io/kops/bazel-bin/cmd/kops/linux-amd64/kops /logs/artifacts/5551e09d-1d53-11ec-bbe6-dab681da360c/kops
I0924 16:25:59.161184    4856 up.go:43] Cleaning up any leaked resources from previous cluster
I0924 16:25:59.161239    4856 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 16:25:59.188584   13009 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 16:25:59.188788   13009 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Error: Cluster.kops.k8s.io "e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io" not found
W0924 16:25:59.651188    4856 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0924 16:25:59.651270    4856 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 16:25:59.685441   13019 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 16:25:59.685588   13019 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 16:26:00.131160    4856 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/09/24 16:26:00 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 16:26:00.141006    4856 http.go:37] curl https://ip.jsb.workers.dev
I0924 16:26:00.227908    4856 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 35.202.128.122/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-1a --master-size c5.large
I0924 16:26:00.258003   13029 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 16:26:00.258091   13029 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
I0924 16:26:00.291795   13029 create_cluster.go:838] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I0924 16:26:00.779283   13029 new_cluster.go:1077]  Cloud Provider ID = aws
... skipping 31 lines ...

I0924 16:26:28.884275    4856 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 16:26:28.954341   13048 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 16:26:28.957120   13048 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-ffe10e9c76-2a8bf.test-cncf-aws.k8s.io

W0924 16:26:30.357099   13048 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-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:26:40.390916   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:26:50.427872   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:27:00.461138   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:27:10.499572   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:27:20.529437   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:27:30.560686   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:27:40.589030   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:27:50.624955   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:28:00.658482   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:28:10.703809   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:28:20.748851   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:28:30.780917   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
W0924 16:28:40.799831   13048 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-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:28:50.831330   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:29:00.871200   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:29:10.922981   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:29:20.956031   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:29:31.022396   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:29:41.052598   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:29:51.096421   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:30:01.130649   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:30:11.161236   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address.  The API DNS IP address is the placeholder address that kops creates: 203.0.113.123.  Please wait about 5-10 minutes for a master to start, dns-controller to launch, and DNS to propagate.  The protokube container and dns-controller deployment logs may contain more diagnostic information.  Etcd and the API DNS entries must be updated for a kops Kubernetes cluster to start.

Validation Failed
W0924 16:30:21.222551   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 7 lines ...
Machine	i-0641cb5ffe6265306				machine "i-0641cb5ffe6265306" has not yet joined cluster
Machine	i-06fbcfc595e336a57				machine "i-06fbcfc595e336a57" has not yet joined cluster
Machine	i-0ceb2c04f7f6546dc				machine "i-0ceb2c04f7f6546dc" has not yet joined cluster
Pod	kube-system/coredns-5dc785954d-wwhkh		system-cluster-critical pod "coredns-5dc785954d-wwhkh" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-nfw87	system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-nfw87" is pending

Validation Failed
W0924 16:30:34.885289   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 17 lines ...
Pod	kube-system/ebs-csi-node-xhjnh				system-node-critical pod "ebs-csi-node-xhjnh" is pending
Pod	kube-system/weave-net-d8rnt				system-node-critical pod "weave-net-d8rnt" is pending
Pod	kube-system/weave-net-rqhmj				system-node-critical pod "weave-net-rqhmj" is pending
Pod	kube-system/weave-net-tnkq2				system-node-critical pod "weave-net-tnkq2" is pending
Pod	kube-system/weave-net-xqtgr				system-node-critical pod "weave-net-xqtgr" is pending

Validation Failed
W0924 16:30:47.268221   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 11 lines ...
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is pending
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is pending
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is pending
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is pending
Pod	kube-system/weave-net-rqhmj		system-node-critical pod "weave-net-rqhmj" is pending

Validation Failed
W0924 16:30:59.695117   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 6 lines ...
ip-172-20-58-89.ap-northeast-1.compute.internal		node	True

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

Validation Failed
W0924 16:31:12.058362   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 6 lines ...
ip-172-20-58-89.ap-northeast-1.compute.internal		node	True

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

Validation Failed
W0924 16:31:24.473639   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 7 lines ...

VALIDATION ERRORS
KIND	NAME									MESSAGE
Pod	kube-system/coredns-5dc785954d-wwhkh					system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/kube-proxy-ip-172-20-58-239.ap-northeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-58-239.ap-northeast-1.compute.internal" is pending

Validation Failed
W0924 16:31:36.924330   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 6 lines ...
ip-172-20-58-89.ap-northeast-1.compute.internal		node	True

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

Validation Failed
W0924 16:31:49.420517   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 6 lines ...
ip-172-20-58-89.ap-northeast-1.compute.internal		node	True

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

Validation Failed
W0924 16:32:02.176398   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 6 lines ...
ip-172-20-58-89.ap-northeast-1.compute.internal		node	True

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

Validation Failed
W0924 16:32:14.646056   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 6 lines ...
ip-172-20-58-89.ap-northeast-1.compute.internal		node	True

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

Validation Failed
W0924 16:32:27.089099   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 7 lines ...

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

Validation Failed
W0924 16:32:39.670658   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

Validation Failed
W0924 16:32:52.042544   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

Validation Failed
W0924 16:33:04.506311   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 6 lines ...
ip-172-20-58-89.ap-northeast-1.compute.internal		node	True

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

Validation Failed
W0924 16:33:16.916274   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 6 lines ...
ip-172-20-58-89.ap-northeast-1.compute.internal		node	True

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

Validation Failed
W0924 16:33:29.230695   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 6 lines ...
ip-172-20-58-89.ap-northeast-1.compute.internal		node	True

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

Validation Failed
W0924 16:33:41.572928   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 6 lines ...
ip-172-20-58-89.ap-northeast-1.compute.internal		node	True

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

Validation Failed
W0924 16:33:53.905359   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 6 lines ...
ip-172-20-58-89.ap-northeast-1.compute.internal		node	True

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

Validation Failed
W0924 16:34:06.188575   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

Validation Failed
W0924 16:34:18.479265   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

Validation Failed
W0924 16:34:31.497276   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

Validation Failed
W0924 16:34:43.849241   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

Validation Failed
W0924 16:34:56.194236   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

Validation Failed
W0924 16:35:08.652232   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

Validation Failed
W0924 16:35:20.937967   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

Validation Failed
W0924 16:35:33.189973   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 6 lines ...
ip-172-20-58-89.ap-northeast-1.compute.internal		node	True

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

Validation Failed
W0924 16:35:45.533453   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 7 lines ...

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

Validation Failed
W0924 16:35:58.097023   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-northeast-1a	Master	c5.large	1	1	ap-northeast-1a
nodes-ap-northeast-1a	Node	t3.large	4	4	ap-northeast-1a

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 9 lines ...
KIND	NAME					MESSAGE
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 7 lines ...

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

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

... skipping 7 lines ...

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

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

... skipping 7 lines ...

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

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

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

... skipping 10 lines ...
Pod	kube-system/coredns-5dc785954d-wwhkh	system-cluster-critical pod "coredns-5dc785954d-wwhkh" is not ready (coredns)
Pod	kube-system/ebs-csi-node-4v9pt		system-node-critical pod "ebs-csi-node-4v9pt" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-8dzsn		system-node-critical pod "ebs-csi-node-8dzsn" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-hhtb6		system-node-critical pod "ebs-csi-node-hhtb6" is not ready (ebs-plugin)
Pod	kube-system/ebs-csi-node-xhjnh		system-node-critical pod "ebs-csi-node-xhjnh" is not ready (ebs-plugin)

Validation Failed
W0924 16:41:31.432044   13048 validate_cluster.go:232] (will retry): cluster not yet healthy
Error: Validation failed: wait time exceeded during validation
I0924 16:41:41.435819    4856 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 16:41:41.451355   13062 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true
I0924 16:41:41.451759   13062 featureflag.go:166] FeatureFlag "AlphaAllowGCE"=true
2021/09/24 16:41:52 Dumping node ip-172-20-35-215.ap-northeast-1.compute.internal
2021/09/24 16:41:59 Dumping node ip-172-20-45-136.ap-northeast-1.compute.internal
2021/09/24 16:42:07 Dumping node ip-172-20-48-226.ap-northeast-1.compute.internal
... skipping 1445 lines ...
route-table:rtb-08d592a8a51c25d18	ok
vpc:vpc-0e2ee77b57286a988	ok
dhcp-options:dopt-0360c8a16316c1b74	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 ...