{"tests":[{"name":"docker.lib-coreos-dockerd-compat/docker-info","result":"PASS","duration":5874598715,"output":""},{"name":"docker.lib-coreos-dockerd-compat/resources","result":"PASS","duration":9666423723,"output":" 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.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\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: 2.12MB 0.0s 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.1s\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:ee86936009bfdf6b2fa37caf88759f3ec7f73bedbdb5c1213a88cc56a98b32f1 done\n cluster.go:125: #5 naming to docker.io/library/sleep\n cluster.go:125: #5 naming to docker.io/library/sleep done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:125: WARNING: Your kernel does not support OomKillDisable. OomKillDisable discarded.\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n"},{"name":"docker.lib-coreos-dockerd-compat/networks-reliably","result":"PASS","duration":172195018518,"output":" 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: 4.09MB 0.0s 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.1s done\n cluster.go:125: #5 writing image sha256:dbcd8c436a949cdf0b902e58ceceb939c4870f3f27ff20e230620cf6cdf49e35 done\n cluster.go:125: #5 naming to docker.io/library/ping 0.0s done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"docker.lib-coreos-dockerd-compat/user-no-caps","result":"PASS","duration":3835088883,"output":" 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.1s\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: 5.15MB 0.0s 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.1s done\n cluster.go:125: #5 writing image sha256:a57725bd9d5c5daa4aca0b8fa25dee035dcf2e5a4416deeaf4448effd1b85296 done\n cluster.go:125: #5 naming to docker.io/library/captest 0.0s done\n cluster.go:125: #5 DONE 0.1s\n"},{"name":"docker.lib-coreos-dockerd-compat/ownership","result":"PASS","duration":8726711051,"output":" cluster.go:125: Unable to find image 'ghcr.io/flatcar/nginx:latest' locally\n cluster.go:125: latest: Pulling from flatcar/nginx\n cluster.go:125: d05801594fd4: Pulling fs layer\n cluster.go:125: bfcccb2d28d9: Pulling fs layer\n cluster.go:125: 86ffcbfd30a5: Pulling fs layer\n cluster.go:125: bbf3ff12606e: Pulling fs layer\n cluster.go:125: cb68f929468a: Pulling fs layer\n cluster.go:125: 821e83dec5db: Pulling fs layer\n cluster.go:125: f0e67f386109: Pulling fs layer\n cluster.go:125: bbf3ff12606e: Waiting\n cluster.go:125: cb68f929468a: Waiting\n cluster.go:125: 821e83dec5db: Waiting\n cluster.go:125: f0e67f386109: Waiting\n cluster.go:125: 86ffcbfd30a5: Verifying Checksum\n cluster.go:125: 86ffcbfd30a5: Download complete\n cluster.go:125: bbf3ff12606e: Verifying Checksum\n cluster.go:125: bbf3ff12606e: Download complete\n cluster.go:125: cb68f929468a: Verifying Checksum\n cluster.go:125: cb68f929468a: Download complete\n cluster.go:125: d05801594fd4: Verifying Checksum\n cluster.go:125: d05801594fd4: Download complete\n cluster.go:125: 821e83dec5db: Verifying Checksum\n cluster.go:125: 821e83dec5db: Download complete\n cluster.go:125: f0e67f386109: Verifying Checksum\n cluster.go:125: f0e67f386109: Download complete\n cluster.go:125: bfcccb2d28d9: Verifying Checksum\n cluster.go:125: bfcccb2d28d9: Download complete\n cluster.go:125: d05801594fd4: Pull complete\n cluster.go:125: bfcccb2d28d9: Pull complete\n cluster.go:125: 86ffcbfd30a5: Pull complete\n cluster.go:125: bbf3ff12606e: Pull complete\n cluster.go:125: cb68f929468a: Pull complete\n cluster.go:125: 821e83dec5db: Pull complete\n cluster.go:125: f0e67f386109: Pull complete\n cluster.go:125: Digest: sha256:70aae0bfcd7c307fa7af235a49ce4b10b331d9bfa3c21a5aa85609bd875e3c10\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/nginx:latest\n"},{"name":"docker.lib-coreos-dockerd-compat","result":"PASS","duration":296158799030,"output":" --- PASS: docker.lib-coreos-dockerd-compat/docker-info (5.87s)\n --- PASS: docker.lib-coreos-dockerd-compat/resources (9.67s)\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.1s\n cluster.go:125: \n cluster.go:125: #2 [internal] load .dockerignore\n cluster.go:125: #2 transferring context:\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: 2.12MB 0.0s 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.1s\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:ee86936009bfdf6b2fa37caf88759f3ec7f73bedbdb5c1213a88cc56a98b32f1 done\n cluster.go:125: #5 naming to docker.io/library/sleep\n cluster.go:125: #5 naming to docker.io/library/sleep done\n cluster.go:125: #5 DONE 0.1s\n cluster.go:125: WARNING: Your kernel does not support OomKillDisable. OomKillDisable discarded.\n cluster.go:125: WARNING: Your kernel does not support memory swappiness capabilities or the cgroup is not mounted. Memory swappiness discarded.\n --- PASS: docker.lib-coreos-dockerd-compat/networks-reliably (172.20s)\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: 4.09MB 0.0s 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.1s done\n cluster.go:125: #5 writing image sha256:dbcd8c436a949cdf0b902e58ceceb939c4870f3f27ff20e230620cf6cdf49e35 done\n cluster.go:125: #5 naming to docker.io/library/ping 0.0s done\n cluster.go:125: #5 DONE 0.1s\n --- PASS: docker.lib-coreos-dockerd-compat/user-no-caps (3.84s)\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.1s\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: 5.15MB 0.0s 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.1s done\n cluster.go:125: #5 writing image sha256:a57725bd9d5c5daa4aca0b8fa25dee035dcf2e5a4416deeaf4448effd1b85296 done\n cluster.go:125: #5 naming to docker.io/library/captest 0.0s done\n cluster.go:125: #5 DONE 0.1s\n --- PASS: docker.lib-coreos-dockerd-compat/ownership (8.73s)\n cluster.go:125: Unable to find image 'ghcr.io/flatcar/nginx:latest' locally\n cluster.go:125: latest: Pulling from flatcar/nginx\n cluster.go:125: d05801594fd4: Pulling fs layer\n cluster.go:125: bfcccb2d28d9: Pulling fs layer\n cluster.go:125: 86ffcbfd30a5: Pulling fs layer\n cluster.go:125: bbf3ff12606e: Pulling fs layer\n cluster.go:125: cb68f929468a: Pulling fs layer\n cluster.go:125: 821e83dec5db: Pulling fs layer\n cluster.go:125: f0e67f386109: Pulling fs layer\n cluster.go:125: bbf3ff12606e: Waiting\n cluster.go:125: cb68f929468a: Waiting\n cluster.go:125: 821e83dec5db: Waiting\n cluster.go:125: f0e67f386109: Waiting\n cluster.go:125: 86ffcbfd30a5: Verifying Checksum\n cluster.go:125: 86ffcbfd30a5: Download complete\n cluster.go:125: bbf3ff12606e: Verifying Checksum\n cluster.go:125: bbf3ff12606e: Download complete\n cluster.go:125: cb68f929468a: Verifying Checksum\n cluster.go:125: cb68f929468a: Download complete\n cluster.go:125: d05801594fd4: Verifying Checksum\n cluster.go:125: d05801594fd4: Download complete\n cluster.go:125: 821e83dec5db: Verifying Checksum\n cluster.go:125: 821e83dec5db: Download complete\n cluster.go:125: f0e67f386109: Verifying Checksum\n cluster.go:125: f0e67f386109: Download complete\n cluster.go:125: bfcccb2d28d9: Verifying Checksum\n cluster.go:125: bfcccb2d28d9: Download complete\n cluster.go:125: d05801594fd4: Pull complete\n cluster.go:125: bfcccb2d28d9: Pull complete\n cluster.go:125: 86ffcbfd30a5: Pull complete\n cluster.go:125: bbf3ff12606e: Pull complete\n cluster.go:125: cb68f929468a: Pull complete\n cluster.go:125: 821e83dec5db: Pull complete\n cluster.go:125: f0e67f386109: Pull complete\n cluster.go:125: Digest: sha256:70aae0bfcd7c307fa7af235a49ce4b10b331d9bfa3c21a5aa85609bd875e3c10\n cluster.go:125: Status: Downloaded newer image for ghcr.io/flatcar/nginx:latest\n"},{"name":"kubeadm.v1.35.1.flannel.base/node_readiness","result":"PASS","duration":14189945090,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/nginx_deployment","result":"PASS","duration":9065110253,"output":""},{"name":"kubeadm.v1.35.1.flannel.base/NFS_deployment","result":"PASS","duration":18986773197,"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":355514986991,"output":" cluster.go:125: I0721 01:30:06.895011 2588 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.35\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.35.6\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.35.6\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.35.6\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.35.6\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: I0721 01:30:20.613870 2799 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.35\n cluster.go:125: [init] Using Kubernetes version: v1.35.6\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593.2.4-n-ff34310f22\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593.2.4-n-ff34310f22\": lookup ci-4593.2.4-n-ff34310f22 on 168.63.129.16:53: no such host\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 [ci-4593.2.4-n-ff34310f22 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.12]\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.66022ms\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://10.0.0.12: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.004310843s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 2.28449943s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 4.503031242s\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 ci-4593.2.4-n-ff34310f22 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 ci-4593.2.4-n-ff34310f22 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: ih6gho.nkqe55b42nhktukq\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 10.0.0.12:6443 --token ih6gho.nkqe55b42nhktukq \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:019293ad5d7bfa58abf66041ba85e642f8e932cc199aefe5ac60f5ff7121d637 \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: W0721 01:31:59.834158 2399 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 (14.19s)\n --- PASS: kubeadm.v1.35.1.flannel.base/nginx_deployment (9.07s)\n --- PASS: kubeadm.v1.35.1.flannel.base/NFS_deployment (18.99s)\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.flannel.base/node_readiness","result":"PASS","duration":20719372444,"output":""},{"name":"kubeadm.v1.36.1.flannel.base/node_readiness","result":"PASS","duration":26938608282,"output":""},{"name":"kubeadm.v1.34.4.flannel.base/nginx_deployment","result":"PASS","duration":15564200142,"output":""},{"name":"kubeadm.v1.36.1.flannel.base/nginx_deployment","result":"PASS","duration":28235713323,"output":""},{"name":"kubeadm.v1.34.4.flannel.base/NFS_deployment","result":"PASS","duration":31552508589,"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":"coreos.locksmith.reboot","result":"PASS","duration":420357580376,"output":""},{"name":"coreos.update.badusr","result":"PASS","duration":423156838036,"output":""},{"name":"kubeadm.v1.34.4.flannel.base","result":"PASS","duration":424262197550,"output":" cluster.go:125: I0721 01:30:13.055106 2577 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.34\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.9\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: I0721 01:30:40.296598 2973 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.34\n cluster.go:125: [init] Using Kubernetes version: v1.34.9\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593.2.4-n-5ef2ef8f71\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593.2.4-n-5ef2ef8f71\": lookup ci-4593.2.4-n-5ef2ef8f71 on 168.63.129.16:53: no such host\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 [ci-4593.2.4-n-5ef2ef8f71 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.14]\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.001529512s\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://10.0.0.14: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 12.006743794s\n cluster.go:125: [control-plane-check] kube-controller-manager is healthy after 12.504078959s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 15.001968718s\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 ci-4593.2.4-n-5ef2ef8f71 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 ci-4593.2.4-n-5ef2ef8f71 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: dsavtk.5522zjsn3lhuquaw\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 10.0.0.14:6443 --token dsavtk.5522zjsn3lhuquaw \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:07f1f4c01666d4f5c515acbe883600e3e8d33b905264b0545185a925037ed1d4 \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: W0721 01:32:37.645569 2523 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 (20.72s)\n --- PASS: kubeadm.v1.34.4.flannel.base/nginx_deployment (15.56s)\n --- PASS: kubeadm.v1.34.4.flannel.base/NFS_deployment (31.55s)\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"},{"name":"kubeadm.v1.36.1.flannel.base/NFS_deployment","result":"PASS","duration":57135564203,"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 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":470857028288,"output":" cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.36.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.36.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.36.2\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.36.2\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.2\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593.2.4-n-59b6a10db2\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593.2.4-n-59b6a10db2\": lookup ci-4593.2.4-n-59b6a10db2 on 168.63.129.16:53: no such host\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 [ci-4593.2.4-n-59b6a10db2 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.15]\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.229586ms\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://10.0.0.15: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 3.501072ms\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 4.925694ms\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 3.001616587s\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 ci-4593.2.4-n-59b6a10db2 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 ci-4593.2.4-n-59b6a10db2 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: hauc3o.6zfaqh024i5abq4w\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 10.0.0.15:6443 --token hauc3o.6zfaqh024i5abq4w \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:19d8b4d1e77a33d30dad1d335a7a2a398365e098454a72b4f97284de1e651cbc \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: W0721 01:32:41.009342 2395 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: W0721 01:32:41.186801 2395 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 (26.94s)\n --- PASS: kubeadm.v1.36.1.flannel.base/nginx_deployment (28.24s)\n --- PASS: kubeadm.v1.36.1.flannel.base/NFS_deployment (57.14s)\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 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":33445331449,"output":""},{"name":"kubeadm.v1.34.4.cilium.base/nginx_deployment","result":"PASS","duration":16021980315,"output":""},{"name":"kubeadm.v1.34.4.cilium.base/NFS_deployment","result":"PASS","duration":25240842737,"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"},{"name":"kubeadm.v1.34.4.cilium.base/IPSec_encryption","result":"PASS","duration":30732130853,"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":586198871021,"output":" cluster.go:125: I0721 01:30:37.080674 2909 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.34\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-apiserver:v1.34.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-controller-manager:v1.34.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-scheduler:v1.34.9\n cluster.go:125: [config/images] Pulled registry.k8s.io/kube-proxy:v1.34.9\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: I0721 01:31:35.054394 3173 version.go:260] remote version is much newer: v1.36.2; falling back to: stable-1.34\n cluster.go:125: [init] Using Kubernetes version: v1.34.9\n cluster.go:125: [preflight] Running pre-flight checks\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593.2.4-n-86958ae686\" could not be reached\n cluster.go:125: \t[WARNING Hostname]: hostname \"ci-4593.2.4-n-86958ae686\": lookup ci-4593.2.4-n-86958ae686 on 168.63.129.16:53: no such host\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 [ci-4593.2.4-n-86958ae686 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.0.0.13]\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 717.496µs\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://10.0.0.13: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 11.005466199s\n cluster.go:125: [control-plane-check] kube-scheduler is healthy after 11.53931055s\n cluster.go:125: [control-plane-check] kube-apiserver is healthy after 13.501784019s\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 ci-4593.2.4-n-86958ae686 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 ci-4593.2.4-n-86958ae686 as control-plane by adding the taints [node-role.kubernetes.io/control-plane:NoSchedule]\n cluster.go:125: [bootstrap-token] Using token: 6sxync.t4ujyplq7by7h6fl\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 10.0.0.13:6443 --token 6sxync.t4ujyplq7by7h6fl \\\n cluster.go:125: \t--discovery-token-ca-cert-hash sha256:7f3c1050453c94b4753e5f62073fda54ae794b55fe0a4c35bfcbe56fdbdce684 \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 Desired: 1, Ready: \u001b[32m1/1\u001b[0m, Available: \u001b[32m1/1\u001b[0m\n cluster.go:125: Deployment cilium-operator Desired: 1, Ready: \u001b[32m1/1\u001b[0m, Available: \u001b[32m1/1\u001b[0m\n cluster.go:125: Containers: cilium Running: \u001b[32m1\u001b[0m\n cluster.go:125: cilium-operator Running: \u001b[32m1\u001b[0m\n cluster.go:125: Cluster Pods: 2/2 managed by Cilium\n cluster.go:125: Image versions cilium quay.io/cilium/cilium:v1.12.5@sha256:06ce2b0a0a472e73334a7504ee5c5d8b2e2d7b72ef728ad94e564740dd505be5: 1\n cluster.go:125: cilium-operator quay.io/cilium/operator-generic:v1.12.5@sha256:b296eb7f0f7656a5cc19724f40a8a7121b7fd725278b7d61dc91fe0b7ffd7c0e: 1\n cluster.go:125: W0721 01:34:45.830629 2567 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 (33.45s)\n --- PASS: kubeadm.v1.34.4.cilium.base/nginx_deployment (16.02s)\n --- PASS: kubeadm.v1.34.4.cilium.base/NFS_deployment (25.24s)\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 --- PASS: kubeadm.v1.34.4.cilium.base/IPSec_encryption (30.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":"cl.update.badverity","result":"PASS","duration":603278419940,"output":""}],"result":"PASS","platform":"azure","version":"4593.2.4"}