We glad to introduce Juju 3.5.6 – a bugfix release dedicated to enhancing the reliability and efficiency of your cloud orchestration. This update addresses a spectrum of issues, from ensuring smoother controller operations with Kubernetes sidecar charms to refining public IP allocation on AWS. Explore the details below.
Fixes:
- Fix controller restart meant sidecar charm k8s workloads restarts
- Fix allocate-public-ip not applied in AWS EC2 provider
- Fix Cannot log into controller where model was migrated
- Fix Potential race in provisioner while destroying model with machine-with-placemen
- Fix Juju cannot enable HA when IPs reside in 100.64.0.0/10
- Fix juju register failed with permission denied
- Fix Juju bootstrap ignores --bootstrap-base parameter
- Fix google vpc firewall rule left around after model/controller destroy
See the full list in the milestone page.
PS: We are now migrating to RTD, we expect all further Juju release announces will be available on special page there after we finish the migration. So, we unpin our previous ‘Roadmap & Releases’ post as a part of this migration, and provide the details in further posts. Apologies for the inconvenience.