zalando / zalando/postgres-operator
Custom CA certificates in Postgres Operator UI
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
- Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.8.2
- Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal K8s (RKE)
- Are you running Postgres Operator in production? We are currently deploying it
- Type of issue? Feature request
We are using Ceph Object Gateway as S3 compatible storage for WAL archiving.
When trying to access the Backups menu in the UI, the following error appears in log file :
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1131)
The following extraEnvs was set in the Helm chart :
extraEnvs:
- name: AWS_ACCESS_KEY_ID
valueFrom:
secretKeyRef:
key: AWS_ACCESS_KEY_ID
name: postgres-pod-secrets
- name: AWS_SECRET_ACCESS_KEY
valueFrom:
secretKeyRef:
key: AWS_SECRET_ACCESS_KEY
name: postgres-pod-secrets
- name: AWS_ENDPOINT
valueFrom:
configMapKeyRef:
key: AWS_ENDPOINT
name: postgres-pod-config
- name: AWS_S3_FORCE_PATH_STYLE
valueFrom:
configMapKeyRef:
key: AWS_S3_FORCE_PATH_STYLE
name: postgres-pod-config
- name: SPILO_S3_BACKUP_BUCKET
value: postgres-operator-wal
The backup from a Postgres cluster works fine thanks to the environment variable WALG_S3_CA_CERT_FILE, but I don't find any way to set a custom ca certificate in the Postgres Operator UI.
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 by inspecting the Helm chart's extraEnvs handling and the UI path that loads the Backups menu. Compare how WALG_S3_CA_CERT_FILE enables the working cluster backup and identify how the operator UI connects to the S3-compatible endpoint. Done means a custom CA certificate can be configured for the UI and the certificate verification error no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, postgresql
- Domain
- databases, frontend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100