The Juju team is proud to release Juju 2.9.2. 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 includes important fixes
- LP #1928486 - juju isnt configuring no-proxy values as before
- LP #1928822 - serviceName not populated correctly on StatefulSet for sidecar charms
- LP #1903607 - add option to export-bundle that shows all config options
Additional bugs fixed can be found in the milestone page.
Model upgrades with sidecar charms
Models which contain k8s sidecar charms cannot be upgraded from 2.9.0. This is not an issue from the previous 2.9.1 release onwards, but any such workloads running on 2.9.0 will need to be redeployed.
libjuju Python Upgrade Steps
Juju is about to release a new version of our Python library to support the new Kubernetes proxy mechanism added in 2.9.0. This allows users to bootstrap to Kubernetes clusters that may not have a native means of exposing the Juju controller to clients.
To facilitate this Juju proxy’s through the Kubernetes api to talk with the controller. To allow these changes in Juju to work in the Python library a small RBAC change has to be made in Kubernetes if you are upgrading a controller from 2.9.0 to 2.9.2. This step does not have to be done for any other case.
Firstly identify the name of the controller namespace in kubernetes. This can be done running
kubectl get nsand looking for the namespaces that matches “controller-”
Once the namespace is found you will need to create an updated changes.yaml file with the following content.
rules: - apiGroups: - "" resources: - pods verbs: - list - get - watch - apiGroups: - "" resources: - services verbs: - get - apiGroups: - "" resources: - pods/portforward verbs: - create - get
- Apply the changes.yaml to the proxy role used by juju using the namespace identified in the first step.
kubectl patch role controller-proxy -p "$(cat changes.yaml)" -n <controller-namespace>
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.9for 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: