This repository contains a collection of pre-configured solutions for the KubeRocketCI Kubernetes Cluster deployments. It follows the GitOps methodology and utilizes the ArgoCD App of Apps pattern for streamlined configuration and deployment.
Is your feature request related to a problem? Please describe.
Currently, our Sonar and Keycloak databases lack a robust backup solution, leaving our critical data at risk of loss or corruption. This vulnerability poses a significant operational risk and can potentially lead to downtime and data recovery challenges.
Describe the solution you'd like
I propose implementing backup settings for our Sonar and Keycloak databases using the PostgreSQL Operator (PGO) approach, as provided by Crunchy Data. This method offers a comprehensive and reliable backup and restore system that can be easily integrated into our existing Kubernetes environment. Specifically, I suggest configuring the PostgresCluster resources for both databases with the following specifications to enable automated backups with pgBackRest:
For Sonar Database:
Utilize the pgbackrest backup solution with scheduled full and incremental backups.
Ensure backups are retained for a suitable period, e.g., 14 days, to balance storage use and data recovery needs.
For Keycloak Database:
Similar to the Sonar database, configure pgbackrest for automated backups.
Schedule backups at different intervals to minimize impact on system performance and ensure data redundancy.
Describe alternatives you've considered
While there are other backup solutions available, such as manual backups or third-party services, the PGO approach is specifically designed for PostgreSQL databases running in Kubernetes. It offers seamless integration, Kubernetes-native operations, and the reliability of Crunchy Data's PostgreSQL expertise. This makes it a superior choice for our needs.
Is your feature request related to a problem? Please describe. Currently, our Sonar and Keycloak databases lack a robust backup solution, leaving our critical data at risk of loss or corruption. This vulnerability poses a significant operational risk and can potentially lead to downtime and data recovery challenges.
Describe the solution you'd like I propose implementing backup settings for our Sonar and Keycloak databases using the PostgreSQL Operator (PGO) approach, as provided by Crunchy Data. This method offers a comprehensive and reliable backup and restore system that can be easily integrated into our existing Kubernetes environment. Specifically, I suggest configuring the PostgresCluster resources for both databases with the following specifications to enable automated backups with pgBackRest:
For Sonar Database:
For Keycloak Database:
Describe alternatives you've considered While there are other backup solutions available, such as manual backups or third-party services, the PGO approach is specifically designed for PostgreSQL databases running in Kubernetes. It offers seamless integration, Kubernetes-native operations, and the reliability of Crunchy Data's PostgreSQL expertise. This makes it a superior choice for our needs.
Additional context Examples