[Proposal] Coverage of all CNPG Operator options in cluster helm chart

[dragoangel]

Hi, wanted to thanks everyone who take a part of CNPG Operator, it rocks! It allows us to manage almost every aspect op PGSQL lifecycle, but current cluster helm chart is far behind from what Operator can provide.

I take some of my time and filled all seeable gaps in helm chart. The change is very big and lacks of auto-tests (this is the reason why I create an issue instead of PR), but I checked most of functionality manually and all looks properly working from my view.

Please check fork at https://github.com/dragoangel/cloudnative-pg-charts/blob/feature/cluster-v2/charts/cluster/values.yaml

Main aspects which was covered compared to official helm chart:

• Helm chart designed with extendibility in mind by utilizing hashKey. Method, topology & providers validated by checking if section exist in corresponding settings. Many other checks are done to prevent users from obvious misconfiguration
• Replica clusters as standalone & distributed topology, promotion/demotion workflow via promotionToken, delayed replicas via minApplyDelay
• Logical replication orchestration: publications and subscriptions
• Support of both new Barman plugin and old build one, ability to set barman.forceUseOf or use auto-selection logic (plugin used if K8s at least v1.29)
• Separation of import bootstrap from recovery for clearness of settings in mind
• High-availability replication slots
• Ability to define own external clusters
• Declarative Database

I would be happy if this changes can be incorporated into official helm chart.

[dosubot[bot]]

Hi, @dragoangel. I'm Dosu, and I'm helping the charts team manage their backlog and am marking this issue as stale.

Issue Summary:

• You proposed expanding the CNPG Operator's cluster Helm chart to cover all operator options and address current gaps.
• You have developed and manually tested a detailed fork with enhanced extensibility, replica cluster topologies, logical replication, Barman plugin support, and declarative database settings.
• You requested that these improvements be merged into the official Helm chart.
• There has been no further discussion or comments on this issue since your initial suggestion.

Next Steps:

• Please let me know if this issue is still relevant to the latest version of the charts repository by commenting here to keep the discussion open.
• If I do not hear back within 7 days, I will automatically close this issue.

Thank you for your understanding and contribution!