Zarf Init against AKS cloud giving ERROR: Unable to estbalish tunnel after 3 attempts

[cheruvu1]

Environment

Device and OS: Source PC: M1 Mac Destination: Azure Cloud - AKS.
App version: Zarf Version# v0.21.2
Kubernetes distro being used: 1.23.8
Other:

Steps to reproduce

1. zarf init

Expected result

ZarfInitConfig should be completed on Azure AKS cluster.

Actual Result

Looks like the HELM install failed with an error “WARNING Unable to complete helm chart install/upgrade”
Deployment is not ready: zarf/zarf-docker-registry. 0 out of 1 expected pods are ready (30m4s)

kubectl -n zarf describe pods.
Events Output: Attached screenshot

zarf init -l=trace
Output attached screenshot:
WARNING Unable to complete helm chart install/upgrade
⠋ Opening tunnel 49804 -> 5000 for svc/zarf-docker-registry in namespace zarf (0s)
• Delay creating tunnel, waiting 10 seconds...
⠋ Opening tunnel 49806 -> 5000 for svc/zarf-docker-registry in namespace zarf (0s)
• Delay creating tunnel, waiting 20 seconds...
⠋ Opening tunnel 49810 -> 5000 for svc/zarf-docker-registry in namespace zarf (0s)
• Delay creating tunnel, waiting 30 seconds...
⠋ Opening tunnel 49812 -> 5000 for svc/zarf-docker-registry in namespace zarf (0s)
ERROR: Unable to estbalish tunnel after 3 attempts

Visual Proof (screenshots, videos, text, etc)

Attached screenshots

Severity/Priority

HIGH

Additional Context

[Noxsios]

injector.log

describe-stage2.log

[Noxsios]

zarf-2022-10-18-17-52-41-3434303561.log

[jeff-mccoy]

Going to close this in favor of the older issue: #592. Good news is we now know what is happening and can explore a couple possible workarounds as we wait for AKS to pickup the containerd patch.