feat: allow use of existing or Helm-managed ai-external-secret in deployment

- Updated deployment.yaml to support referencing a user-provided Secret for AI external API key, with fallback to Helm-managed creation.
- Added ai-external-secret.yaml template to optionally create the secret from values if not provided.

Author: CodeTogetherBot

charts/intel/templates/ai-external-secret.yaml

@@ -1,11 +1,11 @@
-{{- if and .Values.ai.enabled (eq .Values.ai.mode "external") }}
+{{- if and .Values.ai.enabled (eq .Values.ai.mode "external") (or (not .Values.ai.externalSecret.name) .Values.ai.externalSecret.create) }}
 apiVersion: v1
 kind: Secret
 metadata:
-  name: ai-external-secret
+  name: {{ .Values.ai.externalSecret.name | default (printf "%s-ai-external-secret" (include "codetogether.fullname" .)) }}
   namespace: {{ .Release.Namespace }}
 type: Opaque
 stringData:
-  api-key: {{ .Values.ai.apiKey | quote }}
+  api-key: {{ .Values.ai.externalSecret.apiKey | quote }}
 {{- end }}
 

charts/intel/templates/deployment.yaml

@@ -55,7 +55,7 @@ spec:
             - name: AI_EXTERNAL_API_KEY
               valueFrom:
                 secretKeyRef:
-                  name: ai-external-secret
+                  name: {{ .Values.ai.externalSecret.name | default (printf "%s-ai-external-secret" (include "codetogether.fullname" .)) }}
                   key: api-key
               {{- end }}
             {{- end }}