fix: use ingress resource in the chart

konstructio · Oct 23, 2024 · 1026648 · 1026648
1 parent 547767d
commit 1026648
Show file tree

Hide file tree

Showing 4 changed files with 10 additions and 63 deletions.
diff --git a/flappy-kray/components/flappy-kray/application.yaml b/flappy-kray/components/flappy-kray/application.yaml
@@ -25,6 +25,7 @@ spec:
 
         ingress:
           enabled: true
+          # className: 
           annotations:
             cert-manager.io/cluster-issuer: letsencrypt-prod
             argocd.argoproj.io/sync-wave: '1'

diff --git a/flappy-kray/components/flappy-kray/ingress.yaml b/flappy-kray/components/flappy-kray/ingress.yaml
diff --git a/goldilocks/components/goldilocks/application.yaml b/goldilocks/components/goldilocks/application.yaml
@@ -20,22 +20,20 @@ spec:
       dashboard:
         ingress:
           enabled: true
-
-          # dashboard.ingress.ingressClassName -- From Kubernetes 1.18+ this field is supported in case your ingress controller supports it. When set, you do not need to add the ingress class as annotation.
-          ingressClassName:
-          annotations: {}
-            # kubernetes.io/ingress.class: nginx
-            # kubernetes.io/tls-acme: "true"
+          # ingressClassName: 
+          annotations: 
+            cert-manager.io/cluster-issuer: letsencrypt-prod
+            argocd.argoproj.io/sync-wave: '1'
           hosts:
-            - host: chart-example.local
+            - host: goldilocks.<DOMAIN_NAME>
               paths:
                 - path: /
                   type: ImplementationSpecific
 
-          tls: []
-          #  - secretName: chart-example-tls
-          #    hosts:
-          #      - chart-example.local
+          tls:
+          - secretName: goldilocks-tls
+            hosts:
+              - goldilocks.<DOMAIN_NAME>
   destination:
     name: <CLUSTER_DESTINATION>
     namespace: goldilocks

diff --git a/goldilocks/components/goldilocks/ingress.yaml b/goldilocks/components/goldilocks/ingress.yaml