fix: adjust secret reference formatting and add service account configuration for Azure AKS

Author: emmanuelmathot

helm-chart/eoapi/Chart.yaml

@@ -15,7 +15,7 @@ kubeVersion: ">=1.23.0-0"
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: "0.5.3-azure-test-5"
+version: "0.5.3-azure-test-6"
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to

helm-chart/eoapi/templates/services/deployment.yaml

@@ -87,9 +87,9 @@ spec:
         - secretRef:
             name: pgstac-secrets-{{ $.Release.Name }}
         {{- end }}
-        # TODO (emmanuel): choose another name to not mix up with the db secret if internal DB
+          # TODO (emmanuel): choose another name to not mix up with the db secret if internal DB
         {{- if $.Values.azure.aksSecretsProviderAvailable }}
-         - secretRef:
+        - secretRef:
             name: pgstac-secrets-{{ $.Release.Name }}
         {{- end }}
         {{- if index $v "settings" "envSecrets" }}

helm-chart/eoapi/values.yaml

@@ -409,6 +409,8 @@ docServer:
 # and we use this when using Azure managed postgres to pass in the DB creds.
 azure:
   aksSecretsProviderAvailable: false
+  serviceAccount:
+    create: false
   keyvault:
     name: ""
     clientId: ""