Open jbpratt opened 3 years ago
Nope, not a fix, never mind. While that did allow those pods to come up if restarted fast enough, this gets written over by whatever is managing it.
Right now I'm trying to lift several things up into a more sustainable code breakout model.
This is the source of truth as all this gets stabilized out for the 100DaysOfHomelab vlog series.
Multus has been a sticking point, the workaround isnt pretty yet but it is falling inline with this deployment method.
This Kargo repo will be pared down based on how that dust settles and multus likely will be cut out of this repo.
On reboot, my node was failing to bring up the
hostpath-provisioner
andkube-cni-linux-bridge
pods due to a change in the Multus clusterrolebinding. I'm not sure why it is happening but others have ran into this before https://github.com/k8snetworkplumbingwg/multus-cni/issues/667with the event of
Following along with the ticket, it does seem that the
namespace
for the multus SA has been changed tocluster-network-addons
editing the value from
cluster-network-addons
->kube-system
allows the pods to be createdBased on the response from the issue, this may be due to how we are installing things? Just wanted to report this with a patch in case others run into this. :cat: