gistfile1.txt

git clone git@github.com:French-Exception-2/vagranti-dev.php.git vagranti-dev.php.git

https://github.com/French-Exception-2/vagranti-dev.php/blob/develop/provisioning/Debian_64/10.7.0/k8s.install.sh
https://github.com/French-Exception-2/vagranti-dev.php/blob/develop/provisioning/Debian_64/10.7.0/k8s.configure.sh

==> vdi-01-dev-worker-01: Running provisioner: k8s.configure (shell)...
    vdi-01-dev-worker-01: Running: script: k8s.configure
    vdi-01-dev-worker-01: [preflight] Running pre-flight checks
    vdi-01-dev-worker-01:       [WARNING SystemVerification]: missing optional cgroups: hugetlb
    vdi-01-dev-worker-01: [preflight] Reading configuration from the cluster...
    vdi-01-dev-worker-01: [preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
    vdi-01-dev-worker-01: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
    vdi-01-dev-worker-01: [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
    vdi-01-dev-worker-01: [kubelet-start] Starting the kubelet
    vdi-01-dev-worker-01: [kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
    vdi-01-dev-worker-01: [kubelet-check] Initial timeout of 40s passed.
    vdi-01-dev-worker-01: error execution phase kubelet-start: error uploading crisocket: timed out waiting for the condition
    vdi-01-dev-worker-01: To see the stack trace of this error execute with --v=5 or higher
    vdi-01-dev-worker-01: [preflight] Running pre-flight checks
    vdi-01-dev-worker-01: [reset] No etcd config found. Assuming external etcd
    vdi-01-dev-worker-01: [reset] Please, manually reset etcd to prevent further issues
    vdi-01-dev-worker-01: [reset] Stopping the kubelet service
    vdi-01-dev-worker-01: W0215 23:41:45.460278    5879 removeetcdmember.go:79] [reset] No kubeadm config, using etcd pod spec to get data directory
    vdi-01-dev-worker-01: [reset] Unmounting mounted directories in "/var/lib/kubelet"
    vdi-01-dev-worker-01: [reset] Deleting contents of config directories: [/etc/kubernetes/manifests /etc/kubernetes/pki]
    vdi-01-dev-worker-01: [reset] Deleting files: [/etc/kubernetes/admin.conf /etc/kubernetes/kubelet.conf /etc/kubernetes/bootstrap-kubelet.conf /etc/kubernetes/controller-manager.conf /etc/kubernetes/scheduler.conf]
    vdi-01-dev-worker-01: [reset] Deleting contents of stateful directories: [/var/lib/kubelet /var/lib/dockershim /var/run/kubernetes /var/lib/cni]
    vdi-01-dev-worker-01:
    vdi-01-dev-worker-01: The reset process does not clean CNI configuration. To do so, you must remove /etc/cni/net.d
    vdi-01-dev-worker-01:
    vdi-01-dev-worker-01: The reset process does not reset or clean up iptables rules or IPVS tables.
    vdi-01-dev-worker-01: If you wish to reset iptables, you must do so manually by using the "iptables" command.
    vdi-01-dev-worker-01:
    vdi-01-dev-worker-01: If your cluster was setup to utilize IPVS, run ipvsadm --clear (or similar)
    vdi-01-dev-worker-01: to reset your system's IPVS tables.
    vdi-01-dev-worker-01:
    vdi-01-dev-worker-01: The reset process does not clean your kubeconfig files and you must remove them manually.
    vdi-01-dev-worker-01: Please, check the contents of the $HOME/.kube/config file.
    vdi-01-dev-worker-01: [preflight] Running pre-flight checks
    vdi-01-dev-worker-01:       [WARNING SystemVerification]: missing optional cgroups: hugetlb
    vdi-01-dev-worker-01: [preflight] Reading configuration from the cluster...
    vdi-01-dev-worker-01: [preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
    vdi-01-dev-worker-01: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
    vdi-01-dev-worker-01: [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
    vdi-01-dev-worker-01: [kubelet-start] Starting the kubelet
    vdi-01-dev-worker-01: [kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
    vdi-01-dev-worker-01: 
    vdi-01-dev-worker-01: This node has joined the cluster:
    vdi-01-dev-worker-01: * Certificate signing request was sent to apiserver and a response was received.
    vdi-01-dev-worker-01: * The Kubelet was informed of the new secure connection details.
    vdi-01-dev-worker-01:
    vdi-01-dev-worker-01: Run 'kubectl get nodes' on the control-plane to see this node join the cluster.
    vdi-01-dev-worker-01: node/vdi-01-dev-worker-01 labeled
    vdi-01-dev-worker-01: Kubernetes control plane is running at https://10.100.2.2:6443
    vdi-01-dev-worker-01: KubeDNS is running at https://10.100.2.2:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
    vdi-01-dev-worker-01:
    vdi-01-dev-worker-01: To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

==> vdi-01-dev-worker-01: Machine 'vdi-01-dev-worker-01' has a post `vagrant up` message. This is a message
==> vdi-01-dev-worker-01: from the creator of the Vagrantfile, and not from Vagrant itself:
==> vdi-01-dev-worker-01:
==> vdi-01-dev-worker-01: Vanilla Debian box. See https://app.vagrantup.com/debian for help and bug reports