🚨 ArgoCD Deployment Failed: agentic-platform-engineering-demo

[github-actions]

ArgoCD Deployment Failure

Application: agentic-platform-engineering-demo
Timestamp: 2026-02-17T06:46:20.159Z

Cluster Information

Field	Value
Cluster Name	msftgbb
Resource Group	agentic-platform-engineering
Namespace	default

Application Status

Field	Value
Health Status	Degraded
Sync Status	Synced
Revision	ac1a27dad0e4da399e93ddc0cbb6d4dcec015b20
Repository	https://github.com/microsoftgbb/agentic-platform-engineering.git

Error Message

successfully synced (all tasks run)

Troubleshooting Commands

# Check application status in ArgoCD
argocd app get agentic-platform-engineering-demo

# Check pods in namespace
kubectl get pods -n default

# Describe failed pods
kubectl describe pods -n default

# Get pod logs
kubectl logs -n default <pod-name>

# Check events
kubectl get events -n default --sort-by='.lastTimestamp'

Quick Links

• ArgoCD UI
• Source Repository

---

This issue was automatically created by ArgoCD Notifications

[github-actions]

🔍 Cluster Doctor Diagnostic Report

Status: ✅ Root cause identified and fix committed
Timestamp: 2026-02-17T06:48:37Z
Cluster Identity Verified: ✅ AKS cluster msftgbb in resource group agentic-platform-engineering

---

Root Cause Analysis

Issue Summary

The ArgoCD application agentic-platform-engineering-demo shows Degraded health status due to pod order-service-77bf896788-7f4h9 in ImagePullBackOff state.

Root Cause

Container image name contains a typo: order-servie instead of order-service

Evidence Collected

Pod Status:

NAME                                READY   STATUS             RESTARTS      AGE
order-service-77bf896788-7f4h9      0/1     ImagePullBackOff   0             5m

Error Details:

Failed to pull image "ghcr.io/azure-samples/aks-store-demo/order-servie:2.1.0": 
failed to pull and unpack image: failed to resolve reference: 
failed to authorize: failed to fetch anonymous token: 
unexpected status from GET request to https://ghcr.io/token: 403 Forbidden

Analysis:

• The image repository path contains order-servie (typo) instead of order-service
• This results in a 403 Forbidden error because the image does not exist at that path
• The correct image exists at: ghcr.io/azure-samples/aks-store-demo/order-service:2.1.0

---

Diagnosis Process

1. ✅ Retrieved cluster information and confirmed identity
2. ✅ Queried pod status in namespace default
3. ✅ Identified failing pod with ImagePullBackOff status
4. ✅ Examined pod events showing repeated image pull failures
5. ✅ Analyzed deployment manifest and located typo on line 196
6. ✅ Verified source file: Act-3/argocd/apps/broken-aks-store-all-in-one.yaml

---

Remediation Applied

Changes Made

• File: Act-3/argocd/apps/broken-aks-store-all-in-one.yaml
• Line: 196
• Change: order-servie:2.1.0 → order-service:2.1.0

Git Branch

📝 Branch created: fix/cluster-doctor/issue-8-order-service-image-typo
📝 Commit: 5798a1a

Pull Request

⚠️ Note: GitHub Actions bot lacks permissions to create PRs automatically. A manual PR must be created from the branch:

https://github.com/microsoftgbb/agentic-platform-engineering/compare/fix/cluster-doctor/issue-8-order-service-image-typo

---

Expected Outcome

After merging the fix:

1. ArgoCD will detect the manifest change and sync automatically
2. The deployment will create a new pod with the correct image
3. The new pod will successfully pull order-service:2.1.0 and start
4. The old failed pod will be terminated
5. Application health status will transition from Degraded to Healthy

---

Verification Commands

Monitor the fix deployment:

# Watch pod rollout
kubectl rollout status deployment/order-service -n default

# Verify new pods are running
kubectl get pods -n default -l app=order-service

# Check image pull success
kubectl describe pod -n default -l app=order-service | grep "Successfully pulled"

# Verify ArgoCD application health
argocd app get agentic-platform-engineering-demo

---

Rollback Plan

If issues arise after merge:

git revert 5798a1a
git push origin main

ArgoCD will automatically sync the revert and restore the previous state.

---

Next Steps:

1. Create PR manually from branch fix/cluster-doctor/issue-8-order-service-image-typo
2. Review and merge the PR
3. Monitor ArgoCD sync status
4. Verify application returns to healthy state
5. Close this issue once verified