Zarf init errors intermittently when deployed on a k3s cluster with v1.33.6

Environment

App version: Zarf@main Kubernetes distro being used: k3s v1.33.6

Steps to reproduce

This error is intermittent so it doesn't happen everytime.

1. Run a k3s cluster v1.33.6 ( I have heard reports from users that this happens even on v1.33.6 k3s clusters not created through zarf init)
2. Run zarf init --confirm

Expected result

Zarf init completes successfully

Actual Result

https://github.com/zarf-dev/zarf/actions/runs/20029885853/job/57436451232?pr=4435 In case the workflow runs out here are the logs for the component deploy

        	            	2025-12-08 13:56:33 INF deploying component name=zarf-seed-registry
        	            	2025-12-08 13:56:33 INF processing Helm chart name=docker-registry version=1.0.1 source=Zarf-generated
        	            	2025-12-08 13:56:33 INF performing Helm install chart=docker-registry
        	            	2025-12-08 13:56:40 INF running health checks chart=docker-registry
        	            	2025-12-08 13:56:48 INF deploying component name=zarf-registry
        	            	2025-12-08 13:56:48 INF pushing image name=docker.io/library/registry:3.0.0
        	            	2025-12-08 13:56:49 INF pushing image name=docker.io/alpine/socat:1.8.0.3
        	            	2025-12-08 13:56:50 INF done pushing images count=2 duration=1.8s
        	            	2025-12-08 13:56:50 INF processing Helm chart name=docker-registry version=1.0.1 source=Zarf-generated
        	            	2025-12-08 13:56:50 INF performing Helm upgrade chart=docker-registry
        	            	2025-12-08 13:56:52 INF running health checks chart=docker-registry
        	            	2025-12-08 13:56:56 INF processing Helm chart name=raw-init-zarf-registry-registry-connect version=0.1.1765202161 source=Zarf-generated
        	            	2025-12-08 13:56:56 INF performing Helm install chart=raw-init-zarf-registry-registry-connect
        	            	2025-12-08 13:56:57 INF running health checks chart=raw-init-zarf-registry-registry-connect
        	            	2025-12-08 13:56:57 INF processing Helm chart name=raw-init-zarf-registry-kep-1755-registry-annotation version=0.1.1765202161 source=Zarf-generated
        	            	2025-12-08 13:56:57 INF performing Helm install chart=raw-init-zarf-registry-kep-1755-registry-annotation
        	            	2025-12-08 13:56:57 INF running health checks chart=raw-init-zarf-registry-kep-1755-registry-annotation
        	            	2025-12-08 14:11:57 ERR failed to deploy package: unable to deploy component "zarf-registry": local-registry-hosting: ConfigMap not ready, status is Unknown
        	            	context deadline exceeded

Severity/Priority

High

I reproduced this locally with just plain k3s (run with k3d) using this loop:

while true; do
  k3d cluster delete
  k3d cluster create --image rancher/k3s:v1.33.6-k3s1 || continue
  zarf init --confirm || break
done

It's not 100% consistent, but seems to happen intermittently with 1.33.6 on certain machines.

This seems to be a k3s issue, I've created issue https://github.com/k3s-io/k3s/issues/13305 with a lot more detail about this bug and steps to reproduce outside of Zarf