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

Create new SideCar Environment #1281

Closed
cicdw opened this issue Jul 28, 2019 · 5 comments
Closed

Create new SideCar Environment #1281

cicdw opened this issue Jul 28, 2019 · 5 comments

Comments

@cicdw
Copy link
Member

cicdw commented Jul 28, 2019

In addition to auditing our Docker tasks, we should create a new "Side Car Environment" (or simply add appropriate kwargs to RemoteEnvironment, although this might have compatibility issues with non-k8s deployments) which spins up a side car for k8s jobs making it easier / more off-the-shelf to run Docker tasks in Cloud.

cc: @joshmeek

@joshmeek
Copy link

How specific is this sidecar environment? Static where we have (e.g.) a DockerSideCarEnvironment where it attaches a docker daemon or more generic where you can just specify a pod/container spec to use.

@cicdw
Copy link
Member Author

cicdw commented Jul 29, 2019

Depends on what you think is reasonable; I think we could have a docker spec for specifically using our Docker tasks, but still leave the environment completely configurable for what the side car contains -- what do you think of that?

@joshmeek
Copy link

I'm down for that. So it can be specifiable but we have some documentation on commonly used sidecars?

@cicdw
Copy link
Member Author

cicdw commented Jul 29, 2019

Yea! And even more, we might include some actual template files ¯\_(ツ)_/¯

@joshmeek
Copy link

This was mostly addressed through documentation revolving around deployment patterns e.g. https://docs.prefect.io/cloud/recipes/k8s_docker_sidecar.html

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

No branches or pull requests

2 participants