Git-Mirrors/constellation
1
0
Fork 0
mirror of https://github.com/edgelesssys/constellation.git synced 2024-10-01 01:36:09 -04:00
Code Issues Packages Projects Releases Wiki Activity
6323bd774d
constellation/cli/internal/helm
History
Otto Bittner efcd0337b4
Microservice upgrades (#729) 
Run with: constellation upgrade execute --helm.
This will only upgrade the helm charts. No config is needed.

Upgrades are implemented via helm's upgrade action, i.e. they
automatically roll back if something goes wrong. Releases could 
still be managed via helm, even after an upgrade with constellation
has been done.

Currently not user facing as CRD/CR backups are still in progress.
These backups should be automatically created and saved to the 
user's disk as updates may delete CRs. This happens implicitly 
through CRD upgrades, which are part of microservice upgrades.
2022-12-19 16:52:15 +01:00
..
charts kubernetes: use new registry 2022-12-13 16:08:19 +01:00
testdata Bump version to v2.3.0 2022-12-12 17:45:35 +01:00
cilium.patch deploy cilium via helmchart (#321) 2022-08-12 10:20:19 +02:00
client_test.go Microservice upgrades (#729) 2022-12-19 16:52:15 +01:00
client.go Microservice upgrades (#729) 2022-12-19 16:52:15 +01:00
generateCertManager.sh AB#2589: Deploy operators via Helm (#575) 2022-11-21 10:35:40 +01:00
generateCilium.sh AB#2554 GCP CSI driver deployment (#532) 2022-11-18 10:05:02 +01:00
loader_test.go Microservice upgrades (#729) 2022-12-19 16:52:15 +01:00
loader.go Microservice upgrades (#729) 2022-12-19 16:52:15 +01:00
README.md Microservice upgrades (#729) 2022-12-19 16:52:15 +01:00
update-csi-charts.sh Pull in CSI chart from release tag (#757) 2022-12-09 08:32:58 +01:00
values.go metadata: move subnetCIDR to InstanceMetadata 2022-11-02 23:29:04 +01:00

README.md

Chart upgrades

All services that are installed via helm-install are upgraded via helm-upgrade. Two aspects are not full covered by running helm-upgrade: CRDs and values. While helm-install can install CRDs if they are contained in a chart's crds folder, upgrade won't change any installed CRDs. Furthermore, new values introduced with a new version of a chart will not be installed into the cluster if the --reuse-values flag is set. Nevertheless, we have to rely on the values already present in the cluster because some of the values are set by the bootstrapper during installation. Because upgrades should be a CLI-only operation and we want to avoid the behaviour of --reuse-values, we fetch the cluster values and merge them with any new values.

Here is how we manage CRD upgrades for each chart.

Cilium

  • CRDs are updated by cilium-operator.

cert-manager

  • installCRDs flag is set during upgrade. This flag is managed by cert-manager. cert-manager is in charge of correctly upgrading the CRDs.
  • WARNING: upgrading cert-manager might break other installations of cert-manager in the cluster, if those other installation are not on the same version as the Constellation-manager installation. This is due to the cluster-wide CRDs.

Operators

  • Manually update CRDs before upgrading the chart. Update by running applying the CRDs found in the operators/crds/ folder.

Constellation-services

  • There currently are no CRDs in this chart.