Open iocanel opened 2 years ago
When performing a build using:
mvn clean package -Dquarkus.kubernetes.deploy=true -Dquarkus.kubernetes.deployment-target=openshift -Dqarkus.container-image.builder=docker
A push should be performed automatically, in the same spirit that it does when using kubernetes as a deployment target.
Push should be automatically triggered.
Push is not triggered automatically for DeploymentConfig it only happens for Deployment.
DeploymentConfig
Deployment
No response
uname -a
ver
java -version
mvnw --version
gradlew --version
/cc @geoand
So if I understand correctly, this should not apply for the s2i flow, right?
Is this still relevant?
@iocanel ^
Need to check but I think it's still relevant
Describe the bug
When performing a build using:
A push should be performed automatically, in the same spirit that it does when using kubernetes as a deployment target.
Expected behavior
Push should be automatically triggered.
Actual behavior
Push is not triggered automatically for
DeploymentConfig
it only happens forDeployment
.How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response