percona / percona/percona-postgresql-operator

Add ExternalDNS integration via external.hostname

Open
#1,796 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request jira-task PG Proposed
Dominant language
Go
Stars
385
Forks
83
Avg merge
2d 5h
Merged PRs (30d)
39

Description

Proposal

Add support for automatically managing external DNS records for PostgreSQL clusters through the ExternalDNS Operator.

Similar to the ExternalDNS integration available in PSMDB, the PostgreSQL Operator could allow users to configure an external hostname and have the Operator add the appropriate ExternalDNS annotations to the externally exposed Service.

This would provide a declarative way to configure a stable DNS name for a PostgreSQL cluster and would also complement the cert-manager integration.

Use-Case

Currently, users who expose PostgreSQL externally need to manage DNS records separately or manually add ExternalDNS annotations to the generated Services.

This becomes particularly important when using cert-manager

Is this a feature you are interested in implementing yourself?

Maybe

Anything else?

I think all spec.*.external that exists should have the hostname specification

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by examining the existing ExternalDNS integration in PSMDB and the PostgreSQL Operator's spec.*.external configuration and generated externally exposed Services. Done means an external hostname can declaratively add the appropriate ExternalDNS annotations across the relevant external specifications while complementing cert-manager integration.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes, postgresql
Domain
databases, devops, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.