e2e-kops-grid-cilium-rhel8-k22-docker #1593237873748873216
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 2 succeeded |
| Started | |
| Elapsed | 17m43s |
| Revision | master |
kubetest2 Down
kubetest2 Up
ERROR: (gcloud.auth.activate-service-account) There was a problem refreshing your current auth tokens: ('invalid_grant: Invalid JWT Signature.', {'error': 'invalid_grant', 'error_description': 'Invalid JWT Signature.'}) Please run: $ gcloud auth login to obtain new credentials. ... skipping 171 lines ... I1117 13:43:06.386857 6088 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/latest-ci-updown-green.txt I1117 13:43:06.389142 6088 http.go:37] curl https://storage.googleapis.com/kops-ci/bin/1.26.0-alpha.2+v1.26.0-alpha.1-348-gc592a02bb4/linux/amd64/kops I1117 13:43:07.596589 6088 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519 I1117 13:43:07.604032 6088 up.go:44] Cleaning up any leaked resources from previous cluster I1117 13:43:07.604124 6088 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/876362d5-667d-11ed-a804-ce2adf6da13d/kops toolbox dump --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user I1117 13:43:07.604139 6088 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/876362d5-667d-11ed-a804-ce2adf6da13d/kops toolbox dump --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user W1117 13:43:08.109709 6088 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I1117 13:43:08.109888 6088 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/876362d5-667d-11ed-a804-ce2adf6da13d/kops delete cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --yes I1117 13:43:08.109936 6088 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/876362d5-667d-11ed-a804-ce2adf6da13d/kops delete cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --yes I1117 13:43:08.141816 6123 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io" not found I1117 13:43:08.639278 6088 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2022/11/17 13:43:08 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 I1117 13:43:08.651149 6088 http.go:37] curl https://ip.jsb.workers.dev I1117 13:43:08.743174 6088 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/876362d5-667d-11ed-a804-ce2adf6da13d/kops create cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.16 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=309956199498/RHEL-8.7.0_HVM-20221101-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium --container-runtime=docker --admin-access 34.132.202.55/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-1a --master-size c5.large I1117 13:43:08.743217 6088 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/876362d5-667d-11ed-a804-ce2adf6da13d/kops create cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.22.16 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub --override cluster.spec.nodePortAccess=0.0.0.0/0 --image=309956199498/RHEL-8.7.0_HVM-20221101-x86_64-0-Hourly2-GP2 --channel=alpha --networking=cilium --container-runtime=docker --admin-access 34.132.202.55/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-southeast-1a --master-size c5.large I1117 13:43:08.775288 6133 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true I1117 13:43:08.793145 6133 create_cluster.go:836] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519.pub I1117 13:43:09.295531 6133 new_cluster.go:1294] Cloud Provider ID = aws ... skipping 541 lines ... I1117 13:44:00.201358 6088 up.go:251] /home/prow/go/src/k8s.io/kops/_rundir/876362d5-667d-11ed-a804-ce2adf6da13d/kops validate cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --count 10 --wait 15m0s I1117 13:44:00.201406 6088 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/876362d5-667d-11ed-a804-ce2adf6da13d/kops validate cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --count 10 --wait 15m0s I1117 13:44:00.235394 6173 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true Validating cluster e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io W1117 13:44:01.970568 6173 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e2e-kops-grid-cilium-rhel8-k22-docker.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 W1117 13:44:12.011442 6173 validate_cluster.go:232] (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 W1117 13:44:22.062167 6173 validate_cluster.go:232] (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 W1117 13:44:32.111348 6173 validate_cluster.go:232] (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 W1117 13:44:42.163813 6173 validate_cluster.go:232] (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 W1117 13:44:52.201473 6173 validate_cluster.go:232] (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 W1117 13:45:02.237204 6173 validate_cluster.go:232] (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 W1117 13:45:12.272803 6173 validate_cluster.go:232] (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 W1117 13:45:22.311195 6173 validate_cluster.go:232] (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 W1117 13:45:32.353483 6173 validate_cluster.go:232] (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 W1117 13:45:42.387677 6173 validate_cluster.go:232] (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 W1117 13:45:52.420893 6173 validate_cluster.go:232] (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 W1117 13:46:02.458292 6173 validate_cluster.go:232] (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 W1117 13:46:12.511874 6173 validate_cluster.go:232] (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 W1117 13:46:22.562003 6173 validate_cluster.go:232] (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 W1117 13:46:32.605834 6173 validate_cluster.go:232] (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 W1117 13:46:42.681786 6173 validate_cluster.go:232] (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 W1117 13:46:52.733996 6173 validate_cluster.go:232] (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 W1117 13:47:02.772441 6173 validate_cluster.go:232] (will retry): cluster not yet healthy W1117 13:47:12.798982 6173 validate_cluster.go:184] (will retry): unexpected error during validation: unable to resolve Kubernetes cluster API URL dns: lookup api.e2e-e2e-kops-grid-cilium-rhel8-k22-docker.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 W1117 13:47:22.834997 6173 validate_cluster.go:232] (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 W1117 13:47:32.873727 6173 validate_cluster.go:232] (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 W1117 13:47:42.911339 6173 validate_cluster.go:232] (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 W1117 13:47:52.961432 6173 validate_cluster.go:232] (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 W1117 13:48:03.015645 6173 validate_cluster.go:232] (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 W1117 13:48:13.065029 6173 validate_cluster.go:232] (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 W1117 13:48:23.113593 6173 validate_cluster.go:232] (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 W1117 13:48:33.157876 6173 validate_cluster.go:232] (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 W1117 13:48:43.197933 6173 validate_cluster.go:232] (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 W1117 13:48:53.237598 6173 validate_cluster.go:232] (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 W1117 13:49:03.283119 6173 validate_cluster.go:232] (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 W1117 13:49:13.338679 6173 validate_cluster.go:232] (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 W1117 13:49:23.391536 6173 validate_cluster.go:232] (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 W1117 13:49:33.424607 6173 validate_cluster.go:232] (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/cilium-dv7kx system-node-critical pod "cilium-dv7kx" is not ready (cilium-agent) Pod kube-system/coredns-5fcc7b6498-s84lf system-cluster-critical pod "coredns-5fcc7b6498-s84lf" is pending Pod kube-system/coredns-autoscaler-6658b4bf85-8mn8g system-cluster-critical pod "coredns-autoscaler-6658b4bf85-8mn8g" is pending Pod kube-system/ebs-csi-controller-7b65d9d67f-q7ffv system-cluster-critical pod "ebs-csi-controller-7b65d9d67f-q7ffv" is pending Pod kube-system/ebs-csi-node-jsqm7 system-node-critical pod "ebs-csi-node-jsqm7" is pending Validation Failed W1117 13:49:48.255217 6173 validate_cluster.go:232] (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-0f020652276d0bf61 machine "i-0f020652276d0bf61" has not yet joined cluster Pod kube-system/coredns-5fcc7b6498-s84lf system-cluster-critical pod "coredns-5fcc7b6498-s84lf" is pending Pod kube-system/coredns-autoscaler-6658b4bf85-8mn8g system-cluster-critical pod "coredns-autoscaler-6658b4bf85-8mn8g" is pending Pod kube-system/ebs-csi-controller-7b65d9d67f-q7ffv system-cluster-critical pod "ebs-csi-controller-7b65d9d67f-q7ffv" is pending Pod kube-system/ebs-csi-node-jsqm7 system-node-critical pod "ebs-csi-node-jsqm7" is pending Validation Failed W1117 13:50:01.736868 6173 validate_cluster.go:232] (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-0f020652276d0bf61 machine "i-0f020652276d0bf61" has not yet joined cluster Pod kube-system/coredns-5fcc7b6498-s84lf system-cluster-critical pod "coredns-5fcc7b6498-s84lf" is pending Pod kube-system/coredns-autoscaler-6658b4bf85-8mn8g system-cluster-critical pod "coredns-autoscaler-6658b4bf85-8mn8g" is pending Pod kube-system/ebs-csi-controller-7b65d9d67f-q7ffv system-cluster-critical pod "ebs-csi-controller-7b65d9d67f-q7ffv" is pending Pod kube-system/ebs-csi-node-jsqm7 system-node-critical pod "ebs-csi-node-jsqm7" is pending Validation Failed W1117 13:50:14.970462 6173 validate_cluster.go:232] (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 7 lines ... Machine i-0a48ffa6a138501e9 machine "i-0a48ffa6a138501e9" has not yet joined cluster Machine i-0d94a5fde265cd047 machine "i-0d94a5fde265cd047" has not yet joined cluster Machine i-0f020652276d0bf61 machine "i-0f020652276d0bf61" has not yet joined cluster Pod kube-system/coredns-5fcc7b6498-s84lf system-cluster-critical pod "coredns-5fcc7b6498-s84lf" is pending Pod kube-system/coredns-autoscaler-6658b4bf85-8mn8g system-cluster-critical pod "coredns-autoscaler-6658b4bf85-8mn8g" is pending Validation Failed W1117 13:50:28.175422 6173 validate_cluster.go:232] (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 7 lines ... Machine i-0a48ffa6a138501e9 machine "i-0a48ffa6a138501e9" has not yet joined cluster Machine i-0d94a5fde265cd047 machine "i-0d94a5fde265cd047" has not yet joined cluster Machine i-0f020652276d0bf61 machine "i-0f020652276d0bf61" has not yet joined cluster Pod kube-system/coredns-5fcc7b6498-s84lf system-cluster-critical pod "coredns-5fcc7b6498-s84lf" is pending Pod kube-system/coredns-autoscaler-6658b4bf85-8mn8g system-cluster-critical pod "coredns-autoscaler-6658b4bf85-8mn8g" is pending Validation Failed W1117 13:50:41.389197 6173 validate_cluster.go:232] (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 7 lines ... Machine i-0a48ffa6a138501e9 machine "i-0a48ffa6a138501e9" has not yet joined cluster Machine i-0d94a5fde265cd047 machine "i-0d94a5fde265cd047" has not yet joined cluster Machine i-0f020652276d0bf61 machine "i-0f020652276d0bf61" has not yet joined cluster Pod kube-system/coredns-5fcc7b6498-s84lf system-cluster-critical pod "coredns-5fcc7b6498-s84lf" is pending Pod kube-system/coredns-autoscaler-6658b4bf85-8mn8g system-cluster-critical pod "coredns-autoscaler-6658b4bf85-8mn8g" is pending Validation Failed W1117 13:50:54.703174 6173 validate_cluster.go:232] (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 7 lines ... Machine i-0a48ffa6a138501e9 machine "i-0a48ffa6a138501e9" has not yet joined cluster Machine i-0d94a5fde265cd047 machine "i-0d94a5fde265cd047" has not yet joined cluster Machine i-0f020652276d0bf61 machine "i-0f020652276d0bf61" has not yet joined cluster Pod kube-system/coredns-5fcc7b6498-s84lf system-cluster-critical pod "coredns-5fcc7b6498-s84lf" is pending Pod kube-system/coredns-autoscaler-6658b4bf85-8mn8g system-cluster-critical pod "coredns-autoscaler-6658b4bf85-8mn8g" is pending Validation Failed W1117 13:51:07.899257 6173 validate_cluster.go:232] (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 7 lines ... Machine i-0a48ffa6a138501e9 machine "i-0a48ffa6a138501e9" has not yet joined cluster Machine i-0d94a5fde265cd047 machine "i-0d94a5fde265cd047" has not yet joined cluster Machine i-0f020652276d0bf61 machine "i-0f020652276d0bf61" has not yet joined cluster Pod kube-system/coredns-5fcc7b6498-s84lf system-cluster-critical pod "coredns-5fcc7b6498-s84lf" is pending Pod kube-system/coredns-autoscaler-6658b4bf85-8mn8g system-cluster-critical pod "coredns-autoscaler-6658b4bf85-8mn8g" is pending Validation Failed W1117 13:51:21.156377 6173 validate_cluster.go:232] (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 7 lines ... Machine i-0a48ffa6a138501e9 machine "i-0a48ffa6a138501e9" has not yet joined cluster Machine i-0d94a5fde265cd047 machine "i-0d94a5fde265cd047" has not yet joined cluster Machine i-0f020652276d0bf61 machine "i-0f020652276d0bf61" has not yet joined cluster Pod kube-system/coredns-5fcc7b6498-s84lf system-cluster-critical pod "coredns-5fcc7b6498-s84lf" is pending Pod kube-system/coredns-autoscaler-6658b4bf85-8mn8g system-cluster-critical pod "coredns-autoscaler-6658b4bf85-8mn8g" is pending Validation Failed W1117 13:51:34.438036 6173 validate_cluster.go:232] (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 7 lines ... Machine i-0a48ffa6a138501e9 machine "i-0a48ffa6a138501e9" has not yet joined cluster Machine i-0d94a5fde265cd047 machine "i-0d94a5fde265cd047" has not yet joined cluster Machine i-0f020652276d0bf61 machine "i-0f020652276d0bf61" has not yet joined cluster Pod kube-system/coredns-5fcc7b6498-s84lf system-cluster-critical pod "coredns-5fcc7b6498-s84lf" is pending Pod kube-system/coredns-autoscaler-6658b4bf85-8mn8g system-cluster-critical pod "coredns-autoscaler-6658b4bf85-8mn8g" is pending Validation Failed W1117 13:51:47.737173 6173 validate_cluster.go:232] (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 7 lines ... Machine i-0a48ffa6a138501e9 machine "i-0a48ffa6a138501e9" has not yet joined cluster Machine i-0d94a5fde265cd047 machine "i-0d94a5fde265cd047" has not yet joined cluster Machine i-0f020652276d0bf61 machine "i-0f020652276d0bf61" has not yet joined cluster Pod kube-system/coredns-5fcc7b6498-s84lf system-cluster-critical pod "coredns-5fcc7b6498-s84lf" is pending Pod kube-system/coredns-autoscaler-6658b4bf85-8mn8g system-cluster-critical pod "coredns-autoscaler-6658b4bf85-8mn8g" is pending Validation Failed W1117 13:52:00.932260 6173 validate_cluster.go:232] (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-0f020652276d0bf61 machine "i-0f020652276d0bf61" has not yet joined cluster Pod kube-system/cilium-t5fgz system-node-critical pod "cilium-t5fgz" is pending Pod kube-system/coredns-5fcc7b6498-s84lf system-cluster-critical pod "coredns-5fcc7b6498-s84lf" is pending Pod kube-system/coredns-autoscaler-6658b4bf85-8mn8g system-cluster-critical pod "coredns-autoscaler-6658b4bf85-8mn8g" is pending Pod kube-system/ebs-csi-node-7dvd5 system-node-critical pod "ebs-csi-node-7dvd5" is pending Validation Failed W1117 13:52:14.210206 6173 validate_cluster.go:232] (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 ... Node ip-172-20-60-235.ap-southeast-1.compute.internal node "ip-172-20-60-235.ap-southeast-1.compute.internal" of role "node" is not ready Pod kube-system/cilium-t5fgz system-node-critical pod "cilium-t5fgz" is pending Pod kube-system/coredns-5fcc7b6498-s84lf system-cluster-critical pod "coredns-5fcc7b6498-s84lf" is pending Pod kube-system/coredns-autoscaler-6658b4bf85-8mn8g system-cluster-critical pod "coredns-autoscaler-6658b4bf85-8mn8g" is pending Pod kube-system/ebs-csi-node-7dvd5 system-node-critical pod "ebs-csi-node-7dvd5" is pending Validation Failed W1117 13:52:27.603004 6173 validate_cluster.go:232] (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/coredns-5fcc7b6498-s84lf system-cluster-critical pod "coredns-5fcc7b6498-s84lf" is pending Pod kube-system/coredns-autoscaler-6658b4bf85-8mn8g system-cluster-critical pod "coredns-autoscaler-6658b4bf85-8mn8g" is pending Pod kube-system/ebs-csi-node-79nnn system-node-critical pod "ebs-csi-node-79nnn" is pending Pod kube-system/ebs-csi-node-7dvd5 system-node-critical pod "ebs-csi-node-7dvd5" is pending Pod kube-system/ebs-csi-node-hl6gh system-node-critical pod "ebs-csi-node-hl6gh" is pending Validation Failed W1117 13:52:40.863841 6173 validate_cluster.go:232] (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 17 lines ... Pod kube-system/coredns-autoscaler-6658b4bf85-8mn8g system-cluster-critical pod "coredns-autoscaler-6658b4bf85-8mn8g" is pending Pod kube-system/ebs-csi-node-79nnn system-node-critical pod "ebs-csi-node-79nnn" is pending Pod kube-system/ebs-csi-node-7dvd5 system-node-critical pod "ebs-csi-node-7dvd5" is pending Pod kube-system/ebs-csi-node-hl6gh system-node-critical pod "ebs-csi-node-hl6gh" is pending Pod kube-system/ebs-csi-node-w777k system-node-critical pod "ebs-csi-node-w777k" is pending Validation Failed W1117 13:52:54.054932 6173 validate_cluster.go:232] (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 15 lines ... Pod kube-system/cilium-nrcsg system-node-critical pod "cilium-nrcsg" is not ready (cilium-agent) Pod kube-system/ebs-csi-node-79nnn system-node-critical pod "ebs-csi-node-79nnn" is pending Pod kube-system/ebs-csi-node-7dvd5 system-node-critical pod "ebs-csi-node-7dvd5" is pending Pod kube-system/ebs-csi-node-hl6gh system-node-critical pod "ebs-csi-node-hl6gh" is pending Pod kube-system/ebs-csi-node-w777k system-node-critical pod "ebs-csi-node-w777k" is pending Validation Failed W1117 13:53:07.326972 6173 validate_cluster.go:232] (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/ebs-csi-node-79nnn system-node-critical pod "ebs-csi-node-79nnn" is pending Pod kube-system/ebs-csi-node-hl6gh system-node-critical pod "ebs-csi-node-hl6gh" is pending Pod kube-system/ebs-csi-node-w777k system-node-critical pod "ebs-csi-node-w777k" is pending Validation Failed W1117 13:53:20.521738 6173 validate_cluster.go:232] (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 6 lines ... ip-172-20-60-235.ap-southeast-1.compute.internal node True VALIDATION ERRORS KIND NAME MESSAGE Pod kube-system/ebs-csi-node-w777k system-node-critical pod "ebs-csi-node-w777k" is pending Validation Failed W1117 13:53:33.831464 6173 validate_cluster.go:232] (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 141 lines ... ip-172-20-60-235.ap-southeast-1.compute.internal node True Your cluster e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io is ready I1117 13:55:47.446545 6088 up.go:105] cluster reported as up I1117 13:55:47.446627 6088 local.go:42] ⚙️ /home/prow/go/bin/kubetest2-tester-kops --ginkgo-args=--debug --test-args=-test.timeout=60m -num-nodes=0 --test-package-marker=stable-1.22.txt --parallel=25 I1117 13:55:47.465791 6184 featureflag.go:160] FeatureFlag "SpecOverrideFlag"=true F1117 13:55:49.886200 6184 tester.go:477] failed to run ginkgo tester: failed to get kubectl package from published releases: failed to get latest release name: exit status 1 I1117 13:55:49.889312 6088 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/876362d5-667d-11ed-a804-ce2adf6da13d/kops toolbox dump --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user I1117 13:55:49.889362 6088 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/876362d5-667d-11ed-a804-ce2adf6da13d/kops toolbox dump --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user I1117 13:57:05.624617 6088 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/876362d5-667d-11ed-a804-ce2adf6da13d/kops get cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io -o yaml I1117 13:57:05.624696 6088 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/876362d5-667d-11ed-a804-ce2adf6da13d/kops get cluster --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io -o yaml I1117 13:57:06.164547 6088 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/876362d5-667d-11ed-a804-ce2adf6da13d/kops get instancegroups --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io -o yaml I1117 13:57:06.164589 6088 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/876362d5-667d-11ed-a804-ce2adf6da13d/kops get instancegroups --name e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io -o yaml ... skipping 312 lines ... route-table:rtb-02e6e93d304132a04 ok vpc:vpc-0bf641f761b41a193 ok dhcp-options:dopt-0a6eb20419022cd7b ok Deleted kubectl config for e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io Deleted cluster: "e2e-e2e-kops-grid-cilium-rhel8-k22-docker.test-cncf-aws.k8s.io" Error: exit status 255 + EXIT_VALUE=1 + set +o xtrace