loc_az_hci/docs/temporary/DEPLOYMENT_BLOCKERS.md

Deployment Blockers

Current Status

✅ Working Components

• Proxmox ML110: Connected and operational
• Proxmox R630: Connected and operational
• Cloudflare API: Connected and authenticated
• Cloudflare Zone: d-bis.org (active)
• Cloudflare Tunnel Token: Available

⚠️ Blockers

Azure Subscription Read-Only Mode

Issue: All available Azure subscriptions are in read-only mode, preventing:

• Resource group creation
• Azure Arc onboarding
• Any write operations

Affected Subscriptions:

1. Digital Bank of International Settlements (fc08d829-4f14-413d-ab27-ce024425db0b)
2. MIM4U (6d3c4263-bba9-497c-8843-eae6c4e87192)
3. Landrum Law (70569bdd-de60-4dd1-838e-5fde7f91fe8d)
4. International Criminal Court of Commerce (88e5f6a1-ab86-4a86-9e91-831ed63fed81)

Root Cause: Likely billing/payment issue or account-level restriction

Resolution Steps

1. Check Azure Portal

• Navigate to: https://portal.azure.com
• Go to: Subscriptions → Check each subscription status
• Look for: Billing alerts, payment issues, or restrictions

2. Contact Azure Support

• Open support ticket for subscription activation
• Provide subscription IDs that need re-enabling
• Request removal of read-only restriction

3. Alternative: Continue Without Azure Arc

While waiting for Azure resolution, you can:

• ✅ Deploy VMs on Proxmox
• ✅ Configure Cloudflare Tunnel
• ✅ Set up Kubernetes (K3s)
• ✅ Deploy applications
• ⏸️ Onboard to Azure Arc later (once subscription enabled)

Workarounds

Proceed with Local Deployment

All infrastructure can be deployed and configured locally:

1. Create VMs using Terraform or Proxmox UI
2. Configure Cloudflare Tunnel (tunnel token available)
3. Deploy Kubernetes cluster
4. Deploy applications
5. Onboard to Azure Arc when subscription is enabled

Update .env for Alternative Subscription

If you get access to a working subscription:

# Update subscription ID in .env
AZURE_SUBSCRIPTION_ID=new-subscription-id

# Then create resource group
az group create --name HC-Stack --location eastus

Next Actions

1. Resolve Azure subscription issue (priority)
2. Or proceed with local deployment (workaround)
3. Onboard to Azure Arc once subscription is enabled

Files Ready for Deployment

• ✅ All scripts prepared and tested
• ✅ Terraform configurations ready
• ✅ Connection tests passing
• ✅ Documentation complete

Status: Ready to deploy once Azure subscription is enabled, or proceed with local-only deployment.