-
Enhancement
-
Resolution: Duplicate
-
Blocker
-
None
-
EAP-XP-5.0.0.GA
-
None
-
False
-
None
-
False
-
-
Generally speaking we need entry points for customers to understand the product and HOW-TO use it; this Jira would fall into the second category;
In the relevant XP documentation we would like to have a paragraph at the beginning that states what's the default way to provision XP5 applications on OpenShift; we are not sure there's even a recommended way but if any, that's worth mentioning too...
The paragraph could also quickly describe the process (e.g. the maven plugin assembles a bootable jar / exploded server, the build happens locally / in the builder image, helm charts role if any, the builder image is used for this purpose, etc...);
The kind of information to put there are like:
- is using HELM Charts (https://github.com/jbossas/eap-charts/blob/eap-xp5-dev/charts/eap-xp5) the default?
- is using wildfly-jar-maven-plugin + binary build the default?
- are both the builder and runtime images involved in the process? (e.g. when using bootable jar, we are not using any runtime image)