Skip to content

quarkus.kubernetes-client.devservices.manifests does not work well with multiple dev services #49381

@LarsSven

Description

@LarsSven

Describe the bug

When using quarkus.kubernetes-client.devservices.manifests on an application that connects to an existing Kubernetes dev service, it produces: Cannot apply manifests because the Kubernetes dev service is not running

Expected behavior

The most sensible behaviour for this property is to apply its manifests even if the dev service was already started by another microservice

Actual behavior

Manifests are not applied if the dev service is already running

How to Reproduce?

  1. Start an application in dev mode that has a Kubernetes dev service
  2. Start another application in dev mode that also has a Kubernetes dev service and is instructed to apply a set of manifests
  3. Observe the failure in the second application

Output of uname -a or ver

Ubuntu 25.04

Output of java -version

OpenJDK 21.0.8

Quarkus version or git rev

3.25.0

Build tool (ie. output of mvnw --version or gradlew --version)

Gradle 8.14.3

Additional information

I contributed this feature myself so I will probably be the one fixing this, I'm opening this issue to track it and for discussion

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions