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

how should pods be mapped in a docker-compose.yml? #6

Open
jstrachan opened this issue Sep 8, 2015 · 0 comments
Open

how should pods be mapped in a docker-compose.yml? #6

jstrachan opened this issue Sep 8, 2015 · 0 comments

Comments

@jstrachan
Copy link

if you have a docker compose file of 4 containers and 2 are intended to be deployed inside a single pod; I wonder how the pod would be defined in a docker-compose.yml?

Maybe a label/annotation/env var of a pod name so we can associate N of the containers together into a named pod?

BTW great job on compose2kube - I've been pondering that we need a simple, developer centric DSL - like docker compose - for defining the things developers care about in as simple, DRY a way as possible that then generates the k8s JSON/YAML and k8s resources. The tricky bit is how to extend docker compose to add all the stuff developers may wanna optionally specify for k8s specific stuff (e.g. RC auto scaling strategy; how the service should be exposed etc)

I wonder if we need to support a superset of docker compose so we can add in extra stuff thats only used in k8s; but which is easy to strip out so the metadata can still be used on vanilla docker compose?

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

1 participant