cloudnative-pg / cloudnative-pg/plugin-barman-cloud

[Feature request] Enhanced information related to WAL archiving

Ouverte
#629 1 commentaire 2 réactions 0 personnes assignées Voir sur GitHub
enhancement
Langage dominant
Go
Étoiles
191
Forks
72
Merge moyen
1 j 16 h
PR mergées (30 j)
18

Description

The new `ObjectStore` CRD status that the barman cloud plugin introduces has taken over some of the backup-related information from the `Cluster` spec:
* the first recoverability point
* the last successful backup
* the last failed backup
They are all set together in this struct called RecoverabilityWindow, but in truth, for a continuous backup, these are not exactly the limits of the recoverability window, because on top of the last successful backup there can be wal files that essentially extend it.
Therefore i think this information would be more valuable if it also shows information about the last archived WAL file (or the last archived WAL file that was streamed up into the object store being modeled by this CRD).

I noticed in the last release this PR https://github.com/cloudnative-pg/cloudnative-pg/pull/8780 shows more complete information about the WAL, i think including that in the `ObjectStore` status can be a good addition. It would allow more programatic access to this data instead of needing to use the `kubectl cnpg status` command separately or look into the prometheus metrics.

This is of course assuming this plugin is also used for WAL archiving, but as far as i’ve seen it is the only recommended option.

Guide de contribution

Ouvrir le guide de contribution

Piste de recherche

Commencez par examiner le statut du CRD ObjectStore et les champs RecoverabilityWindow décrits dans l’issue, puis comparez les informations WAL ajoutées dans la PR #8780. Vérifiez comment kubectl cnpg status et les métriques Prometheus obtiennent actuellement ces données. La tâche est terminée lorsque le statut d’ObjectStore expose les informations pertinentes sur le dernier WAL archivé pour un accès programmatique.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
go, kubernetes, postgresql
Domaine
backend-api-design, databases
Type d'issue
Fonctionnalité
Difficulté
4/5
Temps estimé
3-5 jours
Activité
Calme
Clarté
Plutôt claire
Accessibilité débutants
48/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.