From c0ec63270510a5b3997c1e49fa1d882106d8f63f Mon Sep 17 00:00:00 2001
From: nold <nold@gnu.one>
Date: Sun, 16 Feb 2025 16:55:26 +0100
Subject: [PATCH] fix(cert-manager)

---
 projects/core/values/cert-manager.yaml | 25 +------------------------
 1 file changed, 1 insertion(+), 24 deletions(-)

diff --git a/projects/core/values/cert-manager.yaml b/projects/core/values/cert-manager.yaml
index 1d18dce8..b085179a 100644
--- a/projects/core/values/cert-manager.yaml
+++ b/projects/core/values/cert-manager.yaml
@@ -131,30 +131,7 @@ prometheus:
 webhook:
   replicaCount: 1
   timeoutSeconds: 10
-
-  # Used to configure options for the webhook pod.
-  # This allows setting options that'd usually be provided via flags.
-  # An APIVersion and Kind must be specified in your values.yaml file.
-  # Flags will override options that are set here.
-  config:
-    # apiVersion: webhook.config.cert-manager.io/v1alpha1
-    # kind: WebhookConfiguration
-
-    # The port that the webhook should listen on for requests.
-    # In GKE private clusters, by default kubernetes apiservers are allowed to
-    # talk to the cluster nodes only on 443 and 10250. so configuring
-    # securePort: 10250, will work out of the box without needing to add firewall
-    # rules or requiring NET_BIND_SERVICE capabilities to bind port numbers <1000.
-    # This should be uncommented and set as a default by the chart once we graduate
-    # the apiVersion of WebhookConfiguration past v1alpha1.
-    # securePort: 10250
-
-  strategy: {}
-    # type: RollingUpdate
-    # rollingUpdate:
-    #   maxSurge: 0
-    #   maxUnavailable: 1
-
+  #
   # Pod Security Context to be set on the webhook component Pod
   # ref: https://kubernetes.io/docs/tasks/configure-pod-container/security-context/
   securityContext: