{"tests":[{"name":"cl.etcd-member.discovery","result":"PASS","duration":155577694515,"output":""},{"name":"cl.flannel.vxlan","result":"PASS","duration":171290814206,"output":" flannel.go:121: ping from 99022626(10.254.66.0) to 99022627(10.254.40.0)\n"},{"name":"kubeadm.v1.36.1.cilium.base/node_readiness","result":"PASS","duration":18977679149,"output":""},{"name":"kubeadm.v1.36.1.flannel.base/node_readiness","result":"PASS","duration":6984424090,"output":""},{"name":"kubeadm.v1.36.1.cilium.base/nginx_deployment","result":"PASS","duration":7981831757,"output":""},{"name":"kubeadm.v1.36.1.flannel.base/nginx_deployment","result":"PASS","duration":7977702842,"output":""},{"name":"kubeadm.v1.36.1.cilium.base/NFS_deployment","result":"PASS","duration":16561589561,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.36.1.flannel.base/NFS_deployment","result":"PASS","duration":16373855128,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.36.1.flannel.base","result":"PASS","duration":462246148654,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0\n cluster.go:125: [init] Using Kubernetes version: v1.36.1\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [172-236-127-201 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 172.236.127.201]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 1.96848ms\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://172.236.127.201:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 8.17851ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 13.05644ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 1.50127381s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node 172-236-127-201 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node 172-236-127-201 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: q69iic.mi0hy3ergdcz52w5\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 172.236.127.201:6443 --token q69iic.mi0hy3ergdcz52w5 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:6507e3fe639a752df4d5d02c6d6b44da04961b5ef23dad58988454e7aecedd9e \n cluster.go:125: namespace/kube-flannel created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created\n cluster.go:125: serviceaccount/flannel created\n cluster.go:125: configmap/kube-flannel-cfg created\n cluster.go:125: daemonset.apps/kube-flannel-ds created\n cluster.go:125: W0612 00:08:27.594038 1804 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: W0612 00:08:27.787593 1804 utils.go:69] The recommended value for \"bindAddress\" in \"KubeProxyConfiguration\" is: ::; the provided value is: 0.0.0.0\n --- PASS: kubeadm.v1.36.1.flannel.base/node_readiness (6.98s)\n --- PASS: kubeadm.v1.36.1.flannel.base/nginx_deployment (7.98s)\n --- PASS: kubeadm.v1.36.1.flannel.base/NFS_deployment (16.37s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.35.1.calico.base/node_readiness","result":"PASS","duration":13088829165,"output":""},{"name":"kubeadm.v1.36.1.cilium.base/IPSec_encryption","result":"PASS","duration":20951675916,"output":" cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"kubeadm.v1.36.1.cilium.base","result":"PASS","duration":479231777672,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0\n cluster.go:125: [init] Using Kubernetes version: v1.36.1\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [172-236-127-243 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 172.236.127.243]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 1.354466ms\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://172.236.127.243:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 8.054645ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 17.715766ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 1.502953466s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node 172-236-127-243 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node 172-236-127-243 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: s8tysn.dfth4ajbaapgy0m1\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 172.236.127.243:6443 --token s8tysn.dfth4ajbaapgy0m1 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:f463b170c3e12e9fe28204b831118ff01fed84f007f6fdaa79501c5593873c90 \n cluster.go:125: i Using Cilium version 1.12.5\n cluster.go:125: ? Auto-detected cluster name: kubernetes\n cluster.go:125: ? Auto-detected datapath mode: tunnel\n cluster.go:125: ? Auto-detected kube-proxy has been installed\n cluster.go:125: i helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan\n cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret\n cluster.go:125: ? Created CA in secret cilium-ca\n cluster.go:125: ? Generating certificates for Hubble...\n cluster.go:125: ? Creating Service accounts...\n cluster.go:125: ? Creating Cluster roles...\n cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5...\n cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17\n cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true\n cluster.go:125: ? Creating Agent DaemonSet...\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: ? Creating Operator Deployment...\n cluster.go:125: ? Waiting for Cilium to be installed and ready...\n cluster.go:125: ? Cilium was successfully installed! Run 'cilium status' to view installation health\n cluster.go:125: \u001b[33m /??\\\n cluster.go:125: \u001b[36m /??\u001b[33m\\__/\u001b[32m??\\\u001b[0m Cilium: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[36m \\__\u001b[31m/??\\\u001b[32m__/\u001b[0m Operator: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[32m /??\u001b[31m\\__/\u001b[35m??\\\u001b[0m Hubble: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[32m \\__\u001b[34m/??\\\u001b[35m__/\u001b[0m ClusterMesh: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[34m \\__/\n cluster.go:125: \u001b[0m\n cluster.go:125: DaemonSet cilium \n cluster.go:125: Deployment cilium-operator \n cluster.go:125: Containers: cilium \n cluster.go:125: cilium-operator \n cluster.go:125: Cluster Pods: 0/0 managed by Cilium\n cluster.go:125: W0612 00:08:11.423215 1856 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: W0612 00:08:11.642987 1856 utils.go:69] The recommended value for \"bindAddress\" in \"KubeProxyConfiguration\" is: ::; the provided value is: 0.0.0.0\n --- PASS: kubeadm.v1.36.1.cilium.base/node_readiness (18.98s)\n --- PASS: kubeadm.v1.36.1.cilium.base/nginx_deployment (7.98s)\n --- PASS: kubeadm.v1.36.1.cilium.base/NFS_deployment (16.56s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n --- PASS: kubeadm.v1.36.1.cilium.base/IPSec_encryption (20.95s)\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"kubeadm.v1.35.1.calico.base/nginx_deployment","result":"PASS","duration":8072099391,"output":""},{"name":"kubeadm.v1.35.1.calico.base/NFS_deployment","result":"PASS","duration":16938769932,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.35.1.calico.base","result":"PASS","duration":499407377555,"output":" cluster.go:125: I0612 00:05:53.413518 2080 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0\n cluster.go:125: I0612 00:06:01.976617 2292 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.5\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [172-236-127-145 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 172.236.127.145]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 501.856761ms\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://172.236.127.145:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 1.507330747s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 2.211599762s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.503103643s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node 172-236-127-145 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node 172-236-127-145 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 7rk8cx.cu61w910bhmtcx0x\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 172.236.127.145:6443 --token 7rk8cx.cu61w910bhmtcx0x \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:106e47f90853ad1724c76eb51b04efb289f6c22b2313f0417ac22ed9e023a51a \n cluster.go:125: namespace/tigera-operator created\n cluster.go:125: serviceaccount/tigera-operator created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: deployment.apps/tigera-operator created\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: installation.operator.tigera.io/default created\n cluster.go:125: apiserver.operator.tigera.io/default created\n cluster.go:125: goldmane.operator.tigera.io/default created\n cluster.go:125: whisker.operator.tigera.io/default created\n cluster.go:125: W0612 00:08:58.219304 1855 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n --- PASS: kubeadm.v1.35.1.calico.base/node_readiness (13.09s)\n --- PASS: kubeadm.v1.35.1.calico.base/nginx_deployment (8.07s)\n --- PASS: kubeadm.v1.35.1.calico.base/NFS_deployment (16.94s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"coreos.ignition.once","result":"PASS","duration":231394191866,"output":""},{"name":"cl.install.cloudinit","result":"PASS","duration":131492075936,"output":""},{"name":"cl.internet/UpdateEngine","result":"PASS","duration":956377573,"output":""},{"name":"cl.internet/DockerPing","result":"PASS","duration":5862727720,"output":""},{"name":"cl.internet/DockerEcho","result":"PASS","duration":1185662525,"output":""},{"name":"cl.internet/NTPDate","result":"PASS","duration":7754681311,"output":""},{"name":"cl.internet","result":"PASS","duration":152725366999,"output":" --- PASS: cl.internet/UpdateEngine (0.96s)\n --- PASS: cl.internet/DockerPing (5.86s)\n --- PASS: cl.internet/DockerEcho (1.19s)\n --- PASS: cl.internet/NTPDate (7.75s)\n"},{"name":"cl.flannel.udp","result":"PASS","duration":226628743310,"output":" cluster.go:125: Timeout occurred while waiting for network connectivity.\n flannel.go:121: ping from 99022826(10.254.65.0) to 99022824(10.254.30.1)\n"},{"name":"cl.network.initramfs.second-boot","result":"PASS","duration":199036322658,"output":""},{"name":"cl.ignition.kargs","result":"PASS","duration":239108114585,"output":" cluster.go:152: + cat /proc/cmdline\n"},{"name":"linux.nfs.v4","result":"PASS","duration":276283615719,"output":" nfs.go:80: NFS server booted.\n nfs.go:85: Test file \"/tmp/tmp.oq5QIbHo0F\" created on server.\n nfs.go:125: NFS client booted.\n nfs.go:133: Got NFS mount.\n"},{"name":"coreos.ignition.resource.remote","result":"PASS","duration":142453639151,"output":""},{"name":"coreos.ignition.resource.local","result":"PASS","duration":282807940319,"output":""},{"name":"coreos.ignition.security.tls","result":"PASS","duration":293133588231,"output":""},{"name":"kubeadm.v1.36.1.calico.base/node_readiness","result":"PASS","duration":18977489572,"output":""},{"name":"kubeadm.v1.36.1.calico.base/nginx_deployment","result":"PASS","duration":7962891675,"output":""},{"name":"kubeadm.v1.36.1.calico.base/NFS_deployment","result":"PASS","duration":16635855576,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.36.1.calico.base","result":"PASS","duration":462799008693,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.14.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.8-0\n cluster.go:125: [init] Using Kubernetes version: v1.36.1\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [172-237-157-101 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 172.237.157.101]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 1.430858ms\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://172.237.157.101:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 4.958263ms\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 5.644692ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 1.502183067s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node 172-237-157-101 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node 172-237-157-101 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: ck6g8x.yqf9nkhax0rnrnrh\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the API server kubelet client certificate to access the kubelet API\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 172.237.157.101:6443 --token ck6g8x.yqf9nkhax0rnrnrh \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:11dc7d86e58c18a7ad9868a69b840d8e802913fcf83813cecfb6250fc5811a02 \n cluster.go:125: namespace/tigera-operator created\n cluster.go:125: serviceaccount/tigera-operator created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: deployment.apps/tigera-operator created\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: installation.operator.tigera.io/default created\n cluster.go:125: apiserver.operator.tigera.io/default created\n cluster.go:125: goldmane.operator.tigera.io/default created\n cluster.go:125: whisker.operator.tigera.io/default created\n cluster.go:125: W0612 00:20:21.891165 1850 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: W0612 00:20:22.170459 1850 utils.go:69] The recommended value for \"bindAddress\" in \"KubeProxyConfiguration\" is: ::; the provided value is: 0.0.0.0\n --- PASS: kubeadm.v1.36.1.calico.base/node_readiness (18.98s)\n --- PASS: kubeadm.v1.36.1.calico.base/nginx_deployment (7.96s)\n --- PASS: kubeadm.v1.36.1.calico.base/NFS_deployment (16.64s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"coreos.ignition.sethostname","result":"PASS","duration":123487007438,"output":""},{"name":"docker.network-openbsd-nc","result":"PASS","duration":147018374767,"output":" docker.go:413: creating netcat containers\n cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 3.69MB 0.1s done\n cluster.go:125: #3 DONE 0.1s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.0s done\n cluster.go:125: #5 writing image sha256:0ea775e258b94a0b0a91d32d2c90ee64c0623a72abee99d4cbe17442322efc51 done\n cluster.go:125: #5 naming to docker.io/library/netcat done\n cluster.go:125: #5 DONE 0.0s\n cluster.go:125: #0 building with \"default\" instance using docker driver\n cluster.go:125: \n cluster.go:125: #1 [internal] load build definition from Dockerfile\n cluster.go:125: #1 transferring dockerfile: 108B done\n cluster.go:125: #1 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context: 2B done\n cluster.go:125: #2 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #3 [internal] load build context\n cluster.go:125: #3 transferring context: 3.69MB 0.0s done\n cluster.go:125: #3 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #4 [1/1] COPY . /\n cluster.go:125: #4 DONE 0.0s\n cluster.go:125: \n cluster.go:125: #5 exporting to image\n cluster.go:125: #5 exporting layers 0.0s done\n cluster.go:125: #5 writing image sha256:9194a4a438e0616a84d5d4b3e39b6512b2e526a16ac96a471deaa68d8d8759e1\n cluster.go:125: #5 writing image sha256:9194a4a438e0616a84d5d4b3e39b6512b2e526a16ac96a471deaa68d8d8759e1 done\n cluster.go:125: #5 naming to docker.io/library/netcat done\n cluster.go:125: #5 DONE 0.0s\n"},{"name":"cl.ignition.v2.btrfsroot","result":"PASS","duration":130453419150,"output":""},{"name":"cl.basic/ServicesActive","result":"PASS","duration":977981496,"output":""},{"name":"cl.basic/ReadOnly","result":"PASS","duration":954284488,"output":""},{"name":"cl.basic/RandomUUID","result":"PASS","duration":988247683,"output":""},{"name":"cl.basic/Useradd","result":"PASS","duration":1089461443,"output":""},{"name":"cl.basic/MachineID","result":"PASS","duration":951379965,"output":""},{"name":"cl.basic/CloudConfig","result":"PASS","duration":1347575501,"output":""},{"name":"cl.basic/Script","result":"PASS","duration":1009332079,"output":""},{"name":"cl.basic/DbusPerms","result":"PASS","duration":1008952871,"output":""},{"name":"cl.basic/SymlinkFlatcar","result":"PASS","duration":965827301,"output":""},{"name":"cl.basic/UpdateEngineKeys","result":"PASS","duration":960266736,"output":""},{"name":"cl.basic/Microcode","result":"PASS","duration":976932948,"output":""},{"name":"cl.basic/PortSSH","result":"PASS","duration":949112754,"output":""},{"name":"cl.basic/Symlink","result":"PASS","duration":956878569,"output":""},{"name":"cl.basic","result":"PASS","duration":127521624362,"output":" --- PASS: cl.basic/ServicesActive (0.98s)\n --- PASS: cl.basic/ReadOnly (0.95s)\n --- PASS: cl.basic/RandomUUID (0.99s)\n --- PASS: cl.basic/Useradd (1.09s)\n --- PASS: cl.basic/MachineID (0.95s)\n --- PASS: cl.basic/CloudConfig (1.35s)\n --- PASS: cl.basic/Script (1.01s)\n --- PASS: cl.basic/DbusPerms (1.01s)\n --- PASS: cl.basic/SymlinkFlatcar (0.97s)\n --- PASS: cl.basic/UpdateEngineKeys (0.96s)\n --- PASS: cl.basic/Microcode (0.98s)\n --- PASS: cl.basic/PortSSH (0.95s)\n --- PASS: cl.basic/Symlink (0.96s)\n"},{"name":"kubeadm.v1.35.1.flannel.base/node_readiness","result":"PASS","duration":7000747356,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/nginx_deployment","result":"PASS","duration":8016123128,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/NFS_deployment","result":"PASS","duration":16587304491,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.35.1.flannel.base","result":"PASS","duration":449634586040,"output":" cluster.go:125: I0612 00:21:56.856539 2035 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0\n cluster.go:125: I0612 00:22:05.023673 2243 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.5\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [172-233-211-107 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 172.233.211.107]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 501.279761ms\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://172.233.211.107:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 1.505189495s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 1.909578159s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.502007184s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node 172-233-211-107 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node 172-233-211-107 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: ejlwyd.vb9da30kkjkwtmgl\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 172.233.211.107:6443 --token ejlwyd.vb9da30kkjkwtmgl \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:5e135fd23c41f0b9605ab2a4d03a99d20eeb3796a85232d7e60ac5b6a8e0cc48 \n cluster.go:125: namespace/kube-flannel created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created\n cluster.go:125: serviceaccount/flannel created\n cluster.go:125: configmap/kube-flannel-cfg created\n cluster.go:125: daemonset.apps/kube-flannel-ds created\n cluster.go:125: W0612 00:24:28.064064 1803 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n --- PASS: kubeadm.v1.35.1.flannel.base/node_readiness (7.00s)\n --- PASS: kubeadm.v1.35.1.flannel.base/nginx_deployment (8.02s)\n --- PASS: kubeadm.v1.35.1.flannel.base/NFS_deployment (16.59s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"linux.nfs.v3","result":"PASS","duration":273014019054,"output":" nfs.go:80: NFS server booted.\n nfs.go:85: Test file \"/tmp/tmp.enrQNrKsbM\" created on server.\n nfs.go:125: NFS client booted.\n nfs.go:133: Got NFS mount.\n"},{"name":"kubeadm.v1.35.1.cilium.base/node_readiness","result":"PASS","duration":13045032292,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/nginx_deployment","result":"PASS","duration":8022932671,"output":""},{"name":"kubeadm.v1.35.1.cilium.base/NFS_deployment","result":"PASS","duration":16562005329,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.35.1.cilium.base/IPSec_encryption","result":"PASS","duration":20208062251,"output":" cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"coreos.ignition.ssh.key","result":"PASS","duration":136592314427,"output":""},{"name":"kubeadm.v1.35.1.cilium.base","result":"PASS","duration":455904789715,"output":" cluster.go:125: I0612 00:26:45.272401 2080 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.5\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.13.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.6-0\n cluster.go:125: I0612 00:26:53.087002 2291 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.5\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [172-237-135-129 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 172.237.135.129]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 501.39203ms\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://172.237.135.129:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 1.50764202s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 2.08738329s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.50136784s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node 172-237-135-129 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node 172-237-135-129 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 1o8pw0.jd5coyhihmlwdy5t\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 172.237.135.129:6443 --token 1o8pw0.jd5coyhihmlwdy5t \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:f2d65cf058bf495d53ef67a2686499399bcb0b28c3a218ef73ddb6ad9d71d8e2 \n cluster.go:125: i Using Cilium version 1.12.5\n cluster.go:125: ? Auto-detected cluster name: kubernetes\n cluster.go:125: ? Auto-detected datapath mode: tunnel\n cluster.go:125: ? Auto-detected kube-proxy has been installed\n cluster.go:125: i helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan\n cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret\n cluster.go:125: ? Created CA in secret cilium-ca\n cluster.go:125: ? Generating certificates for Hubble...\n cluster.go:125: ? Creating Service accounts...\n cluster.go:125: ? Creating Cluster roles...\n cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5...\n cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true\n cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17\n cluster.go:125: ? Creating Agent DaemonSet...\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: ? Creating Operator Deployment...\n cluster.go:125: ? Waiting for Cilium to be installed and ready...\n cluster.go:125: ? Cilium was successfully installed! Run 'cilium status' to view installation health\n cluster.go:125: \u001b[33m /??\\\n cluster.go:125: \u001b[36m /??\u001b[33m\\__/\u001b[32m??\\\u001b[0m Cilium: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[36m \\__\u001b[31m/??\\\u001b[32m__/\u001b[0m Operator: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[32m /??\u001b[31m\\__/\u001b[35m??\\\u001b[0m Hubble: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[32m \\__\u001b[34m/??\\\u001b[35m__/\u001b[0m ClusterMesh: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[34m \\__/\n cluster.go:125: \u001b[0m\n cluster.go:125: DaemonSet cilium \n cluster.go:125: Deployment cilium-operator \n cluster.go:125: Containers: cilium \n cluster.go:125: cilium-operator \n cluster.go:125: Cluster Pods: 0/0 managed by Cilium\n cluster.go:125: W0612 00:29:07.648806 1854 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n --- PASS: kubeadm.v1.35.1.cilium.base/node_readiness (13.05s)\n --- PASS: kubeadm.v1.35.1.cilium.base/nginx_deployment (8.02s)\n --- PASS: kubeadm.v1.35.1.cilium.base/NFS_deployment (16.56s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n --- PASS: kubeadm.v1.35.1.cilium.base/IPSec_encryption (20.21s)\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"kubeadm.v1.34.4.flannel.base/node_readiness","result":"PASS","duration":13003019125,"output":""},{"name":"kubeadm.v1.34.4.flannel.base/nginx_deployment","result":"PASS","duration":8025224947,"output":""},{"name":"kubeadm.v1.34.4.flannel.base/NFS_deployment","result":"PASS","duration":16652815182,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.34.4.flannel.base","result":"PASS","duration":439031908097,"output":" cluster.go:125: I0612 00:28:10.964825 2021 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.12.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.5-0\n cluster.go:125: I0612 00:28:18.944382 2236 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [init] Using Kubernetes version: v1.34.8\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [172-237-150-138 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 172.237.150.138]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 1.001014294s\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://172.237.150.138:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 1.506841919s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 2.186076352s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.0016133s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node 172-237-150-138 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node 172-237-150-138 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: k91o8r.q0a9ilzbe4ekhvd0\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 172.237.150.138:6443 --token k91o8r.q0a9ilzbe4ekhvd0 \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:af4d69369afb73e8032344b82fd03de856c858977b52608086f87d5801ba7a19 \n cluster.go:125: namespace/kube-flannel created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/flannel created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/flannel created\n cluster.go:125: serviceaccount/flannel created\n cluster.go:125: configmap/kube-flannel-cfg created\n cluster.go:125: daemonset.apps/kube-flannel-ds created\n cluster.go:125: W0612 00:30:44.162193 1814 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n --- PASS: kubeadm.v1.34.4.flannel.base/node_readiness (13.00s)\n --- PASS: kubeadm.v1.34.4.flannel.base/nginx_deployment (8.03s)\n --- PASS: kubeadm.v1.34.4.flannel.base/NFS_deployment (16.65s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.34.4.cilium.base/node_readiness","result":"PASS","duration":19063594343,"output":""},{"name":"kubeadm.v1.34.4.cilium.base/nginx_deployment","result":"PASS","duration":8076017552,"output":""},{"name":"kubeadm.v1.34.4.cilium.base/NFS_deployment","result":"PASS","duration":16516793737,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.34.4.cilium.base/IPSec_encryption","result":"PASS","duration":20731157509,"output":" cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"kubeadm.v1.34.4.cilium.base","result":"PASS","duration":486069093097,"output":" cluster.go:125: I0612 00:29:20.856617 2073 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.12.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.5-0\n cluster.go:125: I0612 00:29:28.640017 2288 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [init] Using Kubernetes version: v1.34.8\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [172-237-150-202 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 172.237.150.202]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 500.885203ms\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://172.237.150.202:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 2.006708291s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 2.36925277s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.001158512s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node 172-237-150-202 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node 172-237-150-202 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: for9mt.deug41uaebuhq9ro\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 172.237.150.202:6443 --token for9mt.deug41uaebuhq9ro \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:0561c5c8d2611fb1bfa786a03bad4caaa6d018bb5804b038009f6705d3875a3f \n cluster.go:125: i Using Cilium version 1.12.5\n cluster.go:125: ? Auto-detected cluster name: kubernetes\n cluster.go:125: ? Auto-detected datapath mode: tunnel\n cluster.go:125: ? Auto-detected kube-proxy has been installed\n cluster.go:125: i helm template --namespace kube-system cilium cilium/cilium --version 1.12.5 --set cluster.id=0,cluster.name=kubernetes,encryption.nodeEncryption=false,extraConfig.cluster-pool-ipv4-cidr=192.168.0.0/17,extraConfig.enable-endpoint-routes=true,kubeProxyReplacement=disabled,operator.replicas=1,serviceAccounts.cilium.name=cilium,serviceAccounts.operator.name=cilium-operator,tunnel=vxlan\n cluster.go:125: i Storing helm values file in kube-system/cilium-cli-helm-values Secret\n cluster.go:125: ? Created CA in secret cilium-ca\n cluster.go:125: ? Generating certificates for Hubble...\n cluster.go:125: ? Creating Service accounts...\n cluster.go:125: ? Creating Cluster roles...\n cluster.go:125: ? Creating ConfigMap for Cilium version 1.12.5...\n cluster.go:125: i Manual overwrite in ConfigMap: enable-endpoint-routes=true\n cluster.go:125: i Manual overwrite in ConfigMap: cluster-pool-ipv4-cidr=192.168.0.0/17\n cluster.go:125: ? Creating Agent DaemonSet...\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: ? Creating Operator Deployment...\n cluster.go:125: ? Waiting for Cilium to be installed and ready...\n cluster.go:125: ? Cilium was successfully installed! Run 'cilium status' to view installation health\n cluster.go:125: \u001b[33m /??\\\n cluster.go:125: \u001b[36m /??\u001b[33m\\__/\u001b[32m??\\\u001b[0m Cilium: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[36m \\__\u001b[31m/??\\\u001b[32m__/\u001b[0m Operator: \u001b[32mOK\u001b[0m\n cluster.go:125: \u001b[32m /??\u001b[31m\\__/\u001b[35m??\\\u001b[0m Hubble: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[32m \\__\u001b[34m/??\\\u001b[35m__/\u001b[0m ClusterMesh: \u001b[36mdisabled\u001b[0m\n cluster.go:125: \u001b[34m \\__/\n cluster.go:125: \u001b[0m\n cluster.go:125: DaemonSet cilium \n cluster.go:125: Deployment cilium-operator \n cluster.go:125: Containers: cilium \n cluster.go:125: cilium-operator \n cluster.go:125: Cluster Pods: 0/0 managed by Cilium\n cluster.go:125: W0612 00:32:01.066639 1857 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n --- PASS: kubeadm.v1.34.4.cilium.base/node_readiness (19.06s)\n --- PASS: kubeadm.v1.34.4.cilium.base/nginx_deployment (8.08s)\n --- PASS: kubeadm.v1.34.4.cilium.base/NFS_deployment (16.52s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n --- PASS: kubeadm.v1.34.4.cilium.base/IPSec_encryption (20.73s)\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/mount-cgroup]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/apply-sysctl-overwrites]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/clean-cilium-state]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n cluster.go:125: level=warning msg=\"spec.template.metadata.annotations[container.apparmor.security.beta.kubernetes.io/cilium-agent]: deprecated since v1.30; use the \\\"appArmorProfile\\\" field instead\" subsys=klog\n"},{"name":"kubeadm.v1.34.4.calico.base/node_readiness","result":"PASS","duration":13019963401,"output":""},{"name":"kubeadm.v1.34.4.calico.base/nginx_deployment","result":"PASS","duration":8007530400,"output":""},{"name":"kubeadm.v1.34.4.calico.base/NFS_deployment","result":"PASS","duration":34635131636,"output":" cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"},{"name":"kubeadm.v1.34.4.calico.base","result":"PASS","duration":497214969641,"output":" cluster.go:125: I0612 00:34:38.493122 2080 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.8\n cluster.go:125: [config/images] Pulled registry.k8s.io/coredns/coredns:v1.12.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/pause:3.10.1\n cluster.go:125: [config/images] Pulled registry.k8s.io/etcd:3.6.5-0\n cluster.go:125: I0612 00:34:46.381446 2295 version.go:260] remote version is much newer: v1.36.1; falling back to: stable-1.34\n cluster.go:125: [init] Using Kubernetes version: v1.34.8\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n cluster.go:125: [preflight] Pulling images required for setting up a Kubernetes cluster\n cluster.go:125: [preflight] This might take a minute or two, depending on the speed of your internet connection\n cluster.go:125: [preflight] You can also perform this action beforehand using 'kubeadm config images pull'\n cluster.go:125: [certs] Using certificateDir folder \"/etc/kubernetes/pki\"\n cluster.go:125: [certs] Generating \"ca\" certificate and key\n cluster.go:125: [certs] Generating \"apiserver\" certificate and key\n cluster.go:125: [certs] apiserver serving cert is signed for DNS names [172-237-146-97 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 172.237.146.97]\n cluster.go:125: [certs] Generating \"apiserver-kubelet-client\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-ca\" certificate and key\n cluster.go:125: [certs] Generating \"front-proxy-client\" certificate and key\n cluster.go:125: [certs] External etcd mode: Skipping etcd/ca certificate authority generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/server certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/peer certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping etcd/healthcheck-client certificate generation\n cluster.go:125: [certs] External etcd mode: Skipping apiserver-etcd-client certificate generation\n cluster.go:125: [certs] Generating \"sa\" key and public key\n cluster.go:125: [kubeconfig] Using kubeconfig folder \"/etc/kubernetes\"\n cluster.go:125: [kubeconfig] Writing \"admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"super-admin.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"kubelet.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"controller-manager.conf\" kubeconfig file\n cluster.go:125: [kubeconfig] Writing \"scheduler.conf\" kubeconfig file\n cluster.go:125: [control-plane] Using manifest folder \"/etc/kubernetes/manifests\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-apiserver\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-controller-manager\"\n cluster.go:125: [control-plane] Creating static Pod manifest for \"kube-scheduler\"\n cluster.go:125: [kubelet-start] Writing kubelet environment file with flags to file \"/var/lib/kubelet/kubeadm-flags.env\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/instance-config.yaml\"\n cluster.go:125: [patches] Applied patch of type \"application/strategic-merge-patch+json\" to target \"kubeletconfiguration\"\n cluster.go:125: [kubelet-start] Writing kubelet configuration to file \"/var/lib/kubelet/config.yaml\"\n cluster.go:125: [kubelet-start] Starting the kubelet\n cluster.go:125: [wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory \"/etc/kubernetes/manifests\"\n cluster.go:125: [kubelet-check] Waiting for a healthy kubelet at http://127.0.0.1:10248/healthz. This can take up to 4m0s\n cluster.go:125: [kubelet-check] The kubelet is healthy after 501.00469ms\n cluster.go:125: [control-plane-check] Waiting for healthy control plane components. This can take up to 30m0s\n cluster.go:125: [control-plane-check] Checking kube-apiserver at https://172.237.146.97:6443/livez\n cluster.go:125: [control-plane-check] Checking kube-controller-manager at https://127.0.0.1:10257/healthz\n cluster.go:125: [control-plane-check] Checking kube-scheduler at https://127.0.0.1:10259/livez\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 1.504581521s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 2.150074795s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.00157952s\n cluster.go:125: [upload-config] Storing the configuration used in ConfigMap \"kubeadm-config\" in the \"kube-system\" Namespace\n cluster.go:125: [kubelet] Creating a ConfigMap \"kubelet-config\" in namespace kube-system with the configuration for the kubelets in the cluster\n cluster.go:125: [upload-certs] Skipping phase. Please see --upload-certs\n cluster.go:125: [mark-control-plane] Marking the node 172-237-146-97 as control-plane by adding the labels: [node-role.kubernetes.io/control-plane node.kubernetes.io/exclude-from-external-load-balancers]\n cluster.go:125: [mark-control-plane] Marking the node 172-237-146-97 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 6ldis8.qs7vlku0422fcghs\n cluster.go:125: [bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to get nodes\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token\n cluster.go:125: [bootstrap-token] Configured RBAC rules to allow certificate rotation for all node client certificates in the cluster\n cluster.go:125: [bootstrap-token] Creating the \"cluster-info\" ConfigMap in the \"kube-public\" namespace\n cluster.go:125: [kubelet-finalize] Updating \"/etc/kubernetes/kubelet.conf\" to point to a rotatable kubelet client certificate and key\n cluster.go:125: [addons] Applied essential addon: CoreDNS\n cluster.go:125: [addons] Applied essential addon: kube-proxy\n cluster.go:125: \n cluster.go:125: Your Kubernetes control-plane has initialized successfully!\n cluster.go:125: \n cluster.go:125: To start using your cluster, you need to run the following as a regular user:\n cluster.go:125: \n cluster.go:125: mkdir -p $HOME/.kube\n cluster.go:125: sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config\n cluster.go:125: sudo chown $(id -u):$(id -g) $HOME/.kube/config\n cluster.go:125: \n cluster.go:125: Alternatively, if you are the root user, you can run:\n cluster.go:125: \n cluster.go:125: export KUBECONFIG=/etc/kubernetes/admin.conf\n cluster.go:125: \n cluster.go:125: You should now deploy a pod network to the cluster.\n cluster.go:125: Run \"kubectl apply -f [podnetwork].yaml\" with one of the options listed at:\n cluster.go:125: https://kubernetes.io/docs/concepts/cluster-administration/addons/\n cluster.go:125: \n cluster.go:125: Then you can join any number of worker nodes by running the following on each as root:\n cluster.go:125: \n cluster.go:125: kubeadm join 172.237.146.97:6443 --token 6ldis8.qs7vlku0422fcghs \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:9da428f8fb53f39d7248fc1d8d4db6550634dd99f73458a366af60933ff05f29 \n cluster.go:125: namespace/tigera-operator created\n cluster.go:125: serviceaccount/tigera-operator created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: clusterrole.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: clusterrolebinding.rbac.authorization.k8s.io/tigera-operator created\n cluster.go:125: rolebinding.rbac.authorization.k8s.io/tigera-operator-secrets created\n cluster.go:125: deployment.apps/tigera-operator created\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/installations.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: customresourcedefinition.apiextensions.k8s.io/apiservers.operator.tigera.io condition met\n cluster.go:125: installation.operator.tigera.io/default created\n cluster.go:125: apiserver.operator.tigera.io/default created\n cluster.go:125: goldmane.operator.tigera.io/default created\n cluster.go:125: whisker.operator.tigera.io/default created\n cluster.go:125: W0612 00:37:26.935294 1853 joinconfiguration.go:112] [config] WARNING: Ignored configuration document with GroupVersionKind kubelet.config.k8s.io/v1beta1, Kind=KubeletConfiguration\n cluster.go:125: \t[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'\n --- PASS: kubeadm.v1.34.4.calico.base/node_readiness (13.02s)\n --- PASS: kubeadm.v1.34.4.calico.base/nginx_deployment (8.01s)\n --- PASS: kubeadm.v1.34.4.calico.base/NFS_deployment (34.64s)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n cluster.go:125: jq: error (at \u003cstdin\u003e:123): Cannot iterate over null (null)\n"}],"result":"PASS","platform":"akamai","version":"4593.2.2"}