support multiple containers in a pod#1394
support multiple containers in a pod#1394hangyan merged 4 commits intokubernetes:masterfrom tk42:master
Conversation
|
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
Welcome @tk42! |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: tk42 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/check-cla |
|
/help |
|
@tk42 You can follow the links and sign the CLA |
|
@hangyan P.S. I overlooked an email from HelloSign service. |
|
/check-cla |
|
cla seems works now |
|
@tk42 This looks great, i'm reviewing this when i'm free. You may need to update related docs about this change(https://github.com/kubernetes/kompose/blob/master/docs/user-guide.md, the |
|
Looks all good! |
|
Thanks @tk42. This is great |
|
Thanks for the reviewing:bow: |
|
--multiple-container-mode option is not at the user user guide For me, it would be greate if the kompose.service.export could be used to setup multiples rules on the ingress config |
|
Yeah, will update the docs... |
|
@tk42 is it intended for |
The user guide contains a list of labels which can be used to change the output of `kompose`. `kompose.service.group` is listed as available label, however, it has no effect unless an additional `--multiple-container-mode` flag (which was mentioned in [original PR][1]) is passed. [1]: kubernetes#1394
As is mentioned in #1012,
kompose convertcreates each service as its own pod with single container.--multiple-container-modeenables creating multiple containers in a pod. This function is experimental.In case that such many changes might destroy the behavior known as before, so a temporary argument
--multiple-container-modeswitches its behavior. If the argument wasn't specified, kompose converts your docker-compose.yml along with keeping the behavior before. If no problems are reported after released as stable, this development mode is better to be merged for readable codes.How it works
In your docker-compose.yml, add
kompose.service.group={identifier grouped by pods}inlabelsto specify the containers in the same pod.add
--multiple-container-modeoption inkompose convertthen, you'll get a yaml for deployment as follows