[BUG] memory resources (limits / requests) not well readable

[marcoklaassen]

Expected Behavior

Given:

services:
  frontend:
    image: example/webapp
    deploy:
      resources:
        limits:
          cpus: '0.50'
          memory: 50M
          pids: 1
        reservations:
          cpus: '0.25'
          memory: 20M

when I execute kompose -f docker-compose.yaml convert

I would like to have the memory better readable (e.g. 20Mi / 50Mi).

Actual Behavior

currently I get it like this:

[...]
spec:
      containers:
        - image: example/webapp
          name: frontend
          resources:
            limits:
              cpu: 500m
              memory: "52428800"
            requests:
              cpu: 250m
              memory: "20971520"
[...]

Steps To Reproduce

kompose -f docker-compose.yaml convert

Kompose Version

1.37.0 (HEAD)

Docker-Compose file

services:
  frontend:
    image: example/webapp
    deploy:
      resources:
        limits:
          cpus: '0.50'
          memory: 50M
          pids: 1
        reservations:
          cpus: '0.25'
          memory: 20M

Anything else?

No response

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale