cloudnative-pg / cloudnative-pg/plugin-barman-cloud
[Feature request] Enhanced information related to WAL archiving
- Lenguaje dominante
- Go
- Estrellas
- 191
- Forks
- 72
- Merge medio
- 2 d 21 h
- PR fusionados (30 d)
- 21
Descripción
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.
Guía de contribución
Línea de trabajo
Comienza revisando el estado del CRD ObjectStore y los campos RecoverabilityWindow descritos en el issue, y después compara la información de WAL añadida en el PR #8780. Comprueba cómo obtienen actualmente estos datos kubectl cnpg status y las métricas de Prometheus. Se considera terminado cuando el estado de ObjectStore expone la información relevante sobre el último WAL archivado para el acceso programático.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- go, kubernetes, postgresql
- Área
- backend-api-design, databases
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 48/100