What happened?
In kubernetes 1.29 the Sidecar feature became general available. This means you have a init container which has a restartPolicy: Always runs forever, effectively as a sidecar. This is what istio uses to prevent a lot of issues

The problem is devspace open will wait for the init container to exit, therefore, devspace dev will never continue.

What did you expect to happen instead?
If restartPolicy is defined in the init container it should just continue.

How can we reproduce the bug? (as minimally and precisely as possible)
Use Kubernetes 1.29 or higher. And use a manifest like https://kubernetes.io/docs/concepts/workloads/pods/sidecar-containers/

devspace open wil not continue