Skip to content
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

Support copying binary from init container #108

Open
josephlewis42 opened this issue Feb 9, 2024 · 0 comments
Open

Support copying binary from init container #108

josephlewis42 opened this issue Feb 9, 2024 · 0 comments

Comments

@josephlewis42
Copy link

It would be great if a platform was able to inject an always up to date version of Daytona into arbitrary K8s workloads.

A common way to do this in the K8s world is to create a mutating admission webhook that can rewrite a pod to do the following:

  1. Inject an initContainer and a shared memory volume between the initContainer and the other containers.
  2. Make the binary in the init container copy itself to the shared volume.
  3. Rewrite the command on the application containers to execute the binary that was copied to the shared volume.

If Daytona supported a flag like --copy-to that would allow Daytona to copy itself to a destination then it would be possible to do the above while still using a feature like --secret-env/--entrypoint.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant