feat( cluster ): plugins and barman cloud cnpg-i plugin support#924
Open
itay-grudev wants to merge 44 commits into
Open
feat( cluster ): plugins and barman cloud cnpg-i plugin support#924itay-grudev wants to merge 44 commits into
itay-grudev wants to merge 44 commits into
Conversation
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
This was referenced Jul 2, 2026
Signed-off-by: Nolan Gilley <nkgilley@gmail.com> Signed-off-by: Jan Larwig <jan@larwig.com> Signed-off-by: Itay Grudev <itay+github.com@grudev.com> Co-authored-by: Nolan Gilley <nkgilley@gmail.com> Co-authored-by: Itay Grudev <itay+github.com@grudev.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
…uster Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
…only Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
…ions Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
20e887c to
0ac2b24
Compare
The barman-plugin-migration chainsaw test fails consistently in CI. The migration itself works correctly (verified against operator source and the plugin migration docs); the failures are in test assertions of transient states, plus one secret-name typo. - Migration 'Upgrading cluster' phase (step 4): status.phase is set for only a fraction of a second (the operator models rollouts as PhaseUpgrade -> PhaseWaitingForInstancesToBeActive, see tests/e2e/probes_test.go), and helm --wait does not gate CNPG CRDs, so polling always missed it. Replaced with a polling assert on the persistent UpgradingInstance Event. - Backup 'running' phase (step 5): the backup completes in ~10s, faster than polling. Replaced with a polling assert on the persistent backup 'Starting' Event (backup_controller.go:337). - PITR secret name (step 8): referenced recovery-backup-pitr-superuser (release name) instead of recovery-backup-pitr-cluster-superuser (cluster name), causing CreateContainerConfigError. Fixed. Verified end-to-end in isolated fork CI (identical test( cluster ) workflow), including PITR recovery. Signed-off-by: Abdullah Alaqel <abdullah.t.aqeel@gmail.com> Signed-off-by: Abdullah Alaqeel <abdullah.t.aqeel@gmail.com>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
Signed-off-by: Itay Grudev <itay@verito.digital>
This was referenced Jul 6, 2026
The barman-plugin-scheduledbackups test intermittently fails with 'context deadline exceeded' during cleanup. The chart forces immediate: true on scheduled backups (templates/scheduled-backups.yaml), so a backup is still running when cleanup starts; Barman blocks instance shutdown until it completes, pushing teardown past the 5m cleanup budget on GitHub runners. Expose cluster.stopDelay in the chart (values + schema + template), mapping to the CNPG Cluster spec.stopDelay, which also sets the pod's terminationGracePeriodSeconds. The scheduledbackups test sets stopDelay: 30 so the instance is force-stopped promptly at teardown, interrupting the still-running backup. That's acceptable because this test only verifies a backup is started from the ScheduledBackup; backup success is covered by barman-plugin-backup-restore. Result: passes reliably and runs in ~75s (down from ~6m, previously timing out). Verified green in fork CI. This is the 'help it clean up faster' approach rather than raising the cleanup timeout. Supersedes #940. Supplements #924. Signed-off-by: Abdullah Alaqeel <abdullah.t.aqeel@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Migrating from the Built-in CloudNativePG Backup to the Barman Cloud CNPG-I
plugin is a straightforward, single step process, as the chart creates the
necessary
ObjectStoreresource as a helm hook before the cluster is updated.All you have to do is change the backup method from
barmanObjectStoretopluginand specify the plugin name. The same change should also be applied toyour scheduled backups.
closes: #830
closes: #910
closes: #838
closes: #775