patch: updated all of the versions - ALL OF THEM! #306
Conversation
drew-viles
force-pushed
the
CLDNTV-266
branch
4 times, most recently
from
800ee78
to
bbb1aa3
Compare
* New unikorn release with a note on deprecating and removing cilium taints from `clusteropenstack` helm application as this is now provided via the cilium operator as of 1.14.0 - cilium/cilium#23486 We can't do this yet as it would break any apps pre kubernetes-cluster-1.4.0 * Updates a bunch of other packages with a nuew preview application bundle for both clusters and control plane * Some minor doc corrections
drew-viles
force-pushed
the
CLDNTV-266
branch
from
bbb1aa3
to
7a73ed0
Compare
|
I've hit the same vcluster error and came across loft-sh/vcluster#1141 - upgrading to a newer version of vcluster itself suggests that'll fix the problem. Was this not the case in your testing? |
|
So I've been going on the approach of wanting to upgrade from what's deployed in eckmgt to the new version. A newer version of vcluster is working on my new 1.2.0 which is vcluster 0.15.7 (original is 0.15.0. I'm happy to bump it in the old one on my dev cluster but 0.15.0 is working on eckmgt so a bit confused. At least I can test a basic upgrade of everything else though so let me check that over |
|
There'll be some difference in what kubeadm does versus how kind (or K3s itself in my case) does things, since this suggested fix did the trick for me without having to upgrade. |
|
I've managed to now test the upgrade and new cluster rollout and all is working just fine. I had a couple resource running that remained accessible the entire time and all looks good. |
clusteropenstackhelm application as this is now provided via the cilium operator as of 1.14.0 - CNI: keep cni config on shutdown; taint instead, queue deletions cilium/cilium#23486We can't do this yet as it would break any apps pre kubernetes-cluster-1.4.0
A note worth making on this is I cannot for the life of me get a current cluster spun up in kind. It's failing to spin upvclusterwhen using control-plane bundle 1.1.0 - the error is annoyingly onlyexec /coredns: operation not permittedwhich is in practice useless. I've compared thevclusterI've got with some that are running ineckmgtand it's exactly the same.So, I can't test an upgrade on this so if you fancy giving a quick crack at the upgrade I'd be greatly appreciative.That all being said I have tested running the new version that's been created and all is working just nicely.