This seemed to fix the problem on the juju server running kubernetes-master/1:
Whether or not all the steps (like upgrades) is related, I am not sure.
1. Noticed that juju models were in 'suspended' mode 2. updated model credentials so models were 'available'
Kubernetes-master/1 still blocked
3. juju ssh (Kubernetes-master/1) apt update apt upgrade reboot
Fixed!
As the rest of the servers in my deployment have not been updated, I think the reboot must have fixed the problem on its own and probably has nothing to do with the model credentials either.
This seemed to fix the problem on the juju server running kubernetes- master/ 1:
Whether or not all the steps (like upgrades) is related, I am not sure.
1. Noticed that juju models were in 'suspended' mode
2. updated model credentials so models were 'available'
Kubernetes-master/1 still blocked
3. juju ssh (Kubernetes- master/ 1)
apt update
apt upgrade
reboot
Fixed!
As the rest of the servers in my deployment have not been updated, I think the reboot must have fixed the problem on its own and probably has nothing to do with the model credentials either.