Fix CloudSQL proxy labels to not match Backstage service selector
The CloudSQL proxy pod was using backstage.selectorLabels which made it match the Backstage service selector (app.kubernetes.io/name: backstage, app.kubernetes.io/instance: backstage). This caused Traefik to sometimes route requests to the CloudSQL proxy instead of Backstage, resulting in 502 errors. Changed pod labels to use distinct values (backstage-cloudsql-proxy) so the pod is not selected by the Backstage service. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
parent
0590bcb704
commit
c29e1fce46
@ -16,7 +16,8 @@ spec:
|
||||
metadata:
|
||||
labels:
|
||||
app: backstage-cloudsql-proxy
|
||||
{{- include "backstage.selectorLabels" . | nindent 8 }}
|
||||
app.kubernetes.io/name: backstage-cloudsql-proxy
|
||||
app.kubernetes.io/instance: backstage-cloudsql-proxy
|
||||
spec:
|
||||
serviceAccountName: {{ .Values.cloudSqlProxyServiceAccount.name }}
|
||||
automountServiceAccountToken: true
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user