kompose fails to convert cpu resources from a second (override) docker-compose yaml file

[mikegerber]

I am using a second Compose YAML to override e.g. the image in docker-compose.yml. This works as intended, however, kompose fails to include cpu resources I specify in the second YAML:

% kompose convert --stdout -f docker-compose.yml -f tmp-docker-compose-deploy.yml | grep cpu
%

If I merge the two YAML files manually, kompose includes the cpu resources:

% kompose convert --stdout -f docker-compose-manually-merged.yml | grep cpu
              cpu: "1"
              cpu: "1"
%

YAML files (.zip)

[mikegerber]

To reproduce, use the YAMLs in the .zip, and also create an empty docker.env:

touch docker.env

[mikegerber]

% kompose version
1.17.0 (a74acad)

[mikegerber]

Also fails with current HEAD:

% kompose version
1.17.0 (66ac4af)

[mikegerber]

Same for:

deploy:
  replicas: 2

Tested with kompose 1.18.0 this time.

[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

[mikegerber]

/remove-lifecycle stale

[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

[mikegerber]

Of course this bug report stale because there was no bug fix (or no visible bug fix). I am not going to instruct the bot to remove the label again.