fix: Update registry server install.yaml with new HTTP headers and lo…

…g level value
timmyb824 · Oct 28, 2024 · 69bacdb · 69bacdb
1 parent c6dfd9d
commit 69bacdb
Showing 1 changed file with 6 additions and 4 deletions.
diff --git a/gitops/manifests/registry-server/install.yaml b/gitops/manifests/registry-server/install.yaml
@@ -40,9 +40,9 @@ spec:
           imagePullPolicy: IfNotPresent
           env:
             - name: REGISTRY_HTTP_HEADERS_Access-Control-Allow-Origin
-              value: "[http://registry.local.timmybtech.com]"
+              value: "[http://registry.local.timmybtech.com,https://registry.local.timmybtech.com]"
             - name: REGISTRY_HTTP_HEADERS_Access-Control-Allow-Methods
-              value: "[HEAD,GET,OPTIONS,DELETE]"
+              value: "[HEAD,GET,OPTIONS,DELETE,PUT,POST]"
             - name: REGISTRY_HTTP_HEADERS_Access-Control-Allow-Credentials
               value: "[true]"
             - name: REGISTRY_HTTP_HEADERS_Access-Control-Allow-Headers
@@ -51,14 +51,16 @@ spec:
               value: "[Docker-Content-Digest]"
             - name: REGISTRY_STORAGE_DELETE_ENABLED
               value: "true"
+            - name: REGISTRY_HTTP_SECRET
+              value: "<path:secret/data/argocd#REGISTRY_HTTP_SECRET>"
             - name: REGISTRY_LOG_LEVEL
-              value: "debug"
+              value: "info"
           volumeMounts:
             - name: registry-storage
               mountPath: /var/lib/registry
           ports:
             - containerPort: 5000
-              name: registry
+              name: http
           resources:
             requests:
               cpu: 200m