Open displague opened 5 months ago
Using the new upstream repo gets past the apt update
failure.
https://kubernetes.io/blog/2023/08/15/pkgs-k8s-io-introduction/#how-to-migrate
After #63, provisioning continues to fail because the VIP EIP is used to source the SSH key:
scp -o StrictHostKeyChecking=no -i ssh_key root@{VIP_EIP_HERE}:/etc/kubernetes/admin.conf kubeconfig.admin.yaml
This could be sourced from cp-1 instead.
The cpem-add-on example fails to provision:
This ultimately results in:
This would appear to indicate that the control plane EIP was not assigned to a node in the cluster. Upon logging in to the cp-1 node, we see a cloud-init provisioning failure in
/var/log/cloud-init-output.log
.