From 5215ad91b01741fe8b49cc8fc5c28ff48dc87610 Mon Sep 17 00:00:00 2001 From: James Mellors Date: Wed, 9 Apr 2025 22:48:36 +0100 Subject: [PATCH] updating repo --- argo/controller/sealed-secrets.yaml | 28 +--------------------------- 1 file changed, 1 insertion(+), 27 deletions(-) diff --git a/argo/controller/sealed-secrets.yaml b/argo/controller/sealed-secrets.yaml index c5dccd5..b5665db 100644 --- a/argo/controller/sealed-secrets.yaml +++ b/argo/controller/sealed-secrets.yaml @@ -21,35 +21,9 @@ spec: helm: # Manage configuration through values here or via a values file values: | - # Example: Increase replicas for HA (if needed) - # replicas: 2 + replicas: 1 - # Example: Add resource requests/limits - # resources: - # requests: - # cpu: 100m - # memory: 128Mi - # limits: - # cpu: 200m - # memory: 256Mi - # -- CRITICAL: Decide on CRD management --- - # Option A (Let Helm manage CRDs - Simpler setup, potential issues on Helm upgrades/uninstall): - # installCRDs: true # This flag might exist in some chart versions, check chart docs. - # If not, Helm might install CRDs in templates/crds/ by default. - - # Option B (Recommended by Argo CD for CRDs - Manage CRDs Separately): - # Ensure CRDs are NOT managed by this Helm chart application. - # You would typically manage CRDs using a separate Argo CD Application - # with Sync Waves or apply them manually *before* this app syncs. - # Check the specific chart version's values.yaml for a flag like `crds.create` or similar and set it to `false`. - # If no such flag, Helm <3.x might still install them from templates/crds. - # Let's assume for newer charts you might need to ensure no explicit installCRDs=true is set - # and rely on the separate management described below. - - # Optional: Use a separate values file from your Git repo - # valueFiles: - # - values/sealed-secrets-values.yaml destination: server: https://kubernetes.default.svc # Target namespace for the Sealed Secrets controller deployment itself