Skip to content

K8SPG-963 Documented CR statuses#412

Draft
nastena1606 wants to merge 1 commit into
3.0from
K8SPG-963-Document-cr-status
Draft

K8SPG-963 Documented CR statuses#412
nastena1606 wants to merge 1 commit into
3.0from
K8SPG-963-Document-cr-status

Conversation

@nastena1606

Copy link
Copy Markdown
Collaborator

No description provided.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a dedicated reference page that documents Percona PostgreSQL Custom
Resource (CR) status fields and condition values, and links to it from existing
troubleshooting and standby documentation.

Changes:

  • Add a new cr-statuses.md reference page describing .status fields for
    PerconaPGCluster/Backup/Restore/Upgrade.
  • Add navigation entry for the new page in mkdocs-base.yml.
  • Link to the new reference from docs/debug.md and docs/standby.md.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File Description
mkdocs-base.yml Adds the new “Custom resource statuses” page to the Reference nav section
docs/standby.md Links the StandbyLagging condition mention to the full conditions list
docs/debug.md Aligns troubleshooting guidance with ready status and links to the new reference
docs/cr-statuses.md Introduces a new reference page documenting CR status fields and condition values

Comment thread docs/cr-statuses.md

## How to view custom resource statuses

To check the status of your Percona custom resources, use the `kubectl get <resource-name>` or `kubectl describe <resource-name>` commands. See how to use them to get the quick overview, in-depth details, and targeted queries.
Comment thread docs/cr-statuses.md
Comment on lines +144 to +146
| `RepoDeploymentNotFound` | A pgBackRest repository was not
found during reconciliation |
| `RepoHostCreated` | A pgBackRest repository host was created |
Comment thread docs/cr-statuses.md
| `RepoDeploymentNotFound` | A pgBackRest repository was not
found during reconciliation |
| `RepoHostCreated` | A pgBackRest repository host was created |
| `UnableToCreateStanzas` |
Comment thread docs/debug.md
Comment on lines +21 to 23
The Custom Resource should have `ready` status. See [Custom resource statuses](cr-statuses.md) for other possible values.

!!! note
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants