-
Notifications
You must be signed in to change notification settings - Fork 569
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
Remove environments from Dockerfile #10104
Comments
We would only need to wait for our zeebe-io cluster. Until then we need this as a way to have the dev container available. |
@npepinpe how should we best inform the whole team about this change or is everyone already familiar with ephemeral container usage? |
I could do a short intro to ephemeral containers. I don't think there's enough to make a full techtalk (e.g. 1h of contents), but if there's no topic we could use that slot for a presentation. |
I think anyway only Chris uses the dev image, so at the moment he would be the only one impacted |
Of course, as you're doing this, you could also consider doing the intro to ephemeral containers yourself if you'd like :) |
With the changes I tried debugging via ephemeral containers on a benchmark.
which resulted in
The filesystem of the zeebe process can be accessed via the proc folder:
|
Description
Once we have Kubernetes 1.23+ in all the stages, it would be great to simplify our Dockerfile and remove the
APP_ENV
usage. We won't really need the development version of the image anymore since we will have access to ephemeral containers, letting us attach an image with all our utilities as a sidecar container of our production image.The text was updated successfully, but these errors were encountered: