4 Commits

Author	SHA1	Message	Date
Otto Bittner	075a0e0ad6	cli: ask user to confirm cert-manager upgrades	2023-01-05 17:19:05 +01:00
Otto Bittner	e7c7e35f51	cli: create backups for CRDs and their resources ... These backups could be used in case an upgrade misbehaves after helm declared it as successful. The manual backups are required as helm-rollback won't touch custom resources and changes to CRDs delete resources of the old version.	2023-01-05 16:52:06 +01:00
Daniel Weiße	942d11a4c8	Only upgrade helm releases if versions changed (#818) ... Signed-off-by: Daniel Weiße <dw@edgeless.systems>	2022-12-22 12:30:04 +01:00
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