Okay… so much for the upgrade instructions. You’d think that you’re setting the charm to channel 1.25 by doing:
juju config kubernetes-control-plane channel=1.25/stable
But that’s not the actual channel of the charm, which in my case was still set at 1.24. So I had to do
juju refresh kubernetes-master --channel 1.25/stable
Why is this BIG gotcha not at least noted in the upgrade instructions?
What is the real difference between these commands which both seem to do something with channels, in the first place?
Further, the documentation, (i see this in hindsight), actually mentions that your charm channels should be on ‘stable’, whereas I had ‘1.24/stable’. Why is this? Well, that’s because I upgraded using Upgrading | Ubuntu to 1.24 in the past. That section explicitly sets the channel to ‘1.24/stable’.
This is yet another upgrade continuity error I stumble upon. If Canonical wants to get serious about this, these things should simply not happen. I work at a Kubernetes Certified Service Provider, and everytime my chef asks me if Charmed K8s is an option for our customers, I have to answer: only if you like debugging python code and want to assume an upgrade goes wrong.