Operational validation for CNH GitLab 18.7 with OpenBao
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
Complete operational validation scenarios for OpenBao in Cloud Native Hybrid (CNH) environments that couldn't be tested in GitLab 18.6.
Implementation Plan
- GitLab upgrade with OpenBao enabled
- Custom monitoring setup with OpenBao metrics
Further Details
GitLab Upgrade with OpenBao Enabled
What: Upgrade a 3k CNH environment from GitLab 18.7 to a later version with OpenBao enabled, validating that OpenBao continues to function correctly after the upgrade with no data loss or configuration issues.
Why it couldn't be done before: GitLab 18.6 was the only version where OpenBao could be successfully enabled. A data migration was required for upgrades, but the team opted for a reset instead of investing in migration during the beta phase. With 18.7 now available, we can test the upgrade path.
Custom Monitoring Setup with OpenBao Metrics
What: Validate that custom monitoring setup picks up OpenBao metrics in CNH environment and metrics are properly collected and exposed for monitoring systems.
Why it couldn't be done before: This depends on the OpenBao Helm chart 0.10.0 release (see gitlab-org/cloud-native/charts/openbao#31 (closed)), which was not available during 18.6 validation. Monitoring was tested on GitLab Cloud Native (Chart deployment on GKS) but couldn't be tested on CNH (using GET) until the chart release.