Zack A

> We found that configuring the serviceaccount to use imagepullsecrets also works as an alternative: [kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account) but going to keep this open as the issue itself is still valid as...

Is there a "utility cluster" example coming down the pipe? I think at this point it would basically be airgapping all git repos/images + throwing an ingress on the zarf...

Yeah, this is why we are still using v0.14.0 for our use case - just works out of the box. Haven't had a ton of time to look at all...

Easy bridged networking would be an awesome feature. I have a usecase where I need to run x86 containers in k8s on an m1 mac and have services be exposed...

here is some interesting notes on this https://github.com/clowdhaus/terraform-for-each-unknown

~Can we get one for the `aws-ebs-csi-driver` too please 🙂 ?~

@bryantbiggs Is this what we were waiting for? 🙏 https://github.com/hashicorp/terraform-provider-http/releases/tag/v3.3.0

We ended up just applying the cni configs in the inputs for the EKS addon https://github.com/defenseunicorns/terraform-aws-eks/blob/main/main.tf#L79-L121 additional logic here to create them conditionally but the idea is you can feed...

requesting an easier pattern to set `ZARF_VAR`s Currently now there's no way to set multiple `ZARF_VAR`s that have different values in a single action. Something like how [github actions](https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-environment-variable) implemented...

able to reproduce this when uploading a large binary configmap ~ 1MB through an SSH tunnel against an EKS cluster