Enable kompose to generate configs per docker-compose service

[surajssd]

Right now we create configs of entire docker-compose file.

Consider the following docker-compose file with only one service:

services:
  one:
  ...

Now a user is using this for sometime, but after sometime she adds one more service and docker-compose file looks like this:

services:
  one:
  ...
  two:
  ...

Now what user wants is that only artifacts of service two to be created. How can we enable that to happen? I propose that we add a flag named service which creates config only for particular docker-compose service.

kompose convert --service two
kompose up --service two

[surajnarwade]

I will take this up

[cdrage]

@surajnarwade Please don't take this up yet, we need to discuss the scope of this functionality before any sort of implementation.

@surajssd This doesn't really make sense. If someone we're to add another service, it's as simple as adding the service to docker-compose.yaml converting, and then using kubectl apply, no? Kubernetes would automatically figure out what needs to be added and/or updated.

[surajnarwade]

@cdrage okay :)

[surajssd]

@cdrage yeah people can use kubectl apply but this was more on the lines of UX, not everyone knows about the kubectl apply recipe of using kompose, if we are not adding this feature please consider documenting it.

[fejta-bot]

Issues go stale after 90d 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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten
/remove-lifecycle stale

[surajnarwade]

/remove-lifecycle rotten

[fejta-bot]

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

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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten
/remove-lifecycle stale