v0.8.3: Add Azure AKS deployment support with Key Vault integration and topology constraints#60
v0.8.3: Add Azure AKS deployment support with Key Vault integration and topology constraints#60cosmic-flood merged 6 commits intomainfrom
Conversation
- Deleted outdated AKS deployment files and README. - Added new AKS deployment configuration using Azure Key Vault for secret management. - Updated deployment templates to include topology spread constraints and volume mounts for secrets. - Introduced a comprehensive setup guide for Azure Key Vault integration, detailing steps for creating secrets and configuring access. - Enhanced security practices by integrating managed identities for secret retrieval.
…is configuration - Revised README to clarify deployment with external Azure PostgreSQL and Redis. - Updated `featbit-aks-automatic-via-alb.yaml` with specific external URLs and database configurations. - Ensured secret names align with `keyvault-secret-provider.yaml` for credential management. - Enhanced clarity on prerequisites and setup steps for using Azure Key Vault with FeatBit.
…-via-alb.yaml` to `featbit-aks-automatic-via-lb.yaml` and update references in README
… documentation - Added new README for AKS deployment guide with Traffic Manager and NGINX Ingress. - Introduced `featbit-aks-values.yaml` for standard deployment configurations. - Created `cluster-issuer.yaml` for Let's Encrypt certificate issuers. - Implemented `keyvault-secret-provider.yaml` for Azure Key Vault integration. - Removed outdated AKS example files to streamline the repository. - Updated `.gitignore` to include local configuration files.
|
@copilot please help me to summarize what has been changed, and tell me the potential risks. here's what I did:
please also give me this pull request a title and description of the pull request by changes. basically, all changes are for deploy this helm chart to aks standard (also aks automatic) + azure solution |
|
@cosmic-flood I've opened a new pull request, #61, to work on those changes. Once the pull request is ready, I'll request review from you. |
Extends Helm chart compatibility with Azure Kubernetes Service (AKS Standard and AKS Automatic) through optional template enhancements and production-ready deployment example.
Template Enhancements
Added optional fields to all service deployments (API, UI, ELS, DAS):
volumeMounts/volumes- Azure Key Vault CSI Driver integration for secret managementtopologySpreadConstraints- Pod distribution across nodes/zones for AKS Automatic policy complianceinitContainers.resources- Resource limits/requests for init containers (AKS Automatic requirement)All fields use
{{- with }}conditionals for backward compatibility - existing deployments unaffected.AKS Deployment Example
New
charts/featbit/examples/aks/with production architecture:Internet → Traffic Manager → Azure LB → NGINX Ingress (TLS) → FeatBit
featbit-aks-values.yaml- External PostgreSQL/Redis, Key Vault secrets, autoscaling configkeyvault-secret-provider.yaml- SecretProviderClass for CSI Drivercluster-issuer.yaml- Let's Encrypt staging/production issuersREADME.md- Complete deployment guide: NGINX Ingress setup, cert-manager, Traffic Manager multi-region, troubleshootingConfiguration highlights:
Additional Changes
.gitignore- Added*.local.yamlpattern for local config files