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

determine which containers should be in the same pod #14

Closed
ngtuna opened this issue Jul 6, 2016 · 10 comments
Closed

determine which containers should be in the same pod #14

ngtuna opened this issue Jul 6, 2016 · 10 comments
Assignees
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P1

Comments

@ngtuna
Copy link
Contributor

ngtuna commented Jul 6, 2016

e.g., the ones share the same volume should be in the same pod; the ones link to each other may or may not be in the same pod

@ngtuna
Copy link
Contributor Author

ngtuna commented Jul 18, 2016

@surajssd
Copy link
Member

Will be working on this one!

@ngtuna
Copy link
Contributor Author

ngtuna commented Aug 24, 2016

@surajssd feel free to update priority/P1 label if you are working on it now. That would be great to have it implemented in the next release.

@surajssd
Copy link
Member

#131 right now only addresses volumes_from directive!

@ngtuna
Copy link
Contributor Author

ngtuna commented Oct 26, 2016

Should we close this ?

@surajssd
Copy link
Member

@ngtuna we have not implemented it yet so lets keep it.

@kadel
Copy link
Member

kadel commented Oct 30, 2016

Do we know about another case which would resolve in putting two containers to the same pod?

@fejta-bot
Copy link

Issues go stale after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2017
@surajssd
Copy link
Member

we should not do anything that deviates from the base docker-compose file format so let's not do this one!

@cdrage
Copy link
Member

cdrage commented Dec 20, 2017

@surajssd agreed, let's close

@cdrage cdrage closed this as completed Dec 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P1
Projects
None yet
Development

No branches or pull requests

6 participants