IBM / trusted-service-identity

Trusted Service Identity is closing the gap of preventing access to secrets by an untrusted operator during the process of obtaining authorization for data access by the applications running in the public cloud.
Apache License 2.0
27 stars 11 forks source link

Disable CRD deletion while executing helm unistall or upgrade #145

Closed mrsabath closed 2 years ago

mrsabath commented 2 years ago

Signed-off-by: Mariusz Sabath mrsabath@gmail.com

mrsabath commented 2 years ago

Tested successfully:

trusted-service-identity$helm ls
NAME    NAMESPACE   REVISION    UPDATED                                 STATUS      CHART           APP VERSION
spire   default     1           2022-08-23 14:36:25.011257 -0400 EDT    deployed    spire-1.0.2     0.1        
tornjak default     1           2022-08-22 17:53:21.453883 -0400 EDT    deployed    tornjak-1.0.2   0.1        
trusted-service-identity$helm uninstall spire
These resources were kept due to the resource policy:
[CustomResourceDefinition] spiffeids.spiffeid.spiffe.io

release "spire" uninstalled
trusted-service-identity$k -n spire get po
No resources found in spire namespace.
trusted-service-identity$k -n spire get spiffeid
No resources found in spire namespace.
trusted-service-identity$k -n spire get crd
NAME                           CREATED AT
spiffeids.spiffeid.spiffe.io   2022-08-23T18:36:25Z
mrsabath commented 2 years ago

Fixes #144 . Need to move CRD to crds directory after next release