zalando / zalando/postgres-operator

Add custom volumes in OperatorConfiguration

Open
#1,322 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
Go
Stars
5.2k
Forks
1.1k
Avg merge
2d 16h
Merged PRs (30d)
3

Description

Please, answer some short questions which should help us to understand your problem / question better?

  • Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.6.0
  • Where do you run it - cloud or metal? Kubernetes or OpenShift? metal Kubernetes
  • Are you running Postgres Operator in production? yes
  • Type of issue? feature request

Is it possible to add custom volume mounts globally? We need to connect the sidecar with the config in OperatorConfiguration. If we add to "postgresql", then we have to copy the same records for each postgresql instance

apiVersion: "acid.zalan.do/v1"
kind: OperatorConfiguration
metadata:
  name: postgresql-operator-configuration
configuration:
...
  sidecars:
    - name: fluentbit
      image: grafana/fluent-bit-plugin-loki:2.1.0-amd64
      imagePullPolicy: "IfNotPresent"
      volumeMounts:
        - name: fluent-config
          mountPath: /fluent-bit/etc
...

Desired feature:

apiVersion: "acid.zalan.do/v1"
kind: OperatorConfiguration
metadata:
  name: postgresql-operator-configuration
configuration:
...
  volumes:
    - name: fluent-config
      configMap:
        name: fluent-configmap
...
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: fluent-configmap
  namespace: default
data:
  fluent-bit.conf: |-
...

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 tracing how OperatorConfiguration and the existing sidecars configuration are handled when PostgreSQL clusters are generated. Check how volumeMounts are currently represented and propagated, then define the corresponding global volumes behavior and verify that generated clusters can mount the referenced ConfigMap.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.