charts
charts copied to clipboard
cloudnative-pg
CloudNativePG Helm Charts
Configuration is identical to https://github.com/cloudnative-pg/charts/issues/483 in addition, that the `AZURE_STORAGE_ACCOUNT` has been set. Spinning up a new container causes the following errors: ```txt postgres {"level":"error","ts":"2025-01-04T16:14:24.482164702Z","logger":"wal-archive","msg":"Error invoking barman-cloud-check-wal-archive","logging_pod":"cnpg-cluster-test-1","options":["--cloud-provider","azure-blob-storage","https://myaccount.blob.core.windows.net/postgresql-test","cnpg-cluster-test"],"exitCode":-1,"error":"exit status 2","stacktrace":"github.com/cloudnative-pg/machinery/pkg/log.(*logger).Error\n\tpkg/mod/github.com/cloudnative-pg/[email protected]/pkg/log/log.go:125\ngithub.com/cloudnative-pg/barman-cloud/pkg/walarchive.(*BarmanArchiver).CheckWalArchiveDestination\n\tpkg/mod/github.com/cloudnative-pg/[email protected]/pkg/walarchive/cmd.go:178\ngithub.com/cloudnative-pg/barman-cloud/pkg/archiver.(*WALArchiver).CheckWalArchiveDestination\n\tpkg/mod/github.com/cloudnative-pg/[email protected]/pkg/archiver/archiver.go:131\ngithub.com/cloudnative-pg/cloudnative-pg/pkg/management/postgres/archiver.checkWalArchive\n\tpkg/management/postgres/archiver/archiver.go:320\ngithub.com/cloudnative-pg/cloudnative-pg/pkg/management/postgres/archiver.internalRun\n\tpkg/management/postgres/archiver/archiver.go:191\ngithub.com/cloudnative-pg/cloudnative-pg/pkg/management/postgres/archiver.Run\n\tpkg/management/postgres/archiver/archiver.go:139\ngithub.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/walarchive.NewCmd.func1\n\tinternal/cmd/manager/walarchive/cmd.go:62\ngithub.com/spf13/cobra.(*Command).execute\n\tpkg/mod/github.com/spf13/[email protected]/command.go:985\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tpkg/mod/github.com/spf13/[email protected]/command.go:1117\ngithub.com/spf13/cobra.(*Command).Execute\n\tpkg/mod/github.com/spf13/[email protected]/command.go:1041\nmain.main\n\tcmd/manager/main.go:68\nruntime.main\n\t/opt/hostedtoolcache/go/1.23.4/x64/src/runtime/proc.go:272"} postgres...
I configured the `values.yaml` accordingly to the documentation by providing an existing secret `azure-backup` and the `destinationPath`. One of the given configuration tuples should be enought: ```yaml backups: # --...
Currently, the Helm chart only allows adding additional labels with `podMonitorAdditionalLabels`. Could you extend the Helm chart to also add additional annotations (e.g. `podMonitorAdditionalAnnotations`? I'm using VictoriaMetrics which creates a...
Currently only metrics, query and name are passed to the monitoring configmap. We need to monitor multiple databases and need the target_databases feature from https://cloudnative-pg.io/documentation/current/monitoring/#structure-of-a-user-defined-metric Todos: - pass target_databases to...
This PR add the option to: - configure service resources as described in: https://cloudnative-pg.io/documentation/1.24/service_management/ - adding a ldap configuration
I want to run the cloudnative-pg operator in a namespace on an OpenShift cluster with the helm chart. My user has the project admin role and the cloudnative-pg-admin role. The...
I suspect from the current code, that `region` seems to be used just to infer the S3 endpoint if `endpointURL` is not provided, as seen: https://github.com/cloudnative-pg/charts/blob/main/charts/cluster/templates/_barman_object_store.tpl#L18-L31 However, `region` is important...
When setting up the operator using the chart 0.22.1 from the helm repo the clusterWide feature is not included, although it should be. Using the oci registry works. ## Example...
This should resolve https://github.com/cloudnative-pg/charts/issues/326
