e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker #1610322013174370304
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 1 succeeded |
| Started | |
| Elapsed | 24m3s |
| Revision | master |
kubetest2 Down
... skipping 135 lines ... I0103 17:09:35.980726 5488 http.go:37] curl https://storage.googleapis.com/kops-ci/markers/release-1.26/latest-ci-updown-green.txt I0103 17:09:35.982748 5488 http.go:37] curl https://storage.googleapis.com/k8s-staging-kops/kops/releases/1.26.0-beta.2+v1.26.0-beta.1-20-gfeaf77e270/linux/amd64/kops I0103 17:09:37.909797 5488 local.go:42] ⚙️ ssh-keygen -t ed25519 -N -q -f /tmp/kops/e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io/id_ed25519 I0103 17:09:37.923720 5488 up.go:44] Cleaning up any leaked resources from previous cluster I0103 17:09:37.924012 5488 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/219c3d90-8b89-11ed-b47a-e2b55b2f9198/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user I0103 17:09:37.924145 5488 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/219c3d90-8b89-11ed-b47a-e2b55b2f9198/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user W0103 17:09:38.429020 5488 down.go:34] Dumping cluster logs at the start of Down() failed: exit status 1 I0103 17:09:38.429072 5488 down.go:48] /home/prow/go/src/k8s.io/kops/_rundir/219c3d90-8b89-11ed-b47a-e2b55b2f9198/kops delete cluster --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io --yes I0103 17:09:38.429083 5488 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/219c3d90-8b89-11ed-b47a-e2b55b2f9198/kops delete cluster --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io --yes I0103 17:09:38.469006 5516 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true Error: error reading cluster configuration: Cluster.kops.k8s.io "e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io" not found I0103 17:09:38.946053 5488 http.go:37] curl http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/access-configs/0/external-ip 2023/01/03 17:09:38 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 I0103 17:09:38.961733 5488 http.go:37] curl https://ip.jsb.workers.dev I0103 17:09:39.051090 5488 up.go:167] /home/prow/go/src/k8s.io/kops/_rundir/219c3d90-8b89-11ed-b47a-e2b55b2f9198/kops create cluster --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.23.15 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io/id_ed25519.pub --set 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-eni --container-runtime=docker --admin-access 34.173.43.36/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-1a --master-size c5.large I0103 17:09:39.051138 5488 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/219c3d90-8b89-11ed-b47a-e2b55b2f9198/kops create cluster --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io --cloud aws --kubernetes-version https://storage.googleapis.com/kubernetes-release/release/v1.23.15 --ssh-public-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io/id_ed25519.pub --set 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-eni --container-runtime=docker --admin-access 34.173.43.36/32 --master-count 1 --master-volume-size 48 --node-count 4 --node-volume-size 48 --zones ap-northeast-1a --master-size c5.large I0103 17:09:39.086927 5526 featureflag.go:166] FeatureFlag "SpecOverrideFlag"=true I0103 17:09:39.104659 5526 create_cluster.go:878] Using SSH public key: /tmp/kops/e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io/id_ed25519.pub I0103 17:09:39.587833 5526 new_cluster.go:1338] Cloud Provider ID: "aws" ... skipping 569 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 control plane node 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 W0103 17:13:39.547988 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:13:49.588655 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:13:59.626442 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:14:09.667753 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:14:19.745147 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:14:29.784939 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:14:39.821795 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:14:49.858454 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:14:59.893935 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:15:09.929735 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:15:19.976792 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:15:30.020074 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:15:40.073411 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:15:50.115034 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:16:00.165059 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:16:10.204232 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:16:20.248976 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:16:30.287326 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:16:40.330432 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:16:50.368071 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:17:00.419341 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:17:10.455430 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:17:20.497432 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:17:30.549790 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:17:40.593082 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:17:50.636248 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:18:00.678040 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:18:10.726835 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:18:20.771203 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:18:30.809264 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a NODE STATUS NAME ROLE READY VALIDATION ERRORS KIND NAME MESSAGE dns apiserver Validation Failed The dns-controller Kubernetes deployment has not updated the Kubernetes cluster's API DNS entry to the correct IP address. The API DNS IP address is the placeholder address that kops creates: 203.0.113.123. Please wait about 5-10 minutes for a control plane node 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 W0103 17:18:40.844949 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 10 lines ... Pod kube-system/cilium-xln7x system-node-critical pod "cilium-xln7x" is not ready (cilium-agent) Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Pod kube-system/ebs-csi-controller-6f67b79f49-dfvz2 system-cluster-critical pod "ebs-csi-controller-6f67b79f49-dfvz2" is pending Pod kube-system/ebs-csi-node-fl86t system-node-critical pod "ebs-csi-node-fl86t" is pending Validation Failed W0103 17:18:54.605328 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 10 lines ... Pod kube-system/cilium-xln7x system-node-critical pod "cilium-xln7x" is not ready (cilium-agent) Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Pod kube-system/ebs-csi-controller-6f67b79f49-dfvz2 system-cluster-critical pod "ebs-csi-controller-6f67b79f49-dfvz2" is pending Pod kube-system/ebs-csi-node-fl86t system-node-critical pod "ebs-csi-node-fl86t" is pending Validation Failed W0103 17:19:09.483853 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 9 lines ... Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Pod kube-system/ebs-csi-controller-6f67b79f49-dfvz2 system-cluster-critical pod "ebs-csi-controller-6f67b79f49-dfvz2" is pending Pod kube-system/ebs-csi-node-fl86t system-node-critical pod "ebs-csi-node-fl86t" is pending Validation Failed W0103 17:19:22.114838 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 8 lines ... Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Pod kube-system/ebs-csi-controller-6f67b79f49-dfvz2 system-cluster-critical pod "ebs-csi-controller-6f67b79f49-dfvz2" is pending Validation Failed W0103 17:19:34.631427 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:19:47.165359 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:19:59.711562 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:20:12.390717 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:20:25.026015 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:20:37.537290 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:20:50.010474 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:21:02.582147 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:21:15.069836 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:21:27.675867 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:21:40.283675 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:21:53.036873 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:22:05.689701 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:22:18.146935 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:22:30.646472 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:22:43.145257 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:22:56.097937 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:23:08.701270 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:23:21.360932 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:23:33.980499 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:23:46.746423 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:23:59.322149 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:24:12.011212 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:24:24.527676 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:24:37.176914 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:24:49.661077 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:25:02.269139 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:25:14.733305 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:25:27.314495 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:25:39.962057 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:25:52.562360 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:26:05.139484 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:26:17.697288 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:26:30.395151 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:26:43.064093 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:26:56.169492 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:27:08.724348 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:27:21.241537 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:27:33.929552 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:27:46.641819 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:27:59.300017 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:28:11.809286 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:28:24.486239 5566 validate_cluster.go:232] (will retry): cluster not yet healthy INSTANCE GROUPS NAME ROLE MACHINETYPE MIN MAX SUBNETS control-plane-ap-northeast-1a ControlPlane c5.large 1 1 ap-northeast-1a nodes-ap-northeast-1a Node t3.medium 4 4 ap-northeast-1a ... skipping 7 lines ... Machine i-0885df6b3d183d05f machine "i-0885df6b3d183d05f" has not yet joined cluster Machine i-0bbcaba505fe9d5b1 machine "i-0bbcaba505fe9d5b1" has not yet joined cluster Machine i-0c9abb0b367b2f9b0 machine "i-0c9abb0b367b2f9b0" has not yet joined cluster Pod kube-system/coredns-867df8f45c-ggrlv system-cluster-critical pod "coredns-867df8f45c-ggrlv" is pending Pod kube-system/coredns-autoscaler-557ccb4c66-9zlp8 system-cluster-critical pod "coredns-autoscaler-557ccb4c66-9zlp8" is pending Validation Failed W0103 17:28:37.168223 5566 validate_cluster.go:232] (will retry): cluster not yet healthy Error: validation failed: wait time exceeded during validation I0103 17:28:47.174550 5488 dumplogs.go:45] /home/prow/go/src/k8s.io/kops/_rundir/219c3d90-8b89-11ed-b47a-e2b55b2f9198/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user I0103 17:28:47.174623 5488 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/219c3d90-8b89-11ed-b47a-e2b55b2f9198/kops toolbox dump --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io --dir /logs/artifacts --private-key /tmp/kops/e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io/id_ed25519 --ssh-user ec2-user I0103 17:29:47.899428 5488 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/219c3d90-8b89-11ed-b47a-e2b55b2f9198/kops get cluster --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io -o yaml I0103 17:29:47.899522 5488 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/219c3d90-8b89-11ed-b47a-e2b55b2f9198/kops get cluster --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io -o yaml I0103 17:29:48.398352 5488 dumplogs.go:78] /home/prow/go/src/k8s.io/kops/_rundir/219c3d90-8b89-11ed-b47a-e2b55b2f9198/kops get instancegroups --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io -o yaml I0103 17:29:48.398398 5488 local.go:42] ⚙️ /home/prow/go/src/k8s.io/kops/_rundir/219c3d90-8b89-11ed-b47a-e2b55b2f9198/kops get instancegroups --name e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io -o yaml ... skipping 316 lines ... route-table:rtb-0a958df070ce79a59 ok vpc:vpc-0dca29227e6779594 ok dhcp-options:dopt-0f7fe259e343a89c5 ok Deleted kubectl config for e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io Deleted cluster: "e2e-e2e-kops-grid-cilium-eni-rhel8-k23-ko26-docker.test-cncf-aws.k8s.io" Error: exit status 1 + EXIT_VALUE=1 + set +o xtrace