Which operator(s) is this request for?
Why this matters
Connecting applications to a Percona MySQL cluster today requires developers to manually piece together credentials, hostnames, and connection strings from multiple sources, creating friction, configuration drift, and a common source of deployment errors. The Connection Details Secret gives every application a single Kubernetes-native object containing everything needed to connect, including proxy-aware URIs that automatically reflect whether HAProxy or MySQL Router is in use. This brings the PS Operator in line with the PG Operator's developer experience and makes Percona MySQL a drop-in fit for modern GitOps and self-service platform workflows.
Jira: https://perconadev.atlassian.net/browse/K8SPS-689
Community Note
- Please vote on this issue by adding a 👍 reaction to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, as they generate noise and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Which operator(s) is this request for?
Why this matters
Connecting applications to a Percona MySQL cluster today requires developers to manually piece together credentials, hostnames, and connection strings from multiple sources, creating friction, configuration drift, and a common source of deployment errors. The Connection Details Secret gives every application a single Kubernetes-native object containing everything needed to connect, including proxy-aware URIs that automatically reflect whether HAProxy or MySQL Router is in use. This brings the PS Operator in line with the PG Operator's developer experience and makes Percona MySQL a drop-in fit for modern GitOps and self-service platform workflows.
Jira: https://perconadev.atlassian.net/browse/K8SPS-689
Community Note