Make the Operator Wildfly based but also EAP based #148
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Depends on #159
What needs to be changed in the Operator
Due to windup/windup-openshift#49 Windup can not be based on Wildfly and EAP. The mounting volume points to
/opt/wildfly/standalone/data
or/opt/eap/standalone/data
hence the volume path needs to be defined through the operator.How to create container images of the operator
Checkout this PR and execute:
For creating the operator based on Wildfly:
For creating the operator based on EAP:
Push your images:
Observe that for creating the EAP based container image we are passing a BuildTime property
-Dapp-base-server=eap
Deploy the Operator in Minikube
src/main/resources/k8s/def/windup.deployment.yaml
and change the line20
to point to your image:src/test/resources/windup-test.yaml
and replace it its content by:Minikube dashboard
You can see the deployments and pods executing: