[Bug]: Issue with labels in service selector

[dom0Watt]

Preflight Checklist

• I could not find a solution in the documentation, the existing issues or discussions
• I have joined the ZITADEL chat

Version

8.5.0

App version

v2.61.0

Describe the problem caused by this bug

Hi there,

Just to let you know a small issue with the labels in the service selector.
By default the selectors are
selector: app.kubernetes.io/instance: zitadel app.kubernetes.io/name: zitadel
Which is not enough restrictive because the same labels are used by the init and setup pods.
As the init and setup pods remain in status completed once they ran, the service selector felt down to one of these.

Should be better to be more restritive by adding the app.kubernetes.io/component: or use ttlSecondsAfterFinished field on the jobs to make sure the pods are deleted once they are completed.

To reproduce

1. Deploy zitadel with the default values.
2. Try to port forward the zitadel service.
3. Should lead to an error like "Unable to forward port... pods is in status succeeded, should be running"

Logs

No response

Expected behavior

No response

Relevant Configuration

No response

Additional Context

No response