This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-10-19 01:08
Elapsed20m21s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 131 lines ...
I1019 01:08:47.595878    4749 up.go:43] Cleaning up any leaked resources from previous cluster
I1019 01:08:47.595918    4749 dumplogs.go:40] /logs/artifacts/edcd1a5d-3078-11ec-a761-46851535a78f/kops toolbox dump --name e2e-05827c7fe4-99215.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1019 01:08:47.611744    4772 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1019 01:08:47.611925    4772 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

Cluster.kops.k8s.io "e2e-05827c7fe4-99215.test-cncf-aws.k8s.io" not found
W1019 01:08:48.151474    4749 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I1019 01:08:48.151583    4749 down.go:48] /logs/artifacts/edcd1a5d-3078-11ec-a761-46851535a78f/kops delete cluster --name e2e-05827c7fe4-99215.test-cncf-aws.k8s.io --yes
I1019 01:08:48.167785    4782 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1019 01:08:48.168208    4782 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true

error reading cluster configuration: Cluster.kops.k8s.io "e2e-05827c7fe4-99215.test-cncf-aws.k8s.io" not found
I1019 01:08:48.679913    4749 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2021/10/19 01:08:48 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
I1019 01:08:48.687673    4749 http.go:37] curl https://ip.jsb.workers.dev
I1019 01:08:48.778622    4749 up.go:144] /logs/artifacts/edcd1a5d-3078-11ec-a761-46851535a78f/kops create cluster --name e2e-05827c7fe4-99215.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.21.5 --ssh-public-key /etc/aws-ssh/aws-ssh-public --override cluster.spec.nodePortAccess=0.0.0.0/0 --yes --image=309956199498/RHEL-8.4.0_HVM-20210825-x86_64-0-Hourly2-GP2 --channel=alpha --networking=calico --container-runtime=containerd --admin-access 35.202.2.127/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-1a --master-size c5.large
I1019 01:08:48.793988    4791 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1019 01:08:48.794175    4791 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
I1019 01:08:48.835380    4791 create_cluster.go:728] Using SSH public key: /etc/aws-ssh/aws-ssh-public
I1019 01:08:49.330268    4791 new_cluster.go:1011]  Cloud Provider ID = aws
... skipping 42 lines ...

I1019 01:09:20.021563    4749 up.go:181] /logs/artifacts/edcd1a5d-3078-11ec-a761-46851535a78f/kops validate cluster --name e2e-05827c7fe4-99215.test-cncf-aws.k8s.io --count 10 --wait 15m0s
I1019 01:09:20.037914    4810 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1019 01:09:20.037992    4810 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
Validating cluster e2e-05827c7fe4-99215.test-cncf-aws.k8s.io

W1019 01:09:21.740173    4810 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-05827c7fe4-99215.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:09:31.771253    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:09:41.801518    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:09:51.837288    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:10:01.876234    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:10:11.907327    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:10:21.939243    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:10:31.971824    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:10:42.002399    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:10:52.030589    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:11:02.073061    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:11:12.112216    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:11:22.167428    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:11:32.203425    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:11:42.234250    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
W1019 01:11:52.269642    4810 validate_cluster.go:173] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-05827c7fe4-99215.test-cncf-aws.k8s.io on 10.63.240.10:53: no such host
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:12:02.300681    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:12:12.337101    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:12:22.369978    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:12:32.406887    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:12:42.439481    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:12:52.470164    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:13:02.503231    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:13:12.536141    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:13:22.594199    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:13:32.627830    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:13:42.659020    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:13:52.694570    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:14:02.727198    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:14:12.786491    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:14:22.834246    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:14:32.878144    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W1019 01:14:42.943770    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 9 lines ...
Machine	i-0f4dd6d5cc8d21176					machine "i-0f4dd6d5cc8d21176" has not yet joined cluster
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/calico-node-grhhz				system-node-critical pod "calico-node-grhhz" is pending
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vk8qp		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vk8qp" is pending

Validation Failed
W1019 01:14:57.730358    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 16 lines ...
Pod	kube-system/calico-node-grhhz				system-node-critical pod "calico-node-grhhz" is pending
Pod	kube-system/calico-node-kq7kw				system-node-critical pod "calico-node-kq7kw" is pending
Pod	kube-system/calico-node-lhw95				system-node-critical pod "calico-node-lhw95" is pending
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vk8qp		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vk8qp" is pending

Validation Failed
W1019 01:15:10.803065    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 14 lines ...
Pod	kube-system/calico-node-grhhz				system-node-critical pod "calico-node-grhhz" is not ready (calico-node)
Pod	kube-system/calico-node-kq7kw				system-node-critical pod "calico-node-kq7kw" is pending
Pod	kube-system/calico-node-lhw95				system-node-critical pod "calico-node-lhw95" is pending
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is pending
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vk8qp		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vk8qp" is pending

Validation Failed
W1019 01:15:23.913107    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 10 lines ...
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/calico-node-dn8m4				system-node-critical pod "calico-node-dn8m4" is not ready (calico-node)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is pending
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)
Pod	kube-system/coredns-autoscaler-84d4cfd89c-vk8qp		system-cluster-critical pod "coredns-autoscaler-84d4cfd89c-vk8qp" is pending

Validation Failed
W1019 01:15:37.196197    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 11 lines ...
Pod	kube-system/coredns-5dc785954d-kg544					system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt					system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)
Pod	kube-system/kube-proxy-ip-172-20-50-251.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-50-251.ap-southeast-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-60-172.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-60-172.ap-southeast-1.compute.internal" is pending
Pod	kube-system/kube-proxy-ip-172-20-60-249.ap-southeast-1.compute.internal	system-node-critical pod "kube-proxy-ip-172-20-60-249.ap-southeast-1.compute.internal" is pending

Validation Failed
W1019 01:15:50.407218    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:16:03.677883    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:16:17.472235    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:16:30.668102    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:16:44.344350    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:16:57.535759    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:17:10.816210    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:17:23.925884    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:17:37.242456    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:17:50.438707    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:18:03.788964    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:18:17.028516    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:18:30.208739    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:18:43.499952    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:18:57.373215    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:19:10.470473    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:19:23.630647    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:19:36.794355    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:19:49.953398    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:20:03.120818    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:20:16.361330    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:20:29.518258    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:20:42.704281    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:20:55.806724    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:21:09.073974    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:21:22.219879    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:21:35.514738    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:21:48.839298    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:22:01.927812    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:22:15.109196    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:22:28.209176    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:22:41.371417    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:22:55.180867    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:23:08.339344    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:23:21.556920    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:23:34.830740    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:23:48.025646    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:24:01.175273    4810 validate_cluster.go:221] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-ap-southeast-1a	Master	c5.large	1	1	ap-southeast-1a
nodes-ap-southeast-1a	Node	t3.medium	4	4	ap-southeast-1a

... skipping 8 lines ...
VALIDATION ERRORS
KIND	NAME							MESSAGE
Pod	kube-system/calico-kube-controllers-6b59cd85f8-vkh9x	system-cluster-critical pod "calico-kube-controllers-6b59cd85f8-vkh9x" is not ready (calico-kube-controllers)
Pod	kube-system/coredns-5dc785954d-kg544			system-cluster-critical pod "coredns-5dc785954d-kg544" is not ready (coredns)
Pod	kube-system/coredns-5dc785954d-zqclt			system-cluster-critical pod "coredns-5dc785954d-zqclt" is not ready (coredns)

Validation Failed
W1019 01:24:14.464778    4810 validate_cluster.go:221] (will retry): cluster not yet healthy

Validation failed: wait time exceeded during validation
I1019 01:24:24.478577    4749 dumplogs.go:40] /logs/artifacts/edcd1a5d-3078-11ec-a761-46851535a78f/kops toolbox dump --name e2e-05827c7fe4-99215.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /etc/aws-ssh/aws-ssh-private --ssh-user ec2-user
I1019 01:24:24.495241    4820 featureflag.go:165] FeatureFlag "SpecOverrideFlag"=true
I1019 01:24:24.495328    4820 featureflag.go:165] FeatureFlag "AlphaAllowGCE"=true
2021/10/19 01:24:38 Dumping node ip-172-20-41-13.ap-southeast-1.compute.internal
2021/10/19 01:24:47 Dumping node ip-172-20-50-251.ap-southeast-1.compute.internal
2021/10/19 01:24:54 Dumping node ip-172-20-58-148.ap-southeast-1.compute.internal
... skipping 1391 lines ...
route-table:rtb-023693b06fafcb59f	ok
vpc:vpc-092fdcc3c19938786	ok
dhcp-options:dopt-09a4e158afbc03261	ok
Deleted kubectl config for e2e-05827c7fe4-99215.test-cncf-aws.k8s.io

Deleted cluster: "e2e-05827c7fe4-99215.test-cncf-aws.k8s.io"
Error: exit status 1
+ EXIT_VALUE=1
+ set +o xtrace