Nico Schottelius
Nico Schottelius
@urwen There are many PRs and issues open - would you be open for somebody else to take over the project? I can fork it, but I have seen that...
I have a question, are there anywhere helm charts for a complete cloudstack-on-kubernetes deployment similar to openstack-helm?
I have also been hit by this problem and the bios message appears on every reboot now
@medyagh how/where would one need to implement? Maybe I can give it a try.
Heads up: I had a very similar issue for many years: - start emacs --daemon - run mu4e - have other stuff open - at some point in an active...
To follow up on #3075, there does indeed seem to be a bug within kubeadm even *with* a default route present: ``` [08:33] server123.place10:~# ip route add default via 2001:1700:3500:2::11...
And on both nodes it works with the same workaround as before: ``` [08:54] server123.place10:~# kubeadm token create --print-join-command --v=5 --config ./kubeadm-init-only.yaml I0827 08:54:47.068597 15472 token.go:119] [token] validating mixed arguments...
> i don't think we want to update the documentation or modify kubeadm, because kubeadm is aligned with the IP detection mechanism of all k8s components. they all use default...
> @telmich this is already supported by passing IPs to everything. > this is not a workaround. this is the expected way, but topology wise it's not recommended. I disagree...
> > * b) add an option to manually specific the IP address > > You can and must do this, if you are setting your own routing rules, it...