Support profiling for quarkus-kubernetes extension .yml/.json file path

[umutsahin]

Description

Hi,

Even though the kubernetes extension is flexible there maybe some cases, lets say we need to add properties that extension doesn't support like pod affinity, anti affinity or topology spreads. Right now I am adding these to kubernetes.yml file with empty deployment, as we are using kind deployment, but this is not open and supporting build profiles that quarkus has.

I am not asking to add these to kubernetes extension, but if we can get the configuration entry for kubernetes.yml/json file path, we can have multiple profiles and switch based on our needs.

Thanks!

Implementation ideas

No response

[quarkus-bot[bot]]

/cc @geoand (kubernetes), @iocanel (kubernetes)