377250ce6a
- Add FreeleapsSecret configuration for Azure Key Vault integration - Move sensitive data (mongodbUri, jwtSecretKey, stripeApiKey, etc.) from config to secrets - Update deployment template to read from both config and FreeleapsSecret - Comment out sensitive fields in chat-config.yaml - Create freeleapssecret.yaml template for secret management - Update both alpha and prod environment configurations
20 lines
634 B
YAML
20 lines
634 B
YAML
apiVersion: freeleaps.com/v1alpha1
|
|
kind: FreeleapsSecret
|
|
metadata:
|
|
name: freeleaps-chat-alpha-secrets
|
|
namespace: {{ .Release.Namespace }}
|
|
spec:
|
|
secretStoreRef:
|
|
kind: {{ .Values.chat.secrets.secretStoreRef.kind }}
|
|
name: {{ .Values.chat.secrets.secretStoreRef.name }}
|
|
target:
|
|
name: {{ .Values.chat.secrets.target.name }}
|
|
creationPolicy: {{ .Values.chat.secrets.target.creationPolicy }}
|
|
refreshInterval: {{ .Values.chat.secrets.refreshInterval }}
|
|
data:
|
|
{{- range .Values.chat.secrets.data }}
|
|
- secretKey: {{ .key }}
|
|
remoteRef:
|
|
key: {{ .remoteRef.key }}
|
|
type: {{ .remoteRef.type }}
|
|
{{- end }} |