The Juju team is proud to release Juju 2.9.7. We aim to be your preferred tool for writing operators, software that manages software, whether your hosting infrastructure is Kubernetes, in the cloud or on-premises.
This release candidate includes important fixes
- #1930798 Juju upgrade 2.9 controller from local branch fails with wrong namespace.
- #1922133 unit network data not populated on peer relations in sidecar charms
- #1925670 juju refresh --switch ./local fails for metadata v1 charm
- #1927656 migrated CaaS model will left in the cluster after model destroyed
- #1928182 Unable to deploy postgresql-k8s charm from charmhub
- #1928796 Unable to deploy bundle with sidecar and pod_spec charms
- #1929364 IP address sometimes not set or incorrect on pebble_ready event
- #1929904 juju ssh on k8s poor ux
- #1931139 Support encrypted EBS volumes for bootstrapping controllers on AWS
- #1931140 Document and support charmcraft’s bundle.yaml fields
- #1931708 install hook run after juju upgrade-model 2.7.8 to 2.9.4
- #1871224 controller fails to bring up jujud machine
- #1932547 juju ssh --proxy not working on aws when targeting containers with FAN addresses
- #1933705 “juju resources” revision date format uses year-date-month format instead of year-month-date
- #1934151 “juju config” with empty values erroneously resets since 2.9
Additional bugs fixed can be found in the milestone page.
How do I install Juju?
The best way to get a specific release of Juju is to install the snap from the appropriate channel.
snap info juju will give you a list of the current channels and the versions published in them. For the latest stable release of Juju:
sudo snap install juju --classic --channel=2.9
The Juju CLI is available for a variety of platforms, including Windows and macOS. Refer to the installation documentation for details.
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.9 for example, to get a particular version. To get the latest binary from your channel:
snap refresh juju --channel=2.9
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: