Fights service when deployed to k8s doesn't get random fighters about quarkus-super-heroes HOT 8 CLOSED

Since quarkusio/quarkus@b89fece#diff-f15233cea0f87118b4441038738a41197a55fb6e3e1f3e06efd1dc4b41fe0143R160, the Kubernetes services created by Quarkus now contain two ports:

• HTTP (8080)
• HTTPS (8443)

The problem with the two ports is that our application exposes a single one, so the second one will constantly fail.

When Stork lists the endpoint ports, it finds the two ports and does not know which one to use. So, it picks the first one, which has 50% of selecting the wrong one.

@Sgitario added a feature to Stork that allows selecting the port. However, having a new, almost mandatory attribute for something that should not be is inconvenient. But that's a workaround until we can improve the generation.

\CC @Sgitario @iocanel

from quarkus-super-heroes.

With quarkusio/quarkus#33237, you would need to set port-name: http for the clients using stork.

from quarkus-super-heroes.

I did try that but still did not work.

from quarkus-super-heroes.

from quarkus-super-heroes.

I tried quarkusio/quarkus#33237 with quarkusio/quarkus#33131 and the new property works fine: quarkusio/quarkus#33131 (comment)

from quarkus-super-heroes.

I haven't tried it yet. How would I do that? Build Quarkus main and then build super heroes off of that?

from quarkus-super-heroes.

@edeandrea no need for the full quarkus. Just use Stork 2.2.0 (set the dependency version on the kubernetes service discovery dependency).

The PR bumping the Stork version in Quarkus has been opened. I hope it will be merged and include for the next release (cut today if I'm not mistaken).

from quarkus-super-heroes.

The fix has been integrated in the latest Quarkus release:
https://github.com/quarkusio/quarkus/releases/tag/3.0.3.Final

from quarkus-super-heroes.