Skip to content

Support for network_mode: service:* #1846

@jan-hudec

Description

@jan-hudec

What would you like to be added?

When a service has network_mode of the form service:anotherservice, it should be added as a second container into the deployment of anotherservice instead of getting its own deployment. Because this specification means the services will see each other on localhost, which roughly corresponds to being in the same pod in kubernetes.

Why is this needed?

I tried to convert https://github.com/dehydr8/elevation-of-privilege/blob/master/docker-compose.yml to Kubernetes, but the resulting manifest can't be used as is, because the two containers are set up so the client one, working as reverse proxy for server, references the server at three fixed addresses ws://localhost:8000, http://locahost:8001 and http://localhost:8002 and if they are started in separate pods, they can't.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions