You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello team,
I have been working on documenting the steps required to upgrade the vault-k8s charm. Based on my observation it seemed as if the upgrade was happening unit by unit after running the juju refresh <charm> command. Turns out this wasn't a coincidence as the RollingUpgrade strategy of Kubernetes is used by Juju and k8s will wait for the new pod to be ready before upgrading the next one.
I couldn't find this information anywhere in the docs and got the answer after asking on the Juju channel on Matrix. (Thread here)
I think this can be valuable for teams looking into implementing rolling upgrade for their charms.
The text was updated successfully, but these errors were encountered:
Hello team,
I have been working on documenting the steps required to upgrade the
vault-k8scharm. Based on my observation it seemed as if the upgrade was happening unit by unit after running thejuju refresh <charm>command. Turns out this wasn't a coincidence as the RollingUpgrade strategy of Kubernetes is used by Juju and k8s will wait for the new pod to be ready before upgrading the next one.I couldn't find this information anywhere in the docs and got the answer after asking on the Juju channel on Matrix. (Thread here)
I think this can be valuable for teams looking into implementing rolling upgrade for their charms.
The text was updated successfully, but these errors were encountered: