-
Bug
-
Resolution: Obsolete
-
Blocker
-
None
-
7.3.0.CD18
-
None
Found in docs-bulk-88, revision 61d93d6.
Book: Getting Started with JBoss EAP for OpenShift Container Platform
Chapter: 1.5. Technology Preview Features
The last paragraph says that "For JDK 11 image streams, the application template is eap73-openjdk11-tx-recovery-s2i.". That is a reference to a template from a different image stream. The reference would make sense in 7.3 documentation, where there are two image streams - one JDK8, one JDK11. But the CD stream is only composed of one JDK, and that is currently JDK11. The sentence can be dropped, as the template eap-cd-tx-recovery-s2i is JDK11 based.
Chapter: 4. Migrating to JBoss EAP CD for OpenShift JDK 11 Image
I think this chapter should not be in the CD documentation at all. It is all about a different image stream. All the templates come from eap73-openjdk11-ubi8 and not from eap-cd template branch.
Chapter: 6.1.2. Deployment
This lists two examples: one that references eap-cd template and claims to be JDK8, the other that references eap73 template and claims to be JDK11. The eap-cd-* is actually JDK11 and the second can be dropped as it references a non-CD stream.
Chapter: 7.9.1. Configuring External Red Hat AMQ Brokers
Similar to above, this showcases two examples. The eap-cd example is correct and JDK11, the second can be dropped.
Book: Getting Started with JBoss EAP for OpenShift Online
All of these issues are also in the OpenShift Online book, at the same places. Please note that it might be better to resolve JBEAP-16842 prior to resolving anything for OpenShift Online book.