Prioritize service instead of devspace UI when using port 8090

What happened?
Port forwarding a service on 8090 using devspace dev serves the UI instead of the service.

What did you expect to happen instead?
The service should take priority and the UI should run on the next available port.

How can we reproduce the bug? (as minimally and precisely as possible)
Run devspace dev with the following devspace.yaml:

version: v2beta1
name: whoami
deployments:
  api:
    helm:
      chart:
        name: component-chart
        repo: https://charts.devspace.sh
      values:
        containers:
          - image: traefik/whoami
            env:
              - name: WHOAMI_PORT_NUMBER
                value: "8090"
        service:
          ports:
            - port: 8090
dev:
  api:
    imageSelector: traefik/whoami
    ports:
      - port: "8090"

Local Environment:

DevSpace Version: 6.3.17
Operating System: mac
ARCH of the OS: ARM64

Kubernetes Cluster:

Cloud Provider: docker desktop
Kubernetes Version: client: v1.33.3, server: v1.32.2

Hello!

You can re-map the local port to avoid the conflict:

...
dev:
  api:
    imageSelector: traefik/whoami
    ports:
      - port: "8091:8090"

Hope that helps!

I can change the port it's exposed on, but it'd be nice to be able to use any port (a number of our services use 8090, and it'd be good if it used the same port when running inside and outside of Kubernetes).

Navigation Menu

Repository navigation

Prioritize service instead of devspace UI when using port 8090 #3000

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Prioritize service instead of devspace UI when using port 8090 #3000

Description

Activity

lizardruss commented on Sep 4, 2025

jackwilsdon commented on Sep 5, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions