The typical approach for Kubernetes is to fail fast. If there is Kubernetes service binding plugin used proper behavior would
be to look for the values and if they are not present fail application fast.
This way application can stop etc. Currently app will try to connect to localhost (which is due to values being undefined).
My take is that I would love this to be consistent with behaviour without service binding plugin present (without kafka.* properties/profile/env app will fail to start)
(Note this is improvement and not blocking anything right now)
Describe the bug
The typical approach for Kubernetes is to fail fast. If there is Kubernetes service binding plugin used proper behavior would be to look for the values and if they are not present fail application fast.
This way application can stop etc. Currently app will try to connect to localhost (which is due to values being undefined). My take is that I would love this to be consistent with behaviour without service binding plugin present (without kafka.* properties/profile/env app will fail to start)
(Note this is improvement and not blocking anything right now)
https://github.com/quarkusio/quarkus/issues/16682
$upstream:16682$