Missing service metadata.labels mapping

[sesigl]

Hi,

first, I really like the project, thank you very much!

I am not able to map compose values to service's metadata.labels.

example:

version: "3"
services:
  selenium-hub:
    image: selenium/hub:3.12.0-americium
    container_name: selenium-hub
    ports:
      - "4444:4444"
    deploy:
      resources:
        limits:
          cpus: '0.5'
          memory: 500M
        reservations:
          cpus: '0.5'
          memory: 500M
    labels:
      service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0
      kompose.service.type: LoadBalancer

The result is:

apiVersion: v1
kind: Service
metadata:
  annotations:
    kompose.cmd: kompose convert
    kompose.service.type: LoadBalancer
    kompose.version: 1.4.0 (c7964e7)
    service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0
  creationTimestamp: null
  labels:
    io.kompose.service: selenium-hub
  name: selenium-hub
spec:
  ports:
  - name: "4444"
    port: 4444
    targetPort: 4444
  selector:
    io.kompose.service: selenium-hub
  type: LoadBalancer
status:
  loadBalancer: {}

What I need is the following:

apiVersion: v1
kind: Service
metadata:
  annotations:
    kompose.cmd: kompose convert
    kompose.service.type: LoadBalancer
    kompose.version: 1.4.0 (c7964e7)
    service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0
  creationTimestamp: null
  labels:
    io.kompose.service: selenium-hub
    dns: route53   <--- this field is missing
  name: selenium-hub
spec:
  ports:
  - name: "4444"
    port: 4444
    targetPort: 4444
  selector:
    io.kompose.service: selenium-hub
  type: LoadBalancer
status:
  loadBalancer: {}

Maybe I missed something but I couldn't find any hint in the conversion matrix. I need to find a way to make Kompose creating the dns: route53 label.

Any ideas how to achieve this?

[hangyan]

@Journerist May I ask where is this dns:route53 come from? Did't find it in the compose file

[sesigl]

@hangyan This is the question :) Where to add it ? I tried adding this one to labels, but labels are mapped to metadata.annotations.

[hangyan]

@Journerist I think currently there is no way to support this. But this is a reasonable request, we should figure out a way to support it. @cdrage

[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

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions 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.