Skip to content

[Docs]: Deprecate Cluster status fields related to in-tree backup implementation #8051

Description

@mnencia

Is there an existing issue already for your request/idea?

  • I have searched for an existing issue, and could not find anything. I believe this is a new documentation enhancement to be evaluated.

What problem in the existing documentation this issue aims to solve?

The Cluster status includes five fields that display the newest and oldest available backups, as well as the name of the last failed backup. It's important to note that these fields only apply to in-tree backup implementations and cannot be used with CNPG-I backup plugins. Backup plugins manage their own retention policies and may store this information within their configuration objects; for example, the plugin-barman-cloud does this in the ObjectStore status.

Describe what additions need to be done to the documentation

I propose to deprecate the following fields in the Cluster status:

  • firstRecoverabilityPoint
  • firstRecoverabilityPointByMethod
  • lastSuccessfulBackup
  • lastSuccessfulBackupByMethod
  • lastFailedBackup

Describe what pages need to change in the documentation, if any

No response

Describe what pages need to be removed from the documentation, if any

No response

Additional context

I recommend initiating the deprecation process with the upcoming release of version 1.26.1. This move will clearly communicate that these fields do not function with backup plugins, which have been the recommended method for backups since version 1.26.0. Once the in-tree backup implementation is removed, these fields will be forcibly left blank.

Backport?

Yes

Code of Conduct

  • I agree to follow this project's Code of Conduct

Activity

  1. added this to the 1.26.1 milestone on Jul 17, 2025
  2. added theissue type on Jul 17, 2025
  3. added a commit that references this issue on Jul 22, 2025
    278677a
  4. added a commit that references this issue on Jul 22, 2025
    6763103
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

documentation 📖Improvements or additions to documentation

Type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions