[HELM] - Switching to Helm Webhooks (#1536)

Previously the webhooks were managed by the controller itself; we've move this to being managaed as part of the helm deployment itself now
appvia · Oct 24, 2024 · 6ebb808 · 6ebb808
1 parent 107a53a
commit 6ebb808
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/charts/terranetes-controller/Chart.yaml b/charts/terranetes-controller/Chart.yaml
@@ -3,7 +3,7 @@ apiVersion: v2
 name: terranetes-controller
 description: Controller used to provision a terraform workflow within kubernetes
 type: application
-version: v0.7.21
+version: v0.7.22
 appVersion: v0.4.16
 sources:
   - https://github.com/appvia/terranetes-controller

diff --git a/charts/terranetes-controller/values.yaml b/charts/terranetes-controller/values.yaml
@@ -73,10 +73,10 @@ controller:
   enableWatchers: true
   ## Indicates we should forgo the controller registering it's own webhooks and allowing
   ## helm to manage the webhooks for us
-  enableHelmWebhookRegistration: false
+  enableHelmWebhookRegistration: true
   ## indicates if the controller should register the validation and mutation webhooks
   ## for the Configuration, Revision and CloudResource resources
-  enableControllerWebhookRegistration: true
+  enableControllerWebhookRegistration: false
   # indicates if namespace deletion should be blocked if the namespace contains one
   # or more Configuration resources, forcing the user to delete correctly
   enableNamespaceProtection: false