-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
devspace open will wait for a init container which is a sidecar #2865
Labels
kind/bug
Something isn't working
Comments
nberlee
added a commit
to nberlee/devspace
that referenced
this issue
Jun 12, 2024
nberlee
added a commit
to nberlee/devspace
that referenced
this issue
Jun 12, 2024
fixes devspace-sh#2865 Signed-off-by: Nico Berlee <nico.berlee@on2it.net>
nberlee
added a commit
to nberlee/devspace
that referenced
this issue
Jun 12, 2024
in order to support initContainer RestartPolicy I had to update client-go to 1.29 fixes devspace-sh#2865 Signed-off-by: Nico Berlee <nico.berlee@on2it.net>
nberlee
added a commit
to nberlee/devspace
that referenced
this issue
Jun 12, 2024
in order to support initContainer RestartPolicy I had to update client-go to 1.29 fixes devspace-sh#2865 Signed-off-by: Nico Berlee <nico.berlee@on2it.net>
nberlee
added a commit
to nberlee/devspace
that referenced
this issue
Jun 12, 2024
fixes devspace-sh#2865 Signed-off-by: Nico Berlee <nico.berlee@on2it.net>
nberlee
added a commit
to nberlee/devspace
that referenced
this issue
Jul 10, 2024
fixes devspace-sh#2865 Signed-off-by: Nico Berlee <nico.berlee@on2it.net>
nberlee
added a commit
to nberlee/devspace
that referenced
this issue
Jul 10, 2024
fixes devspace-sh#2865 Signed-off-by: Nico Berlee <nico.berlee@on2it.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 issuesThe 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
The text was updated successfully, but these errors were encountered: