The Juju team is proud to release Juju 2.8.11!
This is a bug-fix release for the 2.8 series.
This release includes important fixes
- LP #1701429 - Netplan bridger does not properly merge yaml files
- LP #1921557 - juju login on unregistered controller fails with cert errors
- LP #1928390 - Juju panic’s when no ip certificate is found
- LP #1928282 - incorrect k8s service address
Additional bugs fixed can be found in the milestone page.
How do I upgrade?
There are three binaries that make up a Juju deployment - the client, the server and the agents. To upgrade a running system:
Upgrade the client
Make sure you have the version of the Juju CLI that you want running across the system (controller and agents in any deployed models). If you installed the Juju snap, it will automatically be updated daily from the channel you selected, but you might want to
sudo snap switch juju --channel=2.8/stable for example, to get a particular version. To get the latest binary from your channel:
snap refresh juju
Upgrading the Juju client through other channels
Make sure that you’re using the Juju version you want.
What to do if Juju reports an old version
The controller state can be saved to allow for recovery in case the upgrade process encounters a serious error.
Upgrade a Juju server
You can see which servers your client knows about, and their versions, with this command:
juju controllers Controller ... Version azure* ... 2.8.3 jaas ... 2.7.6
You can instruct a server to upgrade itself to the latest version:
juju upgrade-controller <controller>
How to upgrade the controller
Upgrade deployed agents
Each running model includes a set of Juju agents which manage the communication between your charms and the Juju server. Your model agents remain at the same version until you ask to upgrade them.
juju upgrade-model <model>
How to upgrade your model(s)
For detailed information about the upgrade process please see: