UPDATE: This should be labeled an enhancement, not sure why it is not (user error?).
When using remote development, sometimes I make application.properties Kubernetes config changes that would normally generate updated YAML on a rebuild (Adding ConfigMap configuration dependency, adding/modifying liveness/readiness probes, etc). This means the developer either has to redeploy the application or manually apply the updated deployment yaml (target/kubernetes/*.yml) for the pod to restart with deployment changes applied.
It would be nice to have a flag for Quarkus to generate and auto-apply the updated YAML and automatically restart the pod when relevant quarrkus.kubernetes.* properties are modified. The remote-dev client tries to auto-reconnect anyway. Example: quarkus.live-reload.restart-pod-on-update=true The flag would be "false" by default. A better property name would be nice :-)
UPDATE: This should be labeled an enhancement, not sure why it is not (user error?).
When using remote development, sometimes I make application.properties Kubernetes config changes that would normally generate updated YAML on a rebuild (Adding ConfigMap configuration dependency, adding/modifying liveness/readiness probes, etc). This means the developer either has to redeploy the application or manually apply the updated deployment yaml (target/kubernetes/*.yml) for the pod to restart with deployment changes applied.
It would be nice to have a flag for Quarkus to generate and auto-apply the updated YAML and automatically restart the pod when relevant quarrkus.kubernetes.* properties are modified. The remote-dev client tries to auto-reconnect anyway. Example:
quarkus.live-reload.restart-pod-on-update=trueThe flag would be "false" by default. A better property name would be nice :-)https://github.com/quarkusio/quarkus/issues/11379
$upstream:11379$