Git-Mirrors/constellation
1
0
Fork 0
mirror of https://github.com/edgelesssys/constellation.git synced 2024-12-12 09:24:24 -05:00
Code Issues Packages Projects Releases Wiki Activity
8f5a2867b4
constellation/cli/internal/helm
History
Adrian Stobbe 22c2a73ae2
cli: store kubernetes version as strong type in config (#2287) 
Co-authored-by: Otto Bittner <cobittner@posteo.net>
Co-authored-by: 3u13r <lc@edgeless.systems>
2023-09-19 13:50:00 +02:00
..
charts cli: remove helm management from join-config (#2251) 2023-08-23 08:14:39 +02:00
imageversion bazel: allow custom container_prefix (#1693) 2023-04-27 11:52:02 +02:00
testdata cli: remove helm management from join-config (#2251) 2023-08-23 08:14:39 +02:00
action.go Retry helm apply on any error (#2322) 2023-09-08 22:54:01 +02:00
actionfactory_test.go cli: check chart versions against target version in users config before upgrading (#2319) 2023-09-08 23:09:02 +02:00
actionfactory.go cli: check chart versions against target version in users config before upgrading (#2319) 2023-09-08 23:09:02 +02:00
BUILD.bazel cli: store kubernetes version as strong type in config (#2287) 2023-09-19 13:50:00 +02:00
chartutil.go cli: save Helm charts to disk before running upgrades (#2305) 2023-09-08 12:02:16 +02:00
cilium.patch deploy cilium via helmchart (#321) 2022-08-12 10:20:19 +02:00
ciliumhelper.go cli: install cilium in cli instead of bootstrapper (#2146) 2023-08-02 15:49:40 +02:00
generateCertManager.sh bazel: add go generate to //:generate target 2023-03-29 12:51:40 -04:00
generateCilium.sh bazel: add go generate to //:generate target 2023-03-29 12:51:40 -04:00
helm_test.go cli: store kubernetes version as strong type in config (#2287) 2023-09-19 13:50:00 +02:00
helm.go cli: store kubernetes version as strong type in config (#2287) 2023-09-19 13:50:00 +02:00
loader_test.go cli: store kubernetes version as strong type in config (#2287) 2023-09-19 13:50:00 +02:00
loader.go cli: store kubernetes version as strong type in config (#2287) 2023-09-19 13:50:00 +02:00
overrides.go cli: helm install and upgrade unification (#2244) 2023-08-24 16:40:47 +02:00
README.md Fix README 2023-07-20 15:47:12 +02:00
release.go cli: helm install and upgrade unification (#2244) 2023-08-24 16:40:47 +02:00
retryaction_test.go Retry helm apply on any error (#2322) 2023-09-08 22:54:01 +02:00
retryaction.go Retry helm apply on any error (#2322) 2023-09-08 22:54:01 +02:00
serviceversion.go cli: output CSI driver versions on status (#2128) 2023-07-27 16:14:36 +02:00
update-aws-load-balancer-chart.sh aws: use new LB controller to fix SecurityGroup cleanup on K8s service deletion (#2090) 2023-07-24 10:30:53 +02:00
update-csi-charts.sh Move CSI charts to separate chart and cleanup loader code 2023-07-20 15:47:12 +02:00
values.go aws: use new LB controller to fix SecurityGroup cleanup on K8s service deletion (#2090) 2023-07-24 10:30:53 +02:00
versionlister.go cli: helm install and upgrade unification (#2244) 2023-08-24 16:40:47 +02:00

README.md

Helm

Constellation uses helm to install and upgrade deployments to the Kubernetes cluster. Helm wraps deployments into charts. One chart should contain all the configuration needed to run a deployment.

Charts used by Constellation

To make installation and lifecycle management easier, Constellation groups multiple related charts into sub-charts. The following "parent" charts are used by Constellation:

  • cert-manager

  • Cilium

  • constellation-services

    Cluster services (mostly) written by us, providing basic functionality of the cluster

  • csi

    Our modified Kubernetes CSI drivers and Snapshot controller/CRDs

  • operators

    Kubernetes operators we use to control and manage the lifecycle of a Constellation cluster

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 applying the CRDs found in the operators/crds/ folder.

Constellation-services

  • There currently are no CRDs in this chart.

CSI

  • CRDs are required for enabling snapshot support
  • CRDs are provided as their own helm chart and may be updated using helm