init --pod-network-cidr=10.217.0.0/16 --skip-phases=addon/kube- proxy In K8s 1.15 and older it is not yet possible to disable kube-proxy via --skip- phases=addon/kube-proxy in kubeadm, therefore the below Agent Name Labels Description agent_bootstrap_seconds scope, outcome Duration of various bootstrap phases api_process_time_seconds Processing time of all the API calls made to the cilium-agent, labeled flag. Using Jenkins for testing Typically when running Jenkins tests via one of the above trigger phases, it will run all of the tests in that particular category. However, there may be cases where you

kube-proxy deployment phase, so it has to be executed with the --skip- phases=addon/kube-proxy option: kubeadm init --skip-phases=addon/kube-proxy For more information please refer to the Kubernetes without newer K8s 1.15 and older kubeadm init --skip-phases=addon/kube-proxy In K8s 1.15 and older it is not yet possible to disable kube-proxy via --skip- phases=addon/kube-proxy in kubeadm, therefore the below Agent Name Labels Description agent_bootstrap_seconds scope, outcome Duration of various bootstrap phases api_process_time_seconds Processing time of all the API calls made to the cilium-agent, labeled

kube-proxy deployment phase, so it has to be executed with the --skip- phases=addon/kube-proxy option: kubeadm init --skip-phases=addon/kube-proxy For more information please refer to the Kubernetes Without 1.16 and newer kubeadm init --skip-phases=addon/kube-proxy K8s 1.15 and older In K8s 1.15 and older it is not yet possible to disable kube-proxy via --skip- phases=addon/kube-proxy in kubeadm, therefore Agent Name Labels Description agent_bootstrap_seconds scope, outcome Duration of various bootstrap phases api_process_time_seconds Processing time of all the API calls made to the cilium-agent, labeled

init --pod-network-cidr=10.217.0.0/16 --skip-phases=addon/kube- proxy In K8s 1.15 and older it is not yet possible to disable kube-proxy via --skip- phases=addon/kube-proxy in kubeadm, therefore the below Agent Name Labels Description agent_bootstrap_seconds scope, outcome Duration of various bootstrap phases api_process_time_seconds Processing time of all the API calls made to the cilium-agent, labeled flag. Using Jenkins for testing Typically when running Jenkins tests via one of the above trigger phases, it will run all of the tests in that particular category. However, there may be cases where you

kube-proxy deployment phase, so it has to be executed with the --skip- phases=addon/kube-proxy option: kubeadm init --skip-phases=addon/kube-proxy For more information please refer to the Kubernetes Without node via kubeadm init and skip the installation of the kube-proxy add-on: $ kubeadm init --skip-phases=addon/kube-proxy Afterwards, join worker nodes by specifying the control-plane node IP address and Agent Name Labels Description agent_bootstrap_seconds scope, outcome Duration of various bootstrap phases api_process_time_seconds Processing time of all the API calls made to the cilium-agent, labeled

kube-proxy deployment phase, so it has to be executed with the --skip- phases=addon/kube-proxy option: kubeadm init --skip-phases=addon/kube-proxy For more information please refer to the Kubernetes Without node via kubeadm init and skip the installation of the kube-proxy add-on: $ kubeadm init --skip-phases=addon/kube-proxy Afterwards, join worker nodes by specifying the control-plane node IP address and Agent Name Labels Description agent_bootstrap_seconds scope, outcome Duration of various bootstrap phases api_process_time_seconds Processing time of all the API calls made to the cilium-agent, labeled

could be queued Labels: action , scope Agent agent_bootstrap_seconds : Dura�on of various bootstrap phases * Labels: scope , outcome api_process_time_seconds : Processing �me of all the API calls made to flag. Using Jenkins for testing Typically when running Jenkins tests via one of the above trigger phases, it will run all of the tests in that par�cular category. However, there may be cases where you just