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

[Feature request] Enhanced information related to WAL archiving

Aperta
#629 1 commento 2 reazioni 0 assegnatari Vedi su GitHub
enhancement
Lingua principale
Go
Stelle
191
Fork
72
Merge medio
2g 21h
PR unite (30g)
21

Descrizione

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.

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Start by reviewing the ObjectStore CRD status and the RecoverabilityWindow fields described in the issue, then compare the WAL information added in PR #8780. Check how kubectl cnpg status and the Prometheus metrics currently obtain this data. Done means the ObjectStore status exposes the relevant last archived WAL information for programmatic access.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
go, kubernetes, postgresql
Ambito
backend-api-design, databases
Tipo di issue
Funzionalità
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Tranquilla
Chiarezza
Abbastanza chiara
Idoneità per principianti
48/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.