Originally posted by **lubronzhan** April 16, 2024
We is still using old multus, without the thick image, as mentioned here
https://github.com/k8snetworkplumbingwg/multus-cni/issues/852. So if the kubeconfig of multus expires, the multus will fail to connect to apiserver to update pod info.
Question, what's the proper way to rotate the token for now? restarting multus pod + pod that needs the second nic?
We will try upgrade to thick image later.
Thank you
Discussed in https://github.com/k8snetworkplumbingwg/multus-cni/discussions/1262