Repository navigation
Conversation
A Backup or ScheduledBackup without method: plugin falls back to the default barmanObjectStore method. The operator then requires a .spec.backup section in the Cluster, which a Cluster using the plugin usually does not have, and the backup fails with "cannot proceed with the backup as the cluster has no backup section". Add this to the list of immediate backup failures, with the fix for Backup and ScheduledBackup resources and for kubectl cnpg backup, as discussed in cloudnative-pg#353. Assisted-by: Claude Opus 5.5 Signed-off-by: YoungjuKim <[email protected]>
mnencia
force-pushed
the
docs-troubleshooting-no-backup-section
branch
from
November 9, 2026 16:23
d2613f6 to
7123c82
Compare
leonardoce
approved these changes
Nov 9, 2026
mnencia
force-pushed
the
docs-troubleshooting-no-backup-section
branch
from
November 9, 2026 16:31
9fc626c to
e3e226d
Compare
The failure is set on the Backup status and events, and the backup never starts. The kubectl cnpg example now uses the long flags, like the usage page. Assisted-by: Claude Sonnet 5.5 Signed-off-by: Marco Nenciarini <[email protected]>
mnencia
force-pushed
the
docs-troubleshooting-no-backup-section
branch
from
November 9, 2026 16:32
e3e226d to
6c0269d
Compare
mnencia
approved these changes
Nov 9, 2026
leonardoce
approved these changes
Nov 9, 2026
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.
Backups without
method: pluginfall back tobarmanObjectStore, which needs a.spec.backupsection in theCluster. AClusterthat uses the plugin usually has none, so the backup fails with "cannot proceed with the backup as the cluster has no backup section". Add this error to the "Backup job fails immediately" entries of the troubleshooting guide, with the fix forBackup,ScheduledBackupandkubectl cnpg backup.Closes #1165
Assisted-by: Claude
Original description by the author:
Closes #1165
Adds the error
cannot proceed with the backup as the cluster has no backup sectionto "Backup job fails immediately" introubleshooting.md.The cause is a
BackuporScheduledBackupwithoutmethod: plugin:methoddefaults to
barmanObjectStore, and the operator then requires a.spec.backupsection that a Cluster using the plugin usually does not have(
internal/controller/backup_controller.goin the operator). The entry showsthe fix for the resources and for
kubectl cnpg backup(-m plugin --plugin-name barman-cloud.cloudnative-pg.io), as discussed in #353.How I checked: on CNPG 1.30,
kubectl explain backup.spec.methodand theBackupandScheduledBackupCRDs both show thebarmanObjectStoredefault.I hit the error with a
ScheduledBackupafter migrating to the plugin, andadding
method: pluginfixed it.This change was drafted with AI assistance and reviewed by me.
🤖 Generated with Claude Code