Added ability to override LATTICE_ENDPOINT env variable with helm (#446)

Co-authored-by: Shawn Kaplan <[email protected]>
aws · Oct 23, 2023 · 7120cce · 7120cce
1 parent 19d3ea7
commit 7120cce
Show file tree

Hide file tree

Showing 4 changed files with 10 additions and 1 deletion.
diff --git a/docs/deploy.md b/docs/deploy.md
@@ -86,7 +86,9 @@ Run through them again for a second cluster to use with the extended example sho
       --set=clusterVpcId= \
       --set=clusterName= \
       --set=awsAccountId= \
-
+      # latticeEndpoint is required for the case where the VPC Lattice endpoint is being overridden
+      --set=latticeEndpoint= \
+   
    ```
 1. Create the `amazon-vpc-lattice` GatewayClass:
    ```bash

diff --git a/helm/templates/configmap.yaml b/helm/templates/configmap.yaml
@@ -7,4 +7,5 @@ data:
     awsAccountId: {{ .Values.awsAccountId | quote }}
     clusterVpcId: {{ .Values.clusterVpcId | quote }}
     clusterName: {{ .Values.clusterName | quote }}
+    latticeEndpoint: {{ .Values.latticeEndpoint | quote }}
 
diff --git a/helm/templates/deployment.yaml b/helm/templates/deployment.yaml
@@ -87,6 +87,11 @@ spec:
               configMapKeyRef:
                 name: env-config
                 key: clusterName
+          - name: LATTICE_ENDPOINT
+            valueFrom:
+              configMapKeyRef:
+                name: env-config
+                key: latticeEndpoint
 
       terminationGracePeriodSeconds: 10
       nodeSelector: {{ toYaml .Values.deployment.nodeSelector | nindent 8 }}

diff --git a/helm/values.yaml b/helm/values.yaml
@@ -75,3 +75,4 @@ awsRegion:
 awsAccountId:
 clusterVpcId:
 clusterName:
+latticeEndpoint: