-
Notifications
You must be signed in to change notification settings - Fork 523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenShift switchToDeployment flag #630
Comments
|
+ Added documentation for `jkube.build.switchToDeployment` flag
Both configurations should be independent of each other. This means that if I state The |
If I refactor DefaultControllerEnricher to remove switchToDeployment specific code, I'm still not able to see Deployment being generated. Looks like DeploymentConfigEnricher forcibly converts Deployment to DeploymentConfig on platform mode OpenShift. I'm not sure how one enricher can check how other enricher is configured(without checking property value). However, if I manually disable DeploymentConfig enricher like this. I'm able to see Deployment getting generated with <configuration>
<enricher>
<excludes>
<exclude>jkube-openshift-deploymentconfig</exclude>
</excludes>
</enricher>
</configuration> |
Description
Document the usage of the flag
jkube.build.switchToDeployment
See why
<jkube.enricher.jkube-controller.type>Deployment</jkube.enricher.jkube-controller.type>
is not working as expected with OpenShift Maven Plugin.See how these flags interact
The text was updated successfully, but these errors were encountered: