@@ -39,6 +39,53 @@ juju deploy charmed-kubernetes --overlay cilium-overlay.yaml
39
39
You can apply any additional customisation overlays to this deployment as
40
40
well.
41
41
42
+ ## Upgrading Charmed Kubernetes with Cilium
43
+
44
+ <div class =" p-notification--information is-inline " >
45
+ <div class =" p-notification__content " >
46
+ <span class="p-notification__title">Note:</span>
47
+ <p class="p-notification__message">Upgrades should be executed stepping through major versions.
48
+ </p>
49
+ </div >
50
+ </div >
51
+
52
+
53
+ Determine which version of cilium is currently installed on the cluster using ` juju status cilium `
54
+
55
+ ``` sh
56
+ App Version Status Scale Charm Channel Rev Exposed Message
57
+ cilium 1.12.5 active 5 cilium latest/stable 29 no Ready
58
+ ```
59
+
60
+ Upgrading will require changing the ` release ` config of the charm with ` juju config cilium release=<version> ` , but choosing
61
+ which version requires seeing what the charm currently supports.
62
+
63
+ ``` sh
64
+ juju run cilium/leader list-versions
65
+ cilium-versions: |
66
+ 1.12.5
67
+ 1.13.16
68
+ 1.14.11
69
+ hubble-versions: | -
70
+ 1.12.5
71
+ 1.13.16
72
+ 1.14.11
73
+ ```
74
+
75
+ If the units are all at ` 1.12.5 ` , The next available step would be to ` 1.13.16 ` . Cilium recommends the cni be upgrading through each
76
+ minor release. To get to the latest current supported charm, follow the following steps.
77
+
78
+ ``` sh
79
+ juju config cilium release=1.13.16
80
+ juju-wait
81
+ kubectl get pods -A
82
+ # ensuring that all cilium pods restart on the new image versions
83
+ juju exec cilium/leader -- cilium status
84
+ # ensure that cilium reflects a successful deployment
85
+ ```
86
+
87
+ Then repeat the steps with ` 1.14.11 ` .
88
+
42
89
## Cilium configuration options
43
90
44
91
A full list of Cilium configuration options and their descriptions can be found
0 commit comments