Skip to content

Fix Act-3 ArgoCD demo deployment#32

Open
github-actions[bot] wants to merge 1 commit intomainfrom
fix/cluster-doctor/issue-31-20260312
Open

Fix Act-3 ArgoCD demo deployment#32
github-actions[bot] wants to merge 1 commit intomainfrom
fix/cluster-doctor/issue-31-20260312

Conversation

@github-actions
Copy link

Summary

  • switch Act-3/argocd-test-app.yaml to deploy a healthy manifest directory
  • add Act-3/argocd/deploy/aks-store-all-in-one.yaml as the reconciled workload set
  • preserve the intentionally broken manifest under Act-3/argocd/apps/ for workshop failure analysis

Why

Issue #31 shows the ArgoCD app agentic-platform-engineering-demo as Synced but Degraded. The repo currently points ArgoCD at Act-3/argocd/apps, which only contains the intentionally broken workshop manifest. That manifest includes multiple runtime-breaking changes (for example ordr-service image typo, incorrect RabbitMQ credentials, and removed/altered probes), so ArgoCD can sync successfully while the workloads remain unhealthy.

Validation

  • az aks show confirmed cluster msftgbb in resource group agentic-platform-engineering is healthy and running, which lowers confidence in a control-plane issue.
  • kubectl apply --dry-run=client --validate=false -f Act-3/argocd-test-app.yaml
  • kubectl apply --dry-run=client --validate=false -f Act-3/argocd/deploy/aks-store-all-in-one.yaml
  • git diff --check

Rollback

Revert this PR to make the sample app deploy the intentionally broken manifest again.

Keep the intentionally broken manifest for workshop analysis, but deploy the healthy manifest by default so the sample ArgoCD app can reconcile successfully.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.

0 participants