Add GCP secret provider support#3308
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## choreo #3308 +/- ##
======================================
Coverage 0.60% 0.60%
======================================
Files 42 42
Lines 4809 4809
======================================
Hits 29 29
Misses 4780 4780
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Purpose
This pull request adds support for Google Cloud Platform (GCP) as a secret provider in the Helm charts, alongside the existing AWS support. It introduces a new SecretProviderClass template for GCP and updates deployment templates to handle both AWS and GCP providers. The chart version is also incremented to reflect these changes.
Purpose
Secret provider enhancements:
secret-provider-gcp.yamltemplate to configure GCP as a SecretProviderClass, enabling Kubernetes deployments to fetch secrets from GCP Secret Manager.adapter-deployment.yaml,common-controller-deployment.yaml,gateway-runtime-deployment.yaml,ratelimiter-deployment.yaml) to support both AWS and GCP as secret providers by modifying conditional logic to check for either provider.Chart versioning:
1.3.0-25to1.3.0-26inChart.yamlto reflect the new features.