search

quarkusio / quarkus

Quarkus: Supersonic Subatomic Java.
https://quarkus.io
Apache License 2.0
13.39k stars 2.56k forks source link

Introduce zero-config solution for OpenShift Serverless #11633

Open rsvoboda opened 3 years ago

rsvoboda commented 3 years ago

Introduce zero-config solution for OpenShift Serverless is follow-up action coming from https://github.com/quarkusio/quarkus/issues/11442#issuecomment-678961995

To use OpenShift Serverless users need to add few properties, users shouldn't have to do that themselves.

We probably could distinguish regular Knative and OpenShift Serverless (either via an extension, e.g. quarkus-openshift-serverless, or via deployment target, e.g. quarkus.kubernetes.deployment-target=openshift-serverless).

I'm slightly more in favor of quarkus.kubernetes.deployment-target=openshift-serverless way instead of introducing another extension but there can be some drawbacks I'm not aware of.

@tqvarnst / @geoand I created this enhancement request because https://github.com/quarkusio/quarkus/issues/11442 was closed as OpenShift Serverless documentation section was added to help users.

quarkusbot commented 3 years ago

/cc @geoand

geoand commented 3 years ago

Thanks for creating a dedicated ticket @rsvoboda

geoand commented 3 years ago

cc @iocanel who is working on something as we speak

maxandersen commented 3 years ago

@rsvoboda @geoand @iocanel this was discussed today but i'm not following what this issue is actually about ? like specifically what settings are considered surplus?

rsvoboda commented 3 years ago

Hi @maxandersen, atm users need to define following properties when using OpenShift Serverless:

quarkus.kubernetes.deployment-target=knative
quarkus.container-image.registry=image-registry.openshift-image-registry.svc:5000

With vanilla OpenShift users just define quarkus.kubernetes.deployment-target=openshift. So there is slight difference in user experience for OpenShift vs OpenShift Serverless.

I hope I didn't miss anything, it's few months since the issue was filed. There is additional context in https://github.com/quarkusio/quarkus/issues/11442.

inoxx03 commented 3 years ago

@maxandersen This change is tracked under QUARKUS-374 in the downstream.