You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{- if eq .Values.opaWebhook.failurePolicy "Fail" }}
15
9
16
10
WARNING!!!
17
11
opaWebhook.failurePolicy is Fail, You need to delete validatingwebhookconfiguration before uninstall, if webhook exists without chart resources you can’t create resources in your cluster!
18
12
{{- end }}
19
-
20
-
{{- if .Values.crdCache.enabled }}
21
-
{{- if eq .Values.crdCache.argoCDCompatibilityMode "none" }}
22
-
23
-
NOTE: ArgoCD Compatibility
24
-
You have enabled CRD-based caching. The cache secrets are modified at runtime by the
25
-
admission controller, which will cause ArgoCD to mark your application as out-of-sync.
26
-
27
-
If you are not using ArgoCD, you can ignore the following section.
28
-
29
-
To prevent this, you have two options:
30
-
31
-
Option 1: Configure ArgoCD to ignore differences in the cache secret's data field.
32
-
Add the following to your ArgoCD Application manifest under spec.ignoreDifferences:
33
-
34
-
{{- $enabledTypes := include "wiz-admission-controller.enabledRunnerTypes" . | fromJsonArray }}
35
-
{{- range $runnerType := $enabledTypes }}
36
-
- group: ""
37
-
kind: Secret
38
-
name: {{ include "wiz-admission-controller.cacheSecretName" $runnerType }}
39
-
namespace: {{ $.Release.Namespace }}
40
-
jsonPointers:
41
-
- /data
42
-
{{- end }}
43
-
44
-
Option 2: Set crdCache.argoCDCompatibilityMode to "helm-hook" in your values.yaml.
45
-
This will add Helm hooks to the cache secrets, preventing ArgoCD from tracking them.
46
-
Note: You will need to manually delete the cache secrets after uninstalling the chart.
0 commit comments