This job view page is being replaced by Spyglass soon. Check out the new job view.
Resultsuccess
Tests 0 failed / 1 succeeded
Started2022-09-02 21:37
Elapsed1h0m
Revision
uploadercrier
uploadercrier

No Test Failures!


Show 1 Passed Tests

Error lines from build-log.txt

... skipping 222 lines ...
I0902 21:39:01.753013    6323 app.go:64] RunDir for this run: "/home/prow/go/src/k8s.io/kops/_rundir/62495366-2b07-11ed-8d6d-7af3f1cf7ce7"
I0902 21:39:01.761039    6323 app.go:128] ID for this run: "62495366-2b07-11ed-8d6d-7af3f1cf7ce7"
I0902 21:39:01.761327    6323 local.go:42] ⚙️ ssh-keygen -t ed25519 -N  -q -f /tmp/kops/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/id_ed25519
I0902 21:39:01.778591    6323 up.go:44] Cleaning up any leaked resources from previous cluster
I0902 21:39:01.778725    6323 dumplogs.go:45] /tmp/kops.lWyy6y1QA toolbox dump --name e2e-4342699135-9b4dd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
I0902 21:39:01.778752    6323 local.go:42] ⚙️ /tmp/kops.lWyy6y1QA toolbox dump --name e2e-4342699135-9b4dd.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ubuntu
W0902 21:39:02.363277    6323 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1
I0902 21:39:02.363351    6323 down.go:48] /tmp/kops.lWyy6y1QA delete cluster --name e2e-4342699135-9b4dd.test-cncf-aws.k8s.io --yes
I0902 21:39:02.363370    6323 local.go:42] ⚙️ /tmp/kops.lWyy6y1QA delete cluster --name e2e-4342699135-9b4dd.test-cncf-aws.k8s.io --yes
I0902 21:39:02.401404    6344 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0902 21:39:02.401523    6344 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-4342699135-9b4dd.test-cncf-aws.k8s.io" not found
I0902 21:39:02.920892    6323 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip
2022/09/02 21:39:02 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
I0902 21:39:02.935990    6323 http.go:37] curl https://ip.jsb.workers.dev
I0902 21:39:03.077589    6323 up.go:159] /tmp/kops.lWyy6y1QA create cluster --name e2e-4342699135-9b4dd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version v1.25.0 --ssh-public-key /tmp/kops/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --networking amazonvpc --set=cluster.spec.awsLoadBalancerController.enabled=true --set=cluster.spec.certManager.enabled=true --zones=eu-west-1a,eu-west-1b,eu-west-1c --discovery-store=s3://k8s-kops-prow/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/discovery --admin-access 34.134.251.70/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --master-size c5.large
I0902 21:39:03.077644    6323 local.go:42] ⚙️ /tmp/kops.lWyy6y1QA create cluster --name e2e-4342699135-9b4dd.test-cncf-aws.k8s.io --cloud aws --kubernetes-version v1.25.0 --ssh-public-key /tmp/kops/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --networking amazonvpc --set=cluster.spec.awsLoadBalancerController.enabled=true --set=cluster.spec.certManager.enabled=true --zones=eu-west-1a,eu-west-1b,eu-west-1c --discovery-store=s3://k8s-kops-prow/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/discovery --admin-access 34.134.251.70/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --master-size c5.large
I0902 21:39:03.113267    6357 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0902 21:39:03.113395    6357 featureflag.go:162] FeatureFlag "SpecOverrideFlag"=true
I0902 21:39:03.134019    6357 create_cluster.go:843] Using SSH public key: /tmp/kops/e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/id_ed25519.pub
... skipping 710 lines ...

NODE STATUS
NAME	ROLE	READY

VALIDATION ERRORS
KIND	NAME		MESSAGE
dns	apiserver	Validation Failed

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

Validation Failed
W0902 21:39:53.373155    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:40:03.421876    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:40:13.484672    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:40:23.523942    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:40:33.575071    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:40:43.626173    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:40:53.694988    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:41:03.751055    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:41:13.820189    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:41:23.865100    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:41:33.927356    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:41:43.987117    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:41:54.041242    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:42:04.086132    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:42:14.129759    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:42:24.226070    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:42:34.276182    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:42:44.346200    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:42:54.397418    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c

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
W0902 21:43:04.449579    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
W0902 21:43:44.508535    6399 validate_cluster.go:184] (will retry): unexpected error during validation: error listing nodes: Get "https://api.e2e-4342699135-9b4dd.test-cncf-aws.k8s.io/api/v1/nodes": dial tcp 203.0.113.123:443: i/o timeout
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
nodes-eu-west-1c	Node	t3.medium	1	1	eu-west-1c
... skipping 7 lines ...
i-0d7cd5dfbba35a035	node	True

VALIDATION ERRORS
KIND	NAME						MESSAGE
Pod	kube-system/ebs-csi-controller-575f78655f-ng6nj	system-cluster-critical pod "ebs-csi-controller-575f78655f-ng6nj" is pending

Validation Failed
W0902 21:44:00.898056    6399 validate_cluster.go:232] (will retry): cluster not yet healthy
INSTANCE GROUPS
NAME			ROLE	MACHINETYPE	MIN	MAX	SUBNETS
master-eu-west-1a	Master	c5.large	1	1	eu-west-1a
nodes-eu-west-1a	Node	t3.medium	2	2	eu-west-1a
nodes-eu-west-1b	Node	t3.medium	1	1	eu-west-1b
... skipping 371 lines ...
• [SLOW TEST] [234.913 seconds]
vanilla ingress tests with `alb.ingress.kubernetes.io/conditions.${conditions-name}` variant settings with annotation based conditions, one ALB shall be created and functional
/tmp/kops.HOJvR8YhE/test/e2e/ingress/vanilla_ingress_test.go:431
------------------------------

Ran 11 of 11 Specs in 2080.655 seconds
SUCCESS! -- 11 Passed | 0 Failed | 0 Pending | 0 Skipped
--- PASS: TestIngress (2080.66s)
PASS

Ginkgo ran 1 suite in 36m8.923975672s
Test Suite Passed
+ ginkgo -v -r test/e2e/service -- -cluster-name=e2e-4342699135-9b4dd.test-cncf-aws.k8s.io -aws-region=eu-west-1 -aws-vpc-id=vpc-0933a42c1f77625c2 -ginkgo.junit-report=/logs/artifacts/aws-lb-controller/junit-service.xml
... skipping 49 lines ...
• [SLOW TEST] [14.320 seconds]
k8s service reconciled by the aws load balancer NLB IP Load Balancer with name Should create and verify service
/tmp/kops.HOJvR8YhE/test/e2e/service/nlb_ip_target_test.go:348
------------------------------

Ran 6 of 8 Specs in 554.075 seconds
SUCCESS! -- 6 Passed | 0 Failed | 0 Pending | 2 Skipped
--- PASS: TestService (554.08s)
PASS

Ginkgo ran 1 suite in 9m26.756004113s
Test Suite Passed
+ kops-finish
... skipping 571 lines ...