You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: