Skip to content

Azure deployment - #157

Merged
ahmedyousry27 merged 3 commits into
mainfrom
deployment_backup
Jul 20, 2026
Merged

Azure deployment#157
ahmedyousry27 merged 3 commits into
mainfrom
deployment_backup

Conversation

@ahmedyousry27

Copy link
Copy Markdown
Collaborator

Summary

  • Add a separate Azure AKS deployment path using Terraform.
  • Provision AKS, ACR, networking, a static ingress IP and remote state storage.
  • Add Azure-specific Helm values and manual deployment scripts.
  • Configure Azure RBAC for AKS and Terraform state access.
  • Publish application images to ACR using immutable commit tags.
  • Configure ingress-nginx, cert-manager and HTTPS.
  • Add Azure monitoring and persistent storage support.
  • Fix the Azure load-balancer health probe using /healthz.
  • Keep the existing Rancher deployment unchanged.

Validation

  • Terraform formatting and validation pass.
  • Terraform reports no infrastructure drift after deployment.
  • Both AKS nodes are Ready.
  • All application and monitoring workloads are running.
  • All persistent volume claims are bound using managed-csi.
  • The TLS certificate is Ready.
  • Frontend, Keycloak discovery and user-service health return HTTP 200.
  • All five application images use the immutable ACR tag.
  • Frontend production dependency audit reports zero vulnerabilities.

Security

  • No credentials, API keys, kubeconfig or generated passwords are committed.
  • Real .tfvars, backend.hcl, Terraform plans and state are ignored.
  • AKS API access is restricted by an authorized IP range.
  • Application secrets are stored as Kubernetes Secrets.
  • The public deployment URL is intentionally not added to the README.

@ahmedyousry27 ahmedyousry27 self-assigned this Jul 20, 2026
@AET-DevOps26 AET-DevOps26 deleted a comment from coderabbitai Bot Jul 20, 2026
@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown

Caution

Failed to replace (edit) comment. This is likely due to insufficient permissions or the comment being deleted.

Error details
Not Found - https://docs.github.com/rest/issues/comments#update-an-issue-comment

1 similar comment
@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown

Caution

Failed to replace (edit) comment. This is likely due to insufficient permissions or the comment being deleted.

Error details
Not Found - https://docs.github.com/rest/issues/comments#update-an-issue-comment

@ahmedyousry27
ahmedyousry27 merged commit b03441e into main Jul 20, 2026
10 of 11 checks passed
@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@ahmedyousry27, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 51 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: f8256c78-c1b8-41ba-b8be-2e24a8f06cfc

📥 Commits

Reviewing files that changed from the base of the PR and between 3972e46 and 62c2c27.

📒 Files selected for processing (27)
  • .github/workflows/validate-azure.yml
  • .gitignore
  • README.md
  • docs/README.md
  • docs/azure-deployment.md
  • helm/ingress-nginx-values-azure.yaml
  • helm/team-drops-monitoring/values-azure.yaml
  • helm/team-drops/templates/mongo.yaml
  • helm/team-drops/templates/postgres.yaml
  • helm/team-drops/values-azure.yaml
  • helm/team-drops/values.yaml
  • infra/azure/.terraform.lock.hcl
  • infra/azure/backend.hcl.example
  • infra/azure/bootstrap/.terraform.lock.hcl
  • infra/azure/bootstrap/main.tf
  • infra/azure/bootstrap/outputs.tf
  • infra/azure/bootstrap/terraform.tfvars.example
  • infra/azure/bootstrap/variables.tf
  • infra/azure/bootstrap/versions.tf
  • infra/azure/main.tf
  • infra/azure/outputs.tf
  • infra/azure/terraform.tfvars.example
  • infra/azure/variables.tf
  • infra/azure/versions.tf
  • scripts/azure/deploy.sh
  • scripts/azure/get-credentials.sh
  • scripts/azure/publish-images.sh
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch deployment_backup

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant