fix: correct typo in order-service image name

[github-actions]

Summary

Fixes #52 - ArgoCD deployment failure for aks-labs-on-tech-connect application.

Root Cause Analysis

The order-service deployment has been failing with ImagePullBackOff errors for the past 8+ hours due to a typo in the container image name.

Evidence Collected

Cluster diagnostics:

• Pod status: order-service-b89d58f55-bnrj5 and order-service-bf95bbdc4-hv654 both in ImagePullBackOff
• Error message: Back-off pulling image "ghcr.io/azure-samples/aks-store-demo/order-servie:2.1.0"
• Event log: Over 2,269 consecutive backoff attempts recorded

Root cause:

• Image name in manifest: ghcr.io/azure-samples/aks-store-demo/order-servie:2.1.0 ❌
• Correct image name: ghcr.io/azure-samples/aks-store-demo/order-service:2.1.0 ✅
• Typo: order-servie vs order-service (missing 'c')

Changes Made

File: Act-3/argocd/apps/broken-aks-store-all-in-one.yaml

• Line 196: Fixed image name from order-servie to order-service

- image: ghcr.io/azure-samples/aks-store-demo/order-servie:2.1.0
+ image: ghcr.io/azure-samples/aks-store-demo/order-service:2.1.0

Impact

Before fix:

• ❌ order-service deployment: 0/1 pods ready
• ❌ Application health: Degraded
• ❌ Sync status: OutOfSync

Expected after merge:

• ✅ ArgoCD will sync the corrected manifest
• ✅ order-service pods will successfully pull the image
• ✅ Application health will return to Healthy
• ✅ All services in the AKS store demo will be operational

Test Plan

1. Merge this PR to main branch
2. ArgoCD should auto-sync (or manual sync if needed): argocd app sync aks-labs-on-tech-connect
3. Verify pod status: kubectl get pods -n default -l app=order-service
4. Expected result: Pod transitions from ImagePullBackOff → Running within 1-2 minutes
5. Verify deployment: kubectl get deployment order-service -n default
6. Expected result: READY: 1/1

Rollback Plan

If issues arise, rollback via:

argocd app rollback aks-labs-on-tech-connect
# or
kubectl rollout undo deployment/order-service -n default

Additional Notes

• This was an intentional typo in the "broken" manifest for demonstration purposes
• All other services are running normally
• No infrastructure or RBAC issues detected
• No changes to secrets, configs, or other resources needed

---

Generated by: Cluster Doctor Agent (Autonomous Kubernetes Diagnostics)
Cluster verified: aks-eastus2 (rg-anyscale-demo)
Analysis timestamp: 2026-02-12T00:51:27Z