Describe the bug
Using the quarkus-container-image-docker and quarkus-kubernetes extensions for deployment to Openshift.
The first deployment with mvn package -Dquarkus.kubernetes.deploy=true works fine.
The second deployment with the same maven call causes two deployments in Openshift.
One is triggered by the changed image-stream, the second is triggered with den new applied deployment-config.
Openshift shows a deployment-counter in the web-console.
The DeploymentConfig in the generated openshift.yml file has a trigger which causes this wrong behavior.
To fix this issue the trigger should not be generated by the kubernetes extension.
Expected behavior
Redeployment causes only one deployment action in openshift.
Actual behavior
Redeployment causes two deployment actions in openshift.
To Reproduce
Steps to reproduce the behavior:
Bootstrap a quarkus project with container-image-docker and kubernetes extension.
Set property quarkus.kubernetes.deployment-target=openshift
Login via oc tool to openshift
Login into docker-registry
Start first deployment with mvn package -Dquarkus.kubernetes.deploy=true
Start second deployment with mvn package -Dquarkus.kubernetes.deploy=true
Look into Openshift webconsole and see double deployments.
Environment (please complete the following information):
Output of uname -a or ver: Microsoft Windows [Version 10.0.17134.1610]
Output of java -version: openjdk version "11.0.6"
Quarkus version or git rev: 999-SNAPSHOT of today (2020-07-21)
Build tool (ie. output of mvnw --version or gradlew --version): Apache Maven 3.6.3
Describe the bug Using the quarkus-container-image-docker and quarkus-kubernetes extensions for deployment to Openshift. The first deployment with
mvn package -Dquarkus.kubernetes.deploy=trueworks fine. The second deployment with the same maven call causes two deployments in Openshift. One is triggered by the changed image-stream, the second is triggered with den new applied deployment-config. Openshift shows a deployment-counter in the web-console.The DeploymentConfig in the generated openshift.yml file has a trigger which causes this wrong behavior. To fix this issue the trigger should not be generated by the kubernetes extension.
Expected behavior Redeployment causes only one deployment action in openshift.
Actual behavior Redeployment causes two deployment actions in openshift.
To Reproduce Steps to reproduce the behavior:
quarkus.kubernetes.deployment-target=openshiftmvn package -Dquarkus.kubernetes.deploy=truemvn package -Dquarkus.kubernetes.deploy=trueEnvironment (please complete the following information):
uname -aorver: Microsoft Windows [Version 10.0.17134.1610]java -version: openjdk version "11.0.6"mvnw --versionorgradlew --version): Apache Maven 3.6.3https://github.com/quarkusio/quarkus/issues/10875
$upstream:10875$