zalando / zalando/postgres-operator
Question: Why is it impossible to override external-dns.alpha.kubernetes.io/hostname on cluster-level?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
-
registry.opensource.zalan.do/acid/postgres-operator:v1.10.1 -
Kubernetes [Bare Metal K8s] -
Are you running Postgres Operator in production? [yes] -
Type of issue? [question]
Hi. I want to use external-dns integration, but unfortunately master_dns_name_format is not suitable for me. I searched the documentation and found the line:
external-dns.alpha.kubernetes.io/hostname with the value defined by the operator configs master_dns_name_format and replica_dns_name_format. This value can't be overwritten. If any changing in its value is needed, it MUST be done changing the DNS format operator config parameters
Why can't overriding be done at masterServiceAnnotations/replicaServiceAnnotations level?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the documentation passage describing external-dns.alpha.kubernetes.io/hostname and the master_dns_name_format, replica_dns_name_format, masterServiceAnnotations, and replicaServiceAnnotations settings. Trace how these settings are handled for cluster services, then determine whether annotation overrides are intended to be supported and what documentation or tests would define the completed behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100