├── .gitignore ├── LICENSE ├── README.adoc.in ├── README.md ├── amq-ssl.adoc.in ├── amq ├── amq62-image-stream.json ├── amq63-basic.json ├── amq63-image-stream.json ├── amq63-persistent-ssl.json ├── amq63-persistent.json └── amq63-ssl.json ├── datagrid.adoc.in ├── datagrid ├── datagrid71-basic.json ├── datagrid71-https.json ├── datagrid71-image-stream.json ├── datagrid71-mysql-persistent.json ├── datagrid71-mysql.json ├── datagrid71-partition.json ├── datagrid71-postgresql-persistent.json └── datagrid71-postgresql.json ├── docs ├── README.adoc ├── amq │ ├── amq63-basic.adoc │ ├── amq63-persistent-ssl.adoc │ ├── amq63-persistent.adoc │ └── amq63-ssl.adoc ├── datagrid │ ├── datagrid71-basic.adoc │ ├── datagrid71-https.adoc │ ├── datagrid71-mysql-persistent.adoc │ ├── datagrid71-mysql.adoc │ ├── datagrid71-partition.adoc │ ├── datagrid71-postgresql-persistent.adoc │ └── datagrid71-postgresql.adoc ├── eap │ ├── eap64-amq-persistent-s2i.adoc │ ├── eap64-amq-s2i.adoc │ ├── eap64-basic-s2i.adoc │ ├── eap64-https-s2i.adoc │ ├── eap64-mongodb-persistent-s2i.adoc │ ├── eap64-mongodb-s2i.adoc │ ├── eap64-mysql-persistent-s2i.adoc │ ├── eap64-mysql-s2i.adoc │ ├── eap64-postgresql-persistent-s2i.adoc │ ├── eap64-postgresql-s2i.adoc │ ├── eap64-sso-s2i.adoc │ ├── eap64-third-party-db-s2i.adoc │ ├── eap64-tx-recovery-s2i.adoc │ ├── eap71-amq-persistent-s2i.adoc │ ├── eap71-amq-s2i.adoc │ ├── eap71-basic-s2i.adoc │ ├── eap71-https-s2i.adoc │ ├── eap71-mongodb-persistent-s2i.adoc │ ├── eap71-mongodb-s2i.adoc │ ├── eap71-mysql-persistent-s2i.adoc │ ├── eap71-mysql-s2i.adoc │ ├── eap71-postgresql-persistent-s2i.adoc │ ├── eap71-postgresql-s2i.adoc │ ├── eap71-sso-s2i.adoc │ ├── eap71-third-party-db-s2i.adoc │ └── eap71-tx-recovery-s2i.adoc ├── openjdk │ └── openjdk18-web-basic-s2i.adoc ├── secrets │ ├── amq-app-secret.adoc │ ├── datagrid-app-secret.adoc │ ├── datavirt-app-secret.adoc │ ├── eap-app-secret.adoc │ ├── eap7-app-secret.adoc │ ├── jws-app-secret.adoc │ └── sso-app-secret.adoc ├── sso │ └── README.md └── webserver │ ├── jws31-tomcat7-basic-s2i.adoc │ ├── jws31-tomcat7-https-s2i.adoc │ ├── jws31-tomcat7-mongodb-persistent-s2i.adoc │ ├── jws31-tomcat7-mongodb-s2i.adoc │ ├── jws31-tomcat7-mysql-persistent-s2i.adoc │ ├── jws31-tomcat7-mysql-s2i.adoc │ ├── jws31-tomcat7-postgresql-persistent-s2i.adoc │ ├── jws31-tomcat7-postgresql-s2i.adoc │ ├── jws31-tomcat8-basic-s2i.adoc │ ├── jws31-tomcat8-https-s2i.adoc │ ├── jws31-tomcat8-mongodb-persistent-s2i.adoc │ ├── jws31-tomcat8-mongodb-s2i.adoc │ ├── jws31-tomcat8-mysql-persistent-s2i.adoc │ ├── jws31-tomcat8-mysql-s2i.adoc │ ├── jws31-tomcat8-postgresql-persistent-s2i.adoc │ └── jws31-tomcat8-postgresql-s2i.adoc ├── eap ├── README_SSO.adoc ├── eap64-amq-persistent-s2i.json ├── eap64-amq-s2i.json ├── eap64-basic-s2i.json ├── eap64-https-s2i.json ├── eap64-image-stream.json ├── eap64-mongodb-persistent-s2i.json ├── eap64-mongodb-s2i.json ├── eap64-mysql-persistent-s2i.json ├── eap64-mysql-s2i.json ├── eap64-postgresql-persistent-s2i.json ├── eap64-postgresql-s2i.json ├── eap64-sso-s2i.json ├── eap64-third-party-db-s2i.json ├── eap64-tx-recovery-postgresql-s2i.json ├── eap64-tx-recovery-s2i.json ├── eap70-image-stream.json ├── eap71-amq-persistent-s2i.json ├── eap71-amq-s2i.json ├── eap71-basic-s2i.json ├── eap71-https-s2i.json ├── eap71-image-stream.json ├── eap71-mongodb-persistent-s2i.json ├── eap71-mongodb-s2i.json ├── eap71-mysql-persistent-s2i.json ├── eap71-mysql-s2i.json ├── eap71-postgresql-persistent-s2i.json ├── eap71-postgresql-s2i.json ├── eap71-sso-s2i.json ├── eap71-third-party-db-s2i.json └── eap71-tx-recovery-s2i.json ├── gen_template_docs.py ├── openjdk └── README.md ├── release-notes.adoc.in ├── secrets ├── amq-app-secret.json ├── datagrid-app-secret.json ├── datavirt-app-secret.yaml ├── eap-app-secret.json ├── eap7-app-secret.json ├── jws-app-secret.json └── sso-app-secret.json ├── sso └── README.md ├── template.adoc.in └── webserver ├── jws30-tomcat7-image-stream.json ├── jws30-tomcat8-image-stream.json ├── jws31-tomcat7-basic-s2i.json ├── jws31-tomcat7-https-s2i.json ├── jws31-tomcat7-image-stream.json ├── jws31-tomcat7-mongodb-persistent-s2i.json ├── jws31-tomcat7-mongodb-s2i.json ├── jws31-tomcat7-mysql-persistent-s2i.json ├── jws31-tomcat7-mysql-s2i.json ├── jws31-tomcat7-postgresql-persistent-s2i.json ├── jws31-tomcat7-postgresql-s2i.json ├── jws31-tomcat8-basic-s2i.json ├── jws31-tomcat8-https-s2i.json ├── jws31-tomcat8-image-stream.json ├── jws31-tomcat8-mongodb-persistent-s2i.json ├── jws31-tomcat8-mongodb-s2i.json ├── jws31-tomcat8-mysql-persistent-s2i.json ├── jws31-tomcat8-mysql-s2i.json ├── jws31-tomcat8-postgresql-persistent-s2i.json └── jws31-tomcat8-postgresql-s2i.json /.gitignore: -------------------------------------------------------------------------------- 1 | /.project 2 | .idea/ 3 | *.iml 4 | -------------------------------------------------------------------------------- /README.adoc.in: -------------------------------------------------------------------------------- 1 | = Application Templates 2 | 3 | This project contains OpenShift v3 application templates which support applications based on JBoss Middleware products. 4 | Source can be found https://github.com/jboss-openshift/application-templates/tree/master[here]. 5 | 6 | :icons: font 7 | :toc: macro 8 | 9 | toc::[levels=1] 10 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Application Templates 2 | This project contains OpenShift v3 application templates which support 3 | applications based on JBoss Middleware products. 4 | 5 | ## Structure 6 | The templates in this folder are organized by JBoss Middleware product. Each 7 | template is configured with the following basic parameters: 8 | * APPLICATION_NAME: the name of the application. This is also used as the 9 | name of the docker image created by the build. 10 | * SOURCE_REPOSITORY_URL: the URI to the git project used for S2I templates. 11 | * SOURCE_REPOSITORY_REF: the git reference to use when pulling the project. 12 | * CONTEXT_DIR: the relative directory within the project to build (if other than the root directory) 13 | * APPLICATION_DOMAIN: the hostname to register for the route (for templates 14 | exposing services publicly, through the router). If unset, the default, the hostnames will be of the form: `..`, e.g. eap-app.myproject.v3.openshift.com 15 | 16 | In addition to these basic parameters, templates utilizing databases will have 17 | the following: 18 | * DB_USER: The name of the database user. 19 | * DB_PASSWORD: The password for the database user. 20 | * DB_DATABASE: The database/tablespace to connect to. 21 | * DB_JNDI: The JNDI name to use for datasource definitions (e.g. eap: java:jdbc/mydb or jws: jdbc/mydb) 22 | 23 | ## Common Image Repositories 24 | The `jboss-image-streams.json` file contains __ImageStream__ definitions for all 25 | JBoss Middleware products. This will need to be 26 | installed in the common `openshift` namespace (`oc create -f jboss-images-streams.json -n openshift`) before using any of the templates in these folders. You will also need to install (into the `openshift` namespace) the database image streams supplied by OpenShift to use any of the templates that integrate with MySQL, PostgreSQL or MongoDB. 27 | 28 | ## HTTPS configuration 29 | The majority of templates contain configuration that requires the creation of resources within your project to support HTTPS, specifically a service account and a secret that can be included into the pod as a volume. The secrets directory contains a number of examples that can be installed into your project to allow you to test the A-MQ, EAP and JWS templates, you should replace the contents of these with data that is more appropriate for your deployments. 30 | 31 | To install the service accounts and secrets into your project: 32 | ``` 33 | $ oc create -n myproject -f secrets 34 | ``` 35 | 36 | The following templates can be used without creating a service account or a secret: eap/eap64-basic-s2i.json, webserver/jws31-tomcat7-basic-s2i.json and webserver/jws31-tomcat8-basic-s2i.json. 37 | 38 | ## Example 39 | The easiest way to use the templates is to install them in your project, then use the _Create+_ button in the OpenShift console to create your application. The console will prompt you for the values for all of the parameters used by the template. To set this up for a particular template: 40 | ``` 41 | $ oc create -n openshift -f jboss-image-streams.json 42 | $ oc create -n myproject -f webserver/jws31-tomcat7-basic-s2i.json 43 | ``` 44 | After executing the above, you should be able to see the template after pressing _Create+_ in your project. 45 | 46 | Or, if you prefer the command line: 47 | ``` 48 | $ oc create -n openshift -f jboss-image-streams.json 49 | $ oc process -n yourproject -f eap/eap64-basic-s2i.json -p APPLICATION_NAME=helloworld -p SOURCE_REPOSITORY_URL=https://github.com/jboss-developer/jboss-eap-quickstarts -p SOURCE_REPOSITORY_REF=6.4.x -p CONTEXT_DIR=helloworld | oc create -n yourproject -f - 50 | ``` 51 | 52 | You may also install the templates into the `openshift` namespace in order to make them 53 | available to all users: 54 | ``` 55 | $ oc create -n openshift -f amq -f eap -f webserver 56 | ``` 57 | -------------------------------------------------------------------------------- /amq-ssl.adoc.in: -------------------------------------------------------------------------------- 1 | For SSL to work, you have to have keystore and truststore files. If you don't have them already, you can generate them using _keytool_ application which is part of Java distribution. Assuming that JAVA_HOME points to your Java distribution, open a working directory and run the commands from the command line. 2 | 3 | 1. Prepare variables 4 | 5 | BROKER_KEYSTORE_PASSWORD= 6 | BROKER_TRUSTSTORE_PASSWORD= 7 | CLIENT_KEYSTORE_PASSWORD= 8 | 9 | 10 | 2. Create client keystore (optional - if you alredy have certificate for the client, proceed to step 4) 11 | 12 | $JAVA_HOME/bin/keytool \ 13 | -genkey \ 14 | -keyalg RSA \ 15 | -alias amq-client \ 16 | -keystore amq-client.ks \ 17 | -storepass $CLIENT_KEYSTORE_PASSWORD \ 18 | -keypass $CLIENT_KEYSTORE_PASSWORD 19 | 20 | 3. Create client certificate (optional - if you alredy have certificate for the client, proceed to step 4) 21 | 22 | $JAVA_HOME/bin/keytool \ 23 | -export \ 24 | -alias amq-client \ 25 | -keystore amq-client.ks \ 26 | -storepass $CLIENT_KEYSTORE_PASSWORD \ 27 | -file amq-client.cert 28 | 29 | 4. Create broker keystore 30 | 31 | $JAVA_HOME/bin/keytool \ 32 | -genkey \ 33 | -keyalg RSA \ 34 | -alias amq-broker \ 35 | -keystore amq-broker.ks \ 36 | -storepass $BROKER_KEYSTORE_PASSWORD \ 37 | -keypass $BROKER_KEYSTORE_PASSWORD 38 | 39 | 5. Create broker truststore from client certificate 40 | 41 | $JAVA_HOME/bin/keytool \ 42 | -import \ 43 | -alias amq-broker \ 44 | -keystore amq-broker.ts \ 45 | -file amq-client.cert \ 46 | -storepass $BROKER_TRUSTSTORE_PASSWORD \ 47 | -trustcacerts \ 48 | -noprompt 49 | 50 | Now, you can use files `amq-broker.ks` and `amq-broker.ts` in OpenShift secret definition. Leave the files `amq-client.ks` and `amq-client.cert` be as they are not needed by the broker. Also, when creating A-MQ application, set the template parameters as: + 51 | 52 | AMQ_KEYSTORE=amq-broker.ks + 53 | AMQ_KEYSTORE_PASSWORD= + 54 | AMQ_TRUSTSTORE=amq-broker.ts + 55 | AMQ_TRUSTSTORE_PASSWORD= + 56 | 57 | -------------------------------------------------------------------------------- /amq/amq62-image-stream.json: -------------------------------------------------------------------------------- 1 | { 2 | "kind": "List", 3 | "apiVersion": "v1", 4 | "metadata": { 5 | "name": "amq62-image-stream", 6 | "annotations": { 7 | "description": "ImageStream definition for Red Hat JBoss AMQ 6.2.", 8 | "openshift.io/provider-display-name": "Red Hat, Inc." 9 | } 10 | }, 11 | "items": [ 12 | { 13 | "kind": "ImageStream", 14 | "apiVersion": "v1", 15 | "metadata": { 16 | "name": "jboss-amq-62", 17 | "annotations": { 18 | "openshift.io/display-name": "Red Hat JBoss A-MQ 6.2", 19 | "openshift.io/provider-display-name": "Red Hat, Inc.", 20 | "version": "1.4.17" 21 | } 22 | }, 23 | "labels": { 24 | "xpaas": "1.4.17" 25 | }, 26 | "spec": { 27 | "tags": [ 28 | { 29 | "name": "1.1", 30 | "annotations": { 31 | "description": "JBoss A-MQ 6.2 broker image.", 32 | "iconClass": "icon-amq", 33 | "tags": "messaging,amq,jboss,hidden", 34 | "supports": "amq:6.2,messaging", 35 | "version": "1.1", 36 | "openshift.io/display-name": "Red Hat JBoss A-MQ 6.2" 37 | }, 38 | "referencePolicy": { 39 | "type": "Local" 40 | }, 41 | "from": { 42 | "kind": "DockerImage", 43 | "name": "registry.redhat.io/jboss-amq-6/amq62-openshift:1.1" 44 | } 45 | }, 46 | { 47 | "name": "1.2", 48 | "annotations": { 49 | "description": "JBoss A-MQ 6.2 broker image.", 50 | "iconClass": "icon-amq", 51 | "tags": "messaging,amq,jboss,hidden", 52 | "supports": "amq:6.2,messaging", 53 | "version": "1.2", 54 | "openshift.io/display-name": "Red Hat JBoss A-MQ 6.2" 55 | }, 56 | "referencePolicy": { 57 | "type": "Local" 58 | }, 59 | "from": { 60 | "kind": "DockerImage", 61 | "name": "registry.redhat.io/jboss-amq-6/amq62-openshift:1.2" 62 | } 63 | }, 64 | { 65 | "name": "1.3", 66 | "annotations": { 67 | "description": "JBoss A-MQ 6.2 broker image.", 68 | "iconClass": "icon-amq", 69 | "tags": "messaging,amq,jboss,hidden", 70 | "supports": "amq:6.2,messaging", 71 | "version": "1.3", 72 | "openshift.io/display-name": "Red Hat JBoss A-MQ 6.2" 73 | }, 74 | "referencePolicy": { 75 | "type": "Local" 76 | }, 77 | "from": { 78 | "kind": "DockerImage", 79 | "name": "registry.redhat.io/jboss-amq-6/amq62-openshift:1.3" 80 | } 81 | }, 82 | { 83 | "name": "1.4", 84 | "annotations": { 85 | "description": "JBoss A-MQ 6.2 broker image.", 86 | "iconClass": "icon-amq", 87 | "tags": "messaging,amq,jboss,hidden", 88 | "supports": "amq:6.2,messaging", 89 | "version": "1.4", 90 | "openshift.io/display-name": "Red Hat JBoss A-MQ 6.2" 91 | }, 92 | "referencePolicy": { 93 | "type": "Local" 94 | }, 95 | "from": { 96 | "kind": "DockerImage", 97 | "name": "registry.redhat.io/jboss-amq-6/amq62-openshift:1.4" 98 | } 99 | }, 100 | { 101 | "name": "1.5", 102 | "annotations": { 103 | "description": "JBoss A-MQ 6.2 broker image.", 104 | "iconClass": "icon-amq", 105 | "tags": "messaging,amq,jboss,hidden", 106 | "supports": "amq:6.2,messaging", 107 | "version": "1.5", 108 | "openshift.io/display-name": "Red Hat JBoss A-MQ 6.2" 109 | }, 110 | "referencePolicy": { 111 | "type": "Local" 112 | }, 113 | "from": { 114 | "kind": "DockerImage", 115 | "name": "registry.redhat.io/jboss-amq-6/amq62-openshift:1.5" 116 | } 117 | }, 118 | { 119 | "name": "1.6", 120 | "annotations": { 121 | "description": "JBoss A-MQ 6.2 broker image.", 122 | "iconClass": "icon-amq", 123 | "tags": "messaging,amq,jboss,hidden", 124 | "supports":"amq:6.2,messaging", 125 | "version": "1.6", 126 | "openshift.io/display-name": "Red Hat JBoss A-MQ 6.2" 127 | }, 128 | "referencePolicy": { 129 | "type": "Local" 130 | }, 131 | "from": { 132 | "kind": "DockerImage", 133 | "name": "registry.redhat.io/jboss-amq-6/amq62-openshift:1.6" 134 | } 135 | }, 136 | { 137 | "name": "1.7", 138 | "annotations": { 139 | "description": "JBoss A-MQ 6.2 broker image.", 140 | "iconClass": "icon-amq", 141 | "tags": "messaging,amq,jboss,hidden", 142 | "supports":"amq:6.2,messaging", 143 | "version": "1.7", 144 | "openshift.io/display-name": "Red Hat JBoss A-MQ 6.2" 145 | }, 146 | "referencePolicy": { 147 | "type": "Local" 148 | }, 149 | "from": { 150 | "kind": "DockerImage", 151 | "name": "registry.redhat.io/jboss-amq-6/amq62-openshift:1.7" 152 | } 153 | } 154 | ] 155 | } 156 | } 157 | ] 158 | } 159 | 160 | -------------------------------------------------------------------------------- /amq/amq63-image-stream.json: -------------------------------------------------------------------------------- 1 | { 2 | "kind": "List", 3 | "apiVersion": "v1", 4 | "metadata": { 5 | "name": "amq63-image-stream", 6 | "annotations": { 7 | "description": "ImageStream definition for Red Hat JBoss AMQ 6.3.", 8 | "openshift.io/provider-display-name": "Red Hat, Inc." 9 | } 10 | }, 11 | "items": [ 12 | { 13 | "kind": "ImageStream", 14 | "apiVersion": "v1", 15 | "metadata": { 16 | "name": "jboss-amq-63", 17 | "annotations": { 18 | "openshift.io/display-name": "Red Hat JBoss A-MQ 6.3", 19 | "openshift.io/provider-display-name": "Red Hat, Inc.", 20 | "version": "1.4.17" 21 | } 22 | }, 23 | "labels": { 24 | "xpaas": "1.4.17" 25 | }, 26 | "spec": { 27 | "tags": [ 28 | { 29 | "name": "1.0", 30 | "annotations": { 31 | "description": "JBoss A-MQ 6.3 broker image.", 32 | "iconClass": "icon-amq", 33 | "tags": "messaging,amq,jboss,hidden", 34 | "supports": "amq:6.3,messaging", 35 | "version": "1.0", 36 | "openshift.io/display-name": "Red Hat JBoss A-MQ 6.3" 37 | }, 38 | "referencePolicy": { 39 | "type": "Local" 40 | }, 41 | "from": { 42 | "kind": "DockerImage", 43 | "name": "registry.redhat.io/jboss-amq-6/amq63-openshift:1.0" 44 | } 45 | }, 46 | { 47 | "name": "1.1", 48 | "annotations": { 49 | "description": "JBoss A-MQ 6.3 broker image.", 50 | "iconClass": "icon-amq", 51 | "tags": "messaging,amq,jboss,hidden", 52 | "supports": "amq:6.3,messaging", 53 | "version": "1.1", 54 | "openshift.io/display-name": "Red Hat JBoss A-MQ 6.3" 55 | }, 56 | "referencePolicy": { 57 | "type": "Local" 58 | }, 59 | "from": { 60 | "kind": "DockerImage", 61 | "name": "registry.redhat.io/jboss-amq-6/amq63-openshift:1.1" 62 | } 63 | }, 64 | { 65 | "name": "1.2", 66 | "annotations": { 67 | "description": "JBoss A-MQ 6.3 broker image.", 68 | "iconClass": "icon-amq", 69 | "tags": "messaging,amq,jboss,hidden", 70 | "supports": "amq:6.3,messaging", 71 | "version": "1.2", 72 | "openshift.io/display-name": "Red Hat JBoss A-MQ 6.3" 73 | }, 74 | "referencePolicy": { 75 | "type": "Local" 76 | }, 77 | "from": { 78 | "kind": "DockerImage", 79 | "name": "registry.redhat.io/jboss-amq-6/amq63-openshift:1.2" 80 | } 81 | }, 82 | { 83 | "name": "1.3", 84 | "annotations": { 85 | "description": "JBoss A-MQ 6.3 broker image.", 86 | "iconClass": "icon-amq", 87 | "tags": "messaging,amq,jboss,hidden", 88 | "supports": "amq:6.3,messaging", 89 | "version": "1.3", 90 | "openshift.io/display-name": "Red Hat JBoss A-MQ 6.3" 91 | }, 92 | "referencePolicy": { 93 | "type": "Local" 94 | }, 95 | "from": { 96 | "kind": "DockerImage", 97 | "name": "registry.redhat.io/jboss-amq-6/amq63-openshift:1.3" 98 | } 99 | }, 100 | { 101 | "name": "1.4", 102 | "annotations": { 103 | "description": "JBoss A-MQ 6.3 broker image.", 104 | "iconClass": "icon-amq", 105 | "tags": "messaging,amq,jboss,hidden", 106 | "supports": "amq:6.3,messaging", 107 | "version": "1.4", 108 | "openshift.io/display-name": "Red Hat JBoss A-MQ 6.3" 109 | }, 110 | "referencePolicy": { 111 | "type": "Local" 112 | }, 113 | "from": { 114 | "kind": "DockerImage", 115 | "name": "registry.redhat.io/jboss-amq-6/amq63-openshift:1.4" 116 | } 117 | } 118 | ] 119 | } 120 | } 121 | ] 122 | } 123 | -------------------------------------------------------------------------------- /datagrid.adoc.in: -------------------------------------------------------------------------------- 1 | For simple authentication, set 2 | 3 | USERNAME= 4 | PASSWORD= 5 | 6 | This will enable user authentication with the datagrid. Provided username and password will be used to access the cache over both HTTPS and HotRod. With this case, the user will have all permissions configured. 7 | 8 | Restrictions for password: 9 | 10 | at least 8 characters 11 | at least 1 digit 12 | at least 1 non-alphanumeric symbol 13 | must be different than username 14 | must not be root, admin, or administrator 15 | -------------------------------------------------------------------------------- /datagrid/datagrid71-image-stream.json: -------------------------------------------------------------------------------- 1 | { 2 | "kind": "List", 3 | "apiVersion": "v1", 4 | "metadata": { 5 | "name": "datagrid71-image-streams", 6 | "annotations": { 7 | "description": "ImageStream definitions for Red Hat JBoss Data Grid 7.1.", 8 | "openshift.io/provider-display-name": "Red Hat, Inc." 9 | } 10 | }, 11 | "items": [ 12 | { 13 | "kind": "ImageStream", 14 | "apiVersion": "v1", 15 | "metadata": { 16 | "name": "jboss-datagrid71-openshift", 17 | "annotations": { 18 | "openshift.io/display-name": "Red Hat JBoss Data Grid 7.1", 19 | "openshift.io/provider-display-name": "Red Hat, Inc.", 20 | "version": "1.4.17" 21 | } 22 | }, 23 | "labels": { 24 | "xpaas": "1.4.17" 25 | }, 26 | "spec": { 27 | "tags": [ 28 | { 29 | "name": "1.0", 30 | "annotations": { 31 | "description": "JBoss Data Grid 7.1 S2I images.", 32 | "iconClass": "icon-datagrid", 33 | "tags": "datagrid,jboss,hidden", 34 | "supports": "datagrid:7.1", 35 | "version": "1.0", 36 | "openshift.io/display-name": "Red Hat JBoss Data Grid 7.1" 37 | }, 38 | "referencePolicy": { 39 | "type": "Local" 40 | }, 41 | "from": { 42 | "kind": "DockerImage", 43 | "name": "registry.redhat.io/jboss-datagrid-7/datagrid71-openshift:1.0" 44 | } 45 | }, 46 | { 47 | "name": "1.1", 48 | "annotations": { 49 | "description": "JBoss Data Grid 7.1 S2I images.", 50 | "iconClass": "icon-datagrid", 51 | "tags": "datagrid,jboss,hidden", 52 | "supports": "datagrid:7.1", 53 | "version": "1.1", 54 | "openshift.io/display-name": "Red Hat JBoss Data Grid 7.1" 55 | }, 56 | "referencePolicy": { 57 | "type": "Local" 58 | }, 59 | "from": { 60 | "kind": "DockerImage", 61 | "name": "registry.redhat.io/jboss-datagrid-7/datagrid71-openshift:1.1" 62 | } 63 | }, 64 | { 65 | "name": "1.2", 66 | "annotations": { 67 | "description": "JBoss Data Grid 7.1 S2I images.", 68 | "iconClass": "icon-datagrid", 69 | "tags": "datagrid,jboss,hidden", 70 | "supports": "datagrid:7.1", 71 | "version": "1.2", 72 | "openshift.io/display-name": "Red Hat JBoss Data Grid 7.1" 73 | }, 74 | "referencePolicy": { 75 | "type": "Local" 76 | }, 77 | "from": { 78 | "kind": "DockerImage", 79 | "name": "registry.redhat.io/jboss-datagrid-7/datagrid71-openshift:1.2" 80 | } 81 | }, 82 | { 83 | "name": "1.3", 84 | "annotations": { 85 | "description": "JBoss Data Grid 7.1 S2I images.", 86 | "iconClass": "icon-datagrid", 87 | "tags": "datagrid,jboss,hidden", 88 | "supports": "datagrid:7.1", 89 | "version": "1.3", 90 | "openshift.io/display-name": "Red Hat JBoss Data Grid 7.1" 91 | }, 92 | "referencePolicy": { 93 | "type": "Local" 94 | }, 95 | "from": { 96 | "kind": "DockerImage", 97 | "name": "registry.redhat.io/jboss-datagrid-7/datagrid71-openshift:1.3" 98 | } 99 | } 100 | ] 101 | } 102 | }, 103 | { 104 | "kind": "ImageStream", 105 | "apiVersion": "v1", 106 | "metadata": { 107 | "name": "jboss-datagrid71-client-openshift", 108 | "annotations": { 109 | "openshift.io/display-name": "Red Hat JBoss Data Grid 7.1 Client Modules for EAP", 110 | "openshift.io/provider-display-name": "Red Hat, Inc.", 111 | "version": "1.4.17" 112 | } 113 | }, 114 | "labels": { 115 | "xpaas": "1.4.17" 116 | }, 117 | "spec": { 118 | "tags": [ 119 | { 120 | "name": "1.0", 121 | "annotations": { 122 | "description": "JBoss Data Grid 7.1 Client Modules for EAP.", 123 | "iconClass": "icon-datagrid", 124 | "tags": "client,jboss,hidden", 125 | "version": "1.0", 126 | "openshift.io/display-name": "Red Hat JBoss Data Grid 7.1 Client Modules for EAP" 127 | }, 128 | "referencePolicy": { 129 | "type": "Local" 130 | }, 131 | "from": { 132 | "kind": "DockerImage", 133 | "name": "registry.redhat.io/jboss-datagrid-7/datagrid71-client-openshift:1.0" 134 | } 135 | } 136 | ] 137 | } 138 | } 139 | ] 140 | } 141 | -------------------------------------------------------------------------------- /docs/README.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = Application Templates 8 | 9 | This project contains OpenShift v3 application templates which support applications based on JBoss Middleware products. 10 | Source can be found https://github.com/jboss-openshift/application-templates/tree/master[here]. 11 | 12 | :icons: font 13 | :toc: macro 14 | 15 | toc::[levels=1] 16 | 17 | == JBoss A-MQ 18 | 19 | * link:./amq/amq63-basic.adoc[amq63-basic] 20 | * link:./amq/amq63-persistent-ssl.adoc[amq63-persistent-ssl] 21 | * link:./amq/amq63-persistent.adoc[amq63-persistent] 22 | * link:./amq/amq63-ssl.adoc[amq63-ssl] 23 | 24 | == JBoss Data Grid 25 | 26 | * link:./datagrid/datagrid71-basic.adoc[datagrid71-basic] 27 | * link:./datagrid/datagrid71-https.adoc[datagrid71-https] 28 | * link:./datagrid/datagrid71-mysql-persistent.adoc[datagrid71-mysql-persistent] 29 | * link:./datagrid/datagrid71-mysql.adoc[datagrid71-mysql] 30 | * link:./datagrid/datagrid71-partition.adoc[datagrid71-partition] 31 | * link:./datagrid/datagrid71-postgresql-persistent.adoc[datagrid71-postgresql-persistent] 32 | * link:./datagrid/datagrid71-postgresql.adoc[datagrid71-postgresql] 33 | 34 | == JBoss EAP 35 | 36 | * link:./eap/README_SSO.adoc[README_SSO] 37 | * link:./eap/eap64-amq-persistent-s2i.adoc[eap64-amq-persistent-s2i] 38 | * link:./eap/eap64-amq-s2i.adoc[eap64-amq-s2i] 39 | * link:./eap/eap64-basic-s2i.adoc[eap64-basic-s2i] 40 | * link:./eap/eap64-https-s2i.adoc[eap64-https-s2i] 41 | * link:./eap/eap64-mongodb-persistent-s2i.adoc[eap64-mongodb-persistent-s2i] 42 | * link:./eap/eap64-mongodb-s2i.adoc[eap64-mongodb-s2i] 43 | * link:./eap/eap64-mysql-persistent-s2i.adoc[eap64-mysql-persistent-s2i] 44 | * link:./eap/eap64-mysql-s2i.adoc[eap64-mysql-s2i] 45 | * link:./eap/eap64-postgresql-persistent-s2i.adoc[eap64-postgresql-persistent-s2i] 46 | * link:./eap/eap64-postgresql-s2i.adoc[eap64-postgresql-s2i] 47 | * link:./eap/eap64-sso-s2i.adoc[eap64-sso-s2i] 48 | * link:./eap/eap64-third-party-db-s2i.adoc[eap64-third-party-db-s2i] 49 | * link:./eap/eap64-tx-recovery-s2i.adoc[eap64-tx-recovery-s2i] 50 | * link:./eap/eap71-amq-persistent-s2i.adoc[eap71-amq-persistent-s2i] 51 | * link:./eap/eap71-amq-s2i.adoc[eap71-amq-s2i] 52 | * link:./eap/eap71-basic-s2i.adoc[eap71-basic-s2i] 53 | * link:./eap/eap71-https-s2i.adoc[eap71-https-s2i] 54 | * link:./eap/eap71-mongodb-persistent-s2i.adoc[eap71-mongodb-persistent-s2i] 55 | * link:./eap/eap71-mongodb-s2i.adoc[eap71-mongodb-s2i] 56 | * link:./eap/eap71-mysql-persistent-s2i.adoc[eap71-mysql-persistent-s2i] 57 | * link:./eap/eap71-mysql-s2i.adoc[eap71-mysql-s2i] 58 | * link:./eap/eap71-postgresql-persistent-s2i.adoc[eap71-postgresql-persistent-s2i] 59 | * link:./eap/eap71-postgresql-s2i.adoc[eap71-postgresql-s2i] 60 | * link:./eap/eap71-sso-s2i.adoc[eap71-sso-s2i] 61 | * link:./eap/eap71-third-party-db-s2i.adoc[eap71-third-party-db-s2i] 62 | * link:./eap/eap71-tx-recovery-s2i.adoc[eap71-tx-recovery-s2i] 63 | 64 | == Red Hat Java S2I 65 | 66 | * link:./openjdk/openjdk18-web-basic-s2i.adoc[openjdk18-web-basic-s2i] 67 | 68 | == secrets 69 | 70 | * link:./secrets/amq-app-secret.adoc[amq-app-secret] 71 | * link:./secrets/datagrid-app-secret.adoc[datagrid-app-secret] 72 | * link:./secrets/datavirt-app-secret.adoc[datavirt-app-secret] 73 | * link:./secrets/eap-app-secret.adoc[eap-app-secret] 74 | * link:./secrets/eap7-app-secret.adoc[eap7-app-secret] 75 | * link:./secrets/jws-app-secret.adoc[jws-app-secret] 76 | * link:./secrets/sso-app-secret.adoc[sso-app-secret] 77 | 78 | == JBoss Web Server 79 | 80 | * link:./webserver/jws31-tomcat7-basic-s2i.adoc[jws31-tomcat7-basic-s2i] 81 | * link:./webserver/jws31-tomcat7-https-s2i.adoc[jws31-tomcat7-https-s2i] 82 | * link:./webserver/jws31-tomcat7-mongodb-persistent-s2i.adoc[jws31-tomcat7-mongodb-persistent-s2i] 83 | * link:./webserver/jws31-tomcat7-mongodb-s2i.adoc[jws31-tomcat7-mongodb-s2i] 84 | * link:./webserver/jws31-tomcat7-mysql-persistent-s2i.adoc[jws31-tomcat7-mysql-persistent-s2i] 85 | * link:./webserver/jws31-tomcat7-mysql-s2i.adoc[jws31-tomcat7-mysql-s2i] 86 | * link:./webserver/jws31-tomcat7-postgresql-persistent-s2i.adoc[jws31-tomcat7-postgresql-persistent-s2i] 87 | * link:./webserver/jws31-tomcat7-postgresql-s2i.adoc[jws31-tomcat7-postgresql-s2i] 88 | * link:./webserver/jws31-tomcat8-basic-s2i.adoc[jws31-tomcat8-basic-s2i] 89 | * link:./webserver/jws31-tomcat8-https-s2i.adoc[jws31-tomcat8-https-s2i] 90 | * link:./webserver/jws31-tomcat8-mongodb-persistent-s2i.adoc[jws31-tomcat8-mongodb-persistent-s2i] 91 | * link:./webserver/jws31-tomcat8-mongodb-s2i.adoc[jws31-tomcat8-mongodb-s2i] 92 | * link:./webserver/jws31-tomcat8-mysql-persistent-s2i.adoc[jws31-tomcat8-mysql-persistent-s2i] 93 | * link:./webserver/jws31-tomcat8-mysql-s2i.adoc[jws31-tomcat8-mysql-s2i] 94 | * link:./webserver/jws31-tomcat8-postgresql-persistent-s2i.adoc[jws31-tomcat8-postgresql-persistent-s2i] 95 | * link:./webserver/jws31-tomcat8-postgresql-s2i.adoc[jws31-tomcat8-postgresql-s2i] 96 | 97 | //// 98 | the source for the release notes part of this page is in the file 99 | ./release-notes.adoc.in 100 | //// 101 | 102 | == Release Notes 103 | 104 | === Relese 1.4.17 105 | * RH-SSO 7.2 templates and related documentation for these templates were moved to dedicated link:https://github.com/jboss-container-images/redhat-sso-7-openshift-image[Red Hat Single Sign-On 7 OpenShift container images] repository 106 | 107 | === Release 1.4.16 108 | * Changed image stream URLs from registry.access.redhat.com to registry.redhat.io 109 | * Removed JBoss Data Grid 6.5 resources 110 | * Removed Jboss Data Virtualization 6.3 resources 111 | 112 | === Release 1.4.10 113 | 114 | === Release 1.4.9 115 | * Add probes for DB pods 116 | * Update datavirt secret to use correct location for database files 117 | * Add support for SSO 7.2 118 | * Update EAP templates to reference AMQ 6.3, from 6.2 119 | * Split jboss-image-streams.json into separate files, e.g. eap/eap64-image-sream.json 120 | 121 | === Release 1.4.8 122 | * Update default volume capacity to 1G 123 | * Add emptyDir volumes for non-persistent databases 124 | * Add parameter for configuring memory limits (default 1G) 125 | * Move from KUBE_PING to DNS_PING for clustering in AMQ and EAP based products 126 | * Removed service accounts (DNS_PING requires no special privileges). 127 | * Added templates for automated TX recovery in EAP (tech-preview) 128 | 129 | === Release 1.4.7 130 | * Support clean shutdown on TERM for EAP 7.x based products 131 | * Remove JWS 3.0 templates 132 | * Remove BxMS 6.3 templates 133 | * Deprecate SSO 7.0 134 | * Add support for configuring queue memory limit (AMQ) 135 | 136 | === Release 1.4.5 137 | * Add support for JDG 7.1 138 | 139 | === Release 1.4.4 140 | * Add templates for AMQ message migration 141 | 142 | === Release 1.4.1 143 | * Update BxMS templates to reference AMQ 6.3, from 6.2 144 | 145 | === Release 1.4.0 146 | * Add parameter for specifying DB version 147 | 148 | === Release 1.3.7 149 | * Add client images for datavirt and datagrid 150 | 151 | === Release 1.3.6 152 | * Add support for Java S2I image 153 | 154 | === Release 1.3.5 155 | * Updated datavirt templates to reference new quickstart 156 | * Modified datavirt-app-secret to include secret for datasource configuration 157 | * datavirt-app-secret.json renamed datavirt-app-secret.yaml to improve readability 158 | 159 | === Release 1.3.4 160 | 161 | * New image definitions for: 162 | ** Red Hat JBoss Data Virtualization 6.3 163 | 164 | === Release 1.3.3 165 | 166 | * New image definitions for: 167 | ** Red Hat JBoss BPM Suite 6.3 intelligent process server 168 | ** Red Hat JBoss BRMS 6.3 decision server 169 | 170 | === Release 1.3.2 171 | 172 | * New image definitions for: 173 | ** EAP 6.4 174 | ** EAP 7 175 | ** Red Hat SS0 7 GA 176 | * Added support for configuring EAP timer service to use an external data source 177 | * Service account name is specified using a parameter in EAP and SSO templates 178 | * Added ability to deploy exploded archives 179 | 180 | === Release 1.3.1 181 | 182 | * New image definitions for: 183 | ** EAP 7 GA 184 | ** A-MQ 6 185 | * A-MQ persistent templates now support meshing. Use AMQ_SPLIT=true to use separate storage directories for each pod in a cluster. 186 | 187 | === Release 1.3.0 188 | 189 | * New image definitions for: 190 | ** Red Hat SSO 191 | ** EAP 7 Beta 192 | ** Red Hat SSO support in EAP 6.4 and 7 beta 193 | * Switch templates using deprecated key serviceAccount to serviceAccountName 194 | 195 | === Release 1.2.0 196 | * Added support for JBoss Data Grid 197 | * Added support for JBoss Decision Server 198 | * Added liveness probe to EAP templates 199 | * Encrypt JGroups communication (EAP based templates) 200 | * JMS physical names 201 | * Add Jolokia port to templates 202 | * Renamed APPLICATION_DOMAIN to HOSTNAME_HTTP and HOSTNAME_HTTPS to correspond to http and https routes 203 | 204 | === Release 1.1.0 205 | * Added terminationGracePeriodSeconds to pod templates 206 | * Renamed templates: 207 | ** Include product minor version in names (e.g. eap6-basic-s2i => eap64-basic-s2i) 208 | ** Replaced sti with s2i 209 | * Add ConfigChange trigger to DeploymentConfig in all templates 210 | * Set appropriate defaults so all templates can be instantiated as-is 211 | * Image names and tags have changed from product release to xPaaS release (e.g. jboss-eap-6/eap6-openshift:6.4 => jboss-eap-6/eap64-openshift:1.1) 212 | * ImageStream names have changed to include minor version in names (e.g. jboss-eap6-openshift => jboss-eap64-openshift) 213 | * Use Kubernetes to locate cluster nodes instead of DNS (e.g. KUBE_PING vs DNS_PING in JGroups configuration) 214 | * Add ConfigChange trigger to BuildConfig in all templates 215 | * Add forcePull=true to BuildConfig in all templates 216 | * Add required=true to all required parameters 217 | * Fix inconsistency in A-MQ templates, MQ_PROTOCOL and AMQ_TRANSPORTS 218 | * Modified route names to produce better default hostnames 219 | * Updated source parameter names to be consistent with other OpenShift templates (e.g. GIT_URI => SOURCE_REPOSITORY_URL) 220 | * Add missing mqtt+ssl port to A-MQ templates 221 | * Add parameter to select ImageStream namespace, defaulting to "openshift" 222 | 223 | === Release 1.0.2 224 | * Fix capitalization of GitHub trigger type 225 | 226 | === Release 1.0.1 227 | * Shorten port names 228 | * update deprecated items in BuildConfig 229 | 230 | === Release 1.0.0 231 | * Initial release with support for JBoss EAP, JBoss Web Server, and JBoss A-MQ 232 | 233 | -------------------------------------------------------------------------------- /docs/amq/amq63-basic.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = amq63-basic 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | Application template for JBoss A-MQ brokers. These can be deployed as standalone or in a mesh. This template doesn't feature SSL support. 13 | 14 | toc::[] 15 | 16 | 17 | == Parameters 18 | 19 | Templates allow you to define parameters which take on a value. That value is then substituted wherever the parameter is referenced. 20 | References can be defined in any text field in the objects list field. Refer to the 21 | https://docs.okd.io/latest/architecture/core_concepts/templates.html#parameters[OKD documentation] for more information. 22 | 23 | |======================================================================= 24 | |Variable name |Image Environment Variable |Description |Example value |Required 25 | 26 | |`APPLICATION_NAME` | -- | The name for the application. | broker | True 27 | |`MQ_PROTOCOL` | -- | Protocols to configure, separated by commas. Allowed values are: `openwire`, `amqp`, `stomp` and `mqtt`. | openwire | False 28 | |`MQ_QUEUES` | `AMQ_QUEUES` | Queue names, separated by commas. These queues will be automatically created when the broker starts. If left empty, queues will be still created dynamically. | `${MQ_QUEUES}` | False 29 | |`MQ_TOPICS` | `AMQ_TOPICS` | Topic names, separated by commas. These topics will be automatically created when the broker starts. If left empty, topics will be still created dynamically. | `${MQ_TOPICS}` | False 30 | |`MQ_SERIALIZABLE_PACKAGES` | `MQ_SERIALIZABLE_PACKAGES` | List of packages that are allowed to be serialized for use in ObjectMessage, separated by commas. If your app doesn't use ObjectMessages, leave this blank. This is a security enforcement. For the rationale, see http://activemq.apache.org/objectmessage.html | `${MQ_SERIALIZABLE_PACKAGES}` | False 31 | |`MQ_USERNAME` | `AMQ_USER` | User name for standard broker user. It is required for connecting to the broker. If left empty, it will be generated. | `${MQ_USERNAME}` | False 32 | |`MQ_PASSWORD` | `AMQ_PASSWORD` | Password for standard broker user. It is required for connecting to the broker. If left empty, it will be generated. | `${MQ_PASSWORD}` | False 33 | |`AMQ_MESH_DISCOVERY_TYPE` | `AMQ_MESH_DISCOVERY_TYPE` | The discovery agent type to use for discovering mesh endpoints. 'dns' will use OpenShift's DNS service to resolve endpoints. 'kube' will use Kubernetes REST API to resolve service endpoints. If using 'kube' the service account for the pod must have the 'view' role, which can be added via 'oc policy add-role-to-user view system:serviceaccount::default' where is the project namespace. | dns | False 34 | |`AMQ_STORAGE_USAGE_LIMIT` | `AMQ_STORAGE_USAGE_LIMIT` | Sets the store disk limit usage in activemq.xml. If the value set is greater than the disk size, it will be resized to the available disk space. | 100 gb | False 35 | |`AMQ_QUEUE_MEMORY_LIMIT` | `AMQ_QUEUE_MEMORY_LIMIT` | The queue memory limit (default is 1mb) | `${AMQ_QUEUE_MEMORY_LIMIT}` | False 36 | |`IMAGE_STREAM_NAMESPACE` | -- | Namespace in which the ImageStreams for Red Hat Middleware images are installed. These ImageStreams are normally installed in the openshift namespace. You should only need to modify this if you've installed the ImageStreams in a different namespace/project. | openshift | True 37 | |======================================================================= 38 | 39 | 40 | 41 | == Objects 42 | 43 | The CLI supports various object types. A list of these object types as well as their abbreviations 44 | can be found in the https://docs.okd.io/latest/cli_reference/basic_cli_operations.html#object-types[OKD documentation]. 45 | 46 | 47 | === Services 48 | 49 | A service is an abstraction which defines a logical set of pods and a policy by which to access them. Refer to the 50 | https://docs.okd.io/latest/architecture/core_concepts/pods_and_services.html#services[OKD documentation] for more information. 51 | 52 | |============= 53 | |Service |Port |Name | Description 54 | 55 | .1+| `${APPLICATION_NAME}-amq-amqp` 56 | |5672 | -- 57 | .1+| The broker's AMQP port. 58 | .1+| `${APPLICATION_NAME}-amq-mqtt` 59 | |1883 | -- 60 | .1+| The broker's MQTT port. 61 | .1+| `${APPLICATION_NAME}-amq-stomp` 62 | |61613 | -- 63 | .1+| The broker's STOMP port. 64 | .1+| `${APPLICATION_NAME}-amq-tcp` 65 | |61616 | -- 66 | .1+| The broker's OpenWire port. 67 | .1+| `${APPLICATION_NAME}-amq-mesh` 68 | |61616 | mesh 69 | .1+| Supports node discovery for mesh formation. 70 | |============= 71 | 72 | 73 | 74 | 75 | 76 | 77 | === Deployment Configurations 78 | 79 | A deployment in OpenShift is a replication controller based on a user defined template called a deployment configuration. Deployments are created manually or in response to triggered events. 80 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/how_deployments_work.html#creating-a-deployment-configuration[OKD documentation] for more information. 81 | 82 | 83 | ==== Triggers 84 | 85 | A trigger drives the creation of new deployments in response to events, both inside and outside OpenShift. Refer to the 86 | https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#triggers[OKD documentation] for more information. 87 | 88 | |============ 89 | |Deployment | Triggers 90 | 91 | |`${APPLICATION_NAME}-amq` | ImageChange 92 | |============ 93 | 94 | 95 | 96 | ==== Replicas 97 | 98 | A replication controller ensures that a specified number of pod "replicas" are running at any one time. 99 | If there are too many, the replication controller kills some pods. If there are too few, it starts more. 100 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#scaling[OKD documentation] 101 | for more information. 102 | 103 | |============ 104 | |Deployment | Replicas 105 | 106 | |`${APPLICATION_NAME}-amq` | 1 107 | |============ 108 | 109 | 110 | ==== Pod Template 111 | 112 | 113 | 114 | 115 | ===== Image 116 | 117 | |============ 118 | |Deployment | Image 119 | 120 | |`${APPLICATION_NAME}-amq` | jboss-amq-63 121 | |============ 122 | 123 | 124 | 125 | ===== Readiness Probe 126 | 127 | 128 | .${APPLICATION_NAME}-amq 129 | ---- 130 | /bin/bash -c /opt/amq/bin/readinessProbe.sh 131 | ---- 132 | 133 | 134 | 135 | 136 | ===== Exposed Ports 137 | 138 | |============= 139 | |Deployments | Name | Port | Protocol 140 | 141 | .5+| `${APPLICATION_NAME}-amq` 142 | |jolokia | 8778 | `TCP` 143 | |amqp | 5672 | `TCP` 144 | |mqtt | 1883 | `TCP` 145 | |stomp | 61613 | `TCP` 146 | |tcp | 61616 | `TCP` 147 | |============= 148 | 149 | 150 | 151 | ===== Image Environment Variables 152 | 153 | |======================================================================= 154 | |Deployment |Variable name |Description |Example value 155 | 156 | .11+| `${APPLICATION_NAME}-amq` 157 | |`AMQ_USER` | User name for standard broker user. It is required for connecting to the broker. If left empty, it will be generated. | `${MQ_USERNAME}` 158 | |`AMQ_PASSWORD` | Password for standard broker user. It is required for connecting to the broker. If left empty, it will be generated. | `${MQ_PASSWORD}` 159 | |`AMQ_TRANSPORTS` | -- | `${MQ_PROTOCOL}` 160 | |`AMQ_QUEUES` | Queue names, separated by commas. These queues will be automatically created when the broker starts. If left empty, queues will be still created dynamically. | `${MQ_QUEUES}` 161 | |`AMQ_TOPICS` | Topic names, separated by commas. These topics will be automatically created when the broker starts. If left empty, topics will be still created dynamically. | `${MQ_TOPICS}` 162 | |`MQ_SERIALIZABLE_PACKAGES` | List of packages that are allowed to be serialized for use in ObjectMessage, separated by commas. If your app doesn't use ObjectMessages, leave this blank. This is a security enforcement. For the rationale, see http://activemq.apache.org/objectmessage.html | `${MQ_SERIALIZABLE_PACKAGES}` 163 | |`AMQ_MESH_DISCOVERY_TYPE` | The discovery agent type to use for discovering mesh endpoints. 'dns' will use OpenShift's DNS service to resolve endpoints. 'kube' will use Kubernetes REST API to resolve service endpoints. If using 'kube' the service account for the pod must have the 'view' role, which can be added via 'oc policy add-role-to-user view system:serviceaccount::default' where is the project namespace. | `${AMQ_MESH_DISCOVERY_TYPE}` 164 | |`AMQ_MESH_SERVICE_NAME` | -- | `${APPLICATION_NAME}-amq-mesh` 165 | |`AMQ_MESH_SERVICE_NAMESPACE` | -- | -- 166 | |`AMQ_STORAGE_USAGE_LIMIT` | Sets the store disk limit usage in activemq.xml. If the value set is greater than the disk size, it will be resized to the available disk space. | `${AMQ_STORAGE_USAGE_LIMIT}` 167 | |`AMQ_QUEUE_MEMORY_LIMIT` | The queue memory limit (default is 1mb) | `${AMQ_QUEUE_MEMORY_LIMIT}` 168 | |======================================================================= 169 | 170 | 171 | 172 | 173 | === External Dependencies 174 | 175 | 176 | 177 | 178 | 179 | 180 | 181 | -------------------------------------------------------------------------------- /docs/amq/amq63-persistent.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = amq63-persistent 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | An example JBoss A-MQ application. For more information about using this template, see https://github.com/jboss-openshift/application-templates. 13 | 14 | toc::[] 15 | 16 | 17 | == Parameters 18 | 19 | Templates allow you to define parameters which take on a value. That value is then substituted wherever the parameter is referenced. 20 | References can be defined in any text field in the objects list field. Refer to the 21 | https://docs.okd.io/latest/architecture/core_concepts/templates.html#parameters[OKD documentation] for more information. 22 | 23 | |======================================================================= 24 | |Variable name |Image Environment Variable |Description |Example value |Required 25 | 26 | |`APPLICATION_NAME` | -- | The name for the application. | broker | True 27 | |`AMQ_SPLIT` | `AMQ_SPLIT` | Split the data directory for each node in a mesh, this is now the default behaviour. | true | False 28 | |`MQ_PROTOCOL` | -- | Protocols to configure, separated by commas. Allowed values are: `openwire`, `amqp`, `stomp` and `mqtt`. | openwire | False 29 | |`MQ_QUEUES` | `AMQ_QUEUES` | Queue names, separated by commas. These queues will be automatically created when the broker starts. If left empty, queues will be still created dynamically. | `${MQ_QUEUES}` | False 30 | |`MQ_TOPICS` | `AMQ_TOPICS` | Topic names, separated by commas. These topics will be automatically created when the broker starts. If left empty, topics will be still created dynamically. | `${MQ_TOPICS}` | False 31 | |`MQ_SERIALIZABLE_PACKAGES` | `MQ_SERIALIZABLE_PACKAGES` | List of packages that are allowed to be serialized for use in ObjectMessage, separated by commas. If your app doesn't use ObjectMessages, leave this blank. This is a security enforcement. For the rationale, see http://activemq.apache.org/objectmessage.html | `${MQ_SERIALIZABLE_PACKAGES}` | False 32 | |`VOLUME_CAPACITY` | -- | Size of the volume used by A-MQ for persisting messages. | 1Gi | True 33 | |`MQ_USERNAME` | `AMQ_USER` | User name for standard broker user. It is required for connecting to the broker. If left empty, it will be generated. | `${MQ_USERNAME}` | False 34 | |`MQ_PASSWORD` | `AMQ_PASSWORD` | Password for standard broker user. It is required for connecting to the broker. If left empty, it will be generated. | `${MQ_PASSWORD}` | False 35 | |`AMQ_MESH_DISCOVERY_TYPE` | `AMQ_MESH_DISCOVERY_TYPE` | The discovery agent type to use for discovering mesh endpoints. 'dns' will use OpenShift's DNS service to resolve endpoints. 'kube' will use Kubernetes REST API to resolve service endpoints. If using 'kube' the service account for the pod must have the 'view' role, which can be added via 'oc policy add-role-to-user view system:serviceaccount::default' where is the project namespace. | dns | False 36 | |`AMQ_STORAGE_USAGE_LIMIT` | `AMQ_STORAGE_USAGE_LIMIT` | Sets the store disk limit usage in activemq.xml. If the value set is greater than the disk size, it will be resized to the available disk space. | 100 gb | False 37 | |`AMQ_QUEUE_MEMORY_LIMIT` | `AMQ_QUEUE_MEMORY_LIMIT` | The queue memory limit (default is 1mb) | `${AMQ_QUEUE_MEMORY_LIMIT}` | False 38 | |`IMAGE_STREAM_NAMESPACE` | -- | Namespace in which the ImageStreams for Red Hat Middleware images are installed. These ImageStreams are normally installed in the openshift namespace. You should only need to modify this if you've installed the ImageStreams in a different namespace/project. | openshift | True 39 | |======================================================================= 40 | 41 | 42 | 43 | == Objects 44 | 45 | The CLI supports various object types. A list of these object types as well as their abbreviations 46 | can be found in the https://docs.okd.io/latest/cli_reference/basic_cli_operations.html#object-types[OKD documentation]. 47 | 48 | 49 | === Services 50 | 51 | A service is an abstraction which defines a logical set of pods and a policy by which to access them. Refer to the 52 | https://docs.okd.io/latest/architecture/core_concepts/pods_and_services.html#services[OKD documentation] for more information. 53 | 54 | |============= 55 | |Service |Port |Name | Description 56 | 57 | .1+| `${APPLICATION_NAME}-amq-amqp` 58 | |5672 | -- 59 | .1+| The broker's AMQP port. 60 | .1+| `${APPLICATION_NAME}-amq-mqtt` 61 | |1883 | -- 62 | .1+| The broker's MQTT port. 63 | .1+| `${APPLICATION_NAME}-amq-stomp` 64 | |61613 | -- 65 | .1+| The broker's STOMP port. 66 | .1+| `${APPLICATION_NAME}-amq-tcp` 67 | |61616 | -- 68 | .1+| The broker's OpenWire port. 69 | .1+| `${APPLICATION_NAME}-amq-mesh` 70 | |61616 | mesh 71 | .1+| Supports node discovery for mesh formation. 72 | |============= 73 | 74 | 75 | 76 | 77 | 78 | 79 | === Deployment Configurations 80 | 81 | A deployment in OpenShift is a replication controller based on a user defined template called a deployment configuration. Deployments are created manually or in response to triggered events. 82 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/how_deployments_work.html#creating-a-deployment-configuration[OKD documentation] for more information. 83 | 84 | 85 | ==== Triggers 86 | 87 | A trigger drives the creation of new deployments in response to events, both inside and outside OpenShift. Refer to the 88 | https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#triggers[OKD documentation] for more information. 89 | 90 | |============ 91 | |Deployment | Triggers 92 | 93 | |`${APPLICATION_NAME}-amq` | ImageChange 94 | |`${APPLICATION_NAME}-drainer` | ImageChange 95 | |============ 96 | 97 | 98 | 99 | ==== Replicas 100 | 101 | A replication controller ensures that a specified number of pod "replicas" are running at any one time. 102 | If there are too many, the replication controller kills some pods. If there are too few, it starts more. 103 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#scaling[OKD documentation] 104 | for more information. 105 | 106 | |============ 107 | |Deployment | Replicas 108 | 109 | |`${APPLICATION_NAME}-amq` | 1 110 | |`${APPLICATION_NAME}-drainer` | 1 111 | |============ 112 | 113 | 114 | ==== Pod Template 115 | 116 | 117 | 118 | 119 | ===== Image 120 | 121 | |============ 122 | |Deployment | Image 123 | 124 | |`${APPLICATION_NAME}-amq` | jboss-amq-63 125 | |`${APPLICATION_NAME}-drainer` | jboss-amq-63 126 | |============ 127 | 128 | 129 | 130 | ===== Readiness Probe 131 | 132 | 133 | .${APPLICATION_NAME}-amq 134 | ---- 135 | /bin/bash -c /opt/amq/bin/readinessProbe.sh 136 | ---- 137 | 138 | 139 | 140 | 141 | ===== Exposed Ports 142 | 143 | |============= 144 | |Deployments | Name | Port | Protocol 145 | 146 | .5+| `${APPLICATION_NAME}-amq` 147 | |jolokia | 8778 | `TCP` 148 | |amqp | 5672 | `TCP` 149 | |mqtt | 1883 | `TCP` 150 | |stomp | 61613 | `TCP` 151 | |tcp | 61616 | `TCP` 152 | .2+| `${APPLICATION_NAME}-drainer` 153 | |jolokia | 8778 | `TCP` 154 | |tcp | 61616 | `TCP` 155 | |============= 156 | 157 | 158 | 159 | ===== Image Environment Variables 160 | 161 | |======================================================================= 162 | |Deployment |Variable name |Description |Example value 163 | 164 | .12+| `${APPLICATION_NAME}-amq` 165 | |`AMQ_USER` | User name for standard broker user. It is required for connecting to the broker. If left empty, it will be generated. | `${MQ_USERNAME}` 166 | |`AMQ_PASSWORD` | Password for standard broker user. It is required for connecting to the broker. If left empty, it will be generated. | `${MQ_PASSWORD}` 167 | |`AMQ_TRANSPORTS` | -- | `${MQ_PROTOCOL}` 168 | |`AMQ_QUEUES` | Queue names, separated by commas. These queues will be automatically created when the broker starts. If left empty, queues will be still created dynamically. | `${MQ_QUEUES}` 169 | |`AMQ_TOPICS` | Topic names, separated by commas. These topics will be automatically created when the broker starts. If left empty, topics will be still created dynamically. | `${MQ_TOPICS}` 170 | |`MQ_SERIALIZABLE_PACKAGES` | List of packages that are allowed to be serialized for use in ObjectMessage, separated by commas. If your app doesn't use ObjectMessages, leave this blank. This is a security enforcement. For the rationale, see http://activemq.apache.org/objectmessage.html | `${MQ_SERIALIZABLE_PACKAGES}` 171 | |`AMQ_SPLIT` | Split the data directory for each node in a mesh, this is now the default behaviour. | `${AMQ_SPLIT}` 172 | |`AMQ_MESH_DISCOVERY_TYPE` | The discovery agent type to use for discovering mesh endpoints. 'dns' will use OpenShift's DNS service to resolve endpoints. 'kube' will use Kubernetes REST API to resolve service endpoints. If using 'kube' the service account for the pod must have the 'view' role, which can be added via 'oc policy add-role-to-user view system:serviceaccount::default' where is the project namespace. | `${AMQ_MESH_DISCOVERY_TYPE}` 173 | |`AMQ_MESH_SERVICE_NAME` | -- | `${APPLICATION_NAME}-amq-mesh` 174 | |`AMQ_MESH_SERVICE_NAMESPACE` | -- | -- 175 | |`AMQ_STORAGE_USAGE_LIMIT` | Sets the store disk limit usage in activemq.xml. If the value set is greater than the disk size, it will be resized to the available disk space. | `${AMQ_STORAGE_USAGE_LIMIT}` 176 | |`AMQ_QUEUE_MEMORY_LIMIT` | The queue memory limit (default is 1mb) | `${AMQ_QUEUE_MEMORY_LIMIT}` 177 | .4+| `${APPLICATION_NAME}-drainer` 178 | |`AMQ_USER` | User name for standard broker user. It is required for connecting to the broker. If left empty, it will be generated. | `${MQ_USERNAME}` 179 | |`AMQ_PASSWORD` | Password for standard broker user. It is required for connecting to the broker. If left empty, it will be generated. | `${MQ_PASSWORD}` 180 | |`AMQ_MESH_SERVICE_NAME` | -- | `${APPLICATION_NAME}-amq-mesh` 181 | |`AMQ_MESH_SERVICE_NAMESPACE` | -- | -- 182 | |======================================================================= 183 | 184 | 185 | 186 | ===== Volumes 187 | 188 | |============= 189 | |Deployment |Name | mountPath | Purpose | readOnly 190 | 191 | |`${APPLICATION_NAME}-amq` | `${APPLICATION_NAME}-amq-pvol` | `/opt/amq/data` | kahadb | false 192 | |`${APPLICATION_NAME}-drainer` | `${APPLICATION_NAME}-amq-pvol` | `/opt/amq/data` | kahadb | false 193 | |============= 194 | 195 | 196 | === External Dependencies 197 | 198 | 199 | ==== Volume Claims 200 | 201 | A `PersistentVolume` object is a storage resource in an OpenShift cluster. Storage is provisioned by an administrator 202 | by creating `PersistentVolume` objects from sources such as GCE Persistent Disks, AWS Elastic Block Stores (EBS), and NFS mounts. 203 | Refer to the https://docs.okd.io/latest/dev_guide/persistent_volumes.html#overview[OKD documentation] for 204 | more information. 205 | 206 | |============= 207 | |Name | Access Mode 208 | 209 | |`${APPLICATION_NAME}-amq-claim` | ReadWriteMany 210 | |============= 211 | 212 | 213 | 214 | 215 | 216 | 217 | 218 | -------------------------------------------------------------------------------- /docs/datagrid/datagrid71-basic.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = datagrid71-basic 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | An example JBoss Data Grid application. For more information about using this template, see https://github.com/jboss-openshift/application-templates. 13 | 14 | For simple authentication, set 15 | 16 | USERNAME= 17 | PASSWORD= 18 | 19 | This will enable user authentication with the datagrid. Provided username and password will be used to access the cache over both HTTPS and HotRod. With this case, the user will have all permissions configured. 20 | 21 | Restrictions for password: 22 | 23 | at least 8 characters 24 | at least 1 digit 25 | at least 1 non-alphanumeric symbol 26 | must be different than username 27 | must not be root, admin, or administrator 28 | 29 | 30 | toc::[] 31 | 32 | 33 | == Parameters 34 | 35 | Templates allow you to define parameters which take on a value. That value is then substituted wherever the parameter is referenced. 36 | References can be defined in any text field in the objects list field. Refer to the 37 | https://docs.okd.io/latest/architecture/core_concepts/templates.html#parameters[OKD documentation] for more information. 38 | 39 | |======================================================================= 40 | |Variable name |Image Environment Variable |Description |Example value |Required 41 | 42 | |`APPLICATION_NAME` | -- | The name for the application. | datagrid-app | True 43 | |`HOSTNAME_HTTP` | -- | Custom hostname for http service route. Leave blank for default hostname, e.g.: -. | -- | False 44 | |`USERNAME` | `USERNAME` | User name for JDG user. | `${USERNAME}` | False 45 | |`PASSWORD` | `PASSWORD` | The password to access the JDG Caches. Must be different than username; must not be root, admin, or administrator; must contain at least 8 characters, 1 alphabetic character(s), 1 digit(s), and 1 non-alphanumeric symbol(s). (optional) | `${PASSWORD}` | False 46 | |`ADMIN_GROUP` | `ADMIN_GROUP` | Comma delimited list of roles/groups associated with the JDG user | `${ADMIN_GROUP}` | False 47 | |`HOTROD_AUTHENTICATION` | `HOTROD_AUTHENTICATION` | Enable Hotrod Authentication | `${HOTROD_AUTHENTICATION}` | False 48 | |`CONTAINER_SECURITY_ROLE_MAPPER` | `CONTAINER_SECURITY_ROLE_MAPPER` | Defines which role mapper to use for cache authentication | `${CONTAINER_SECURITY_ROLE_MAPPER}` | False 49 | |`CONTAINER_SECURITY_ROLES` | `CONTAINER_SECURITY_ROLES` | Comma delimited list of role names and assigned permissions | `${CONTAINER_SECURITY_ROLES}` | False 50 | |`IMAGE_STREAM_NAMESPACE` | -- | Namespace in which the ImageStreams for Red Hat Middleware images are installed. These ImageStreams are normally installed in the openshift namespace. You should only need to modify this if you've installed the ImageStreams in a different namespace/project. | openshift | True 51 | |`INFINISPAN_CONNECTORS` | `INFINISPAN_CONNECTORS` | Comma-separated list of connector types that should be configured (defaults to 'memcached,hotrod,rest') | hotrod,memcached,rest | False 52 | |`CACHE_NAMES` | `CACHE_NAMES` | Comma-separated list of caches to configure. By default, a distributed-cache, with a mode of SYNC will be configured for each entry. | `${CACHE_NAMES}` | False 53 | |`DATAVIRT_CACHE_NAMES` | `CACHE_NAMES` | Comma-separated list of caches to configure for use by Red Hat JBoss Data Virtualization for materialization of views. Three caches will be created for each named cache: , _staging and _alias. | `${CACHE_NAMES}` | False 54 | |`CACHE_TYPE_DEFAULT` | `CACHE_TYPE_DEFAULT` | Default cache type for all caches. If empty then distributed will be the default | `${CACHE_TYPE_DEFAULT}` | False 55 | |`ENCRYPTION_REQUIRE_SSL_CLIENT_AUTH` | `ENCRYPTION_REQUIRE_SSL_CLIENT_AUTH` | | `${ENCRYPTION_REQUIRE_SSL_CLIENT_AUTH}` | False 56 | |`MEMCACHED_CACHE` | `MEMCACHED_CACHE` | The name of the cache to expose through this memcached connector (defaults to 'default') | default | False 57 | |`REST_SECURITY_DOMAIN` | `REST_SECURITY_DOMAIN` | The domain, declared in the security subsystem, that should be used to authenticate access to the REST endpoint | `${REST_SECURITY_DOMAIN}` | False 58 | |`JGROUPS_CLUSTER_PASSWORD` | `PASSWORD` | JGroups cluster password | `${PASSWORD}` | True 59 | |`MEMORY_LIMIT` | -- | Container memory limit | 1Gi | False 60 | |======================================================================= 61 | 62 | 63 | 64 | == Objects 65 | 66 | The CLI supports various object types. A list of these object types as well as their abbreviations 67 | can be found in the https://docs.okd.io/latest/cli_reference/basic_cli_operations.html#object-types[OKD documentation]. 68 | 69 | 70 | === Services 71 | 72 | A service is an abstraction which defines a logical set of pods and a policy by which to access them. Refer to the 73 | https://docs.okd.io/latest/architecture/core_concepts/pods_and_services.html#services[OKD documentation] for more information. 74 | 75 | |============= 76 | |Service |Port |Name | Description 77 | 78 | .1+| `${APPLICATION_NAME}` 79 | |8080 | -- 80 | .1+| The web server's HTTP port. 81 | .1+| `${APPLICATION_NAME}-memcached` 82 | |11211 | -- 83 | .1+| Memcached service for clustered applications. 84 | .1+| `${APPLICATION_NAME}-hotrod` 85 | |11333 | -- 86 | .1+| Hot Rod service for clustered applications. 87 | .1+| `${APPLICATION_NAME}-ping` 88 | |8888 | ping 89 | .1+| The JGroups ping port for clustering. 90 | |============= 91 | 92 | 93 | 94 | === Routes 95 | 96 | A route is a way to expose a service by giving it an externally-reachable hostname such as `www.example.com`. A defined route and the endpoints 97 | identified by its service can be consumed by a router to provide named connectivity from external clients to your applications. Each route consists 98 | of a route name, service selector, and (optionally) security configuration. Refer to the 99 | https://docs.okd.io/latest/dev_guide/routes.html[OKD documentation] for more information. 100 | 101 | |============= 102 | | Service | Security | Hostname 103 | 104 | |`${APPLICATION_NAME}-http` | none | `${HOSTNAME_HTTP}` 105 | |============= 106 | 107 | 108 | 109 | 110 | === Deployment Configurations 111 | 112 | A deployment in OpenShift is a replication controller based on a user defined template called a deployment configuration. Deployments are created manually or in response to triggered events. 113 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/how_deployments_work.html#creating-a-deployment-configuration[OKD documentation] for more information. 114 | 115 | 116 | ==== Triggers 117 | 118 | A trigger drives the creation of new deployments in response to events, both inside and outside OpenShift. Refer to the 119 | https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#triggers[OKD documentation] for more information. 120 | 121 | |============ 122 | |Deployment | Triggers 123 | 124 | |`${APPLICATION_NAME}` | ImageChange 125 | |============ 126 | 127 | 128 | 129 | ==== Replicas 130 | 131 | A replication controller ensures that a specified number of pod "replicas" are running at any one time. 132 | If there are too many, the replication controller kills some pods. If there are too few, it starts more. 133 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#scaling[OKD documentation] 134 | for more information. 135 | 136 | |============ 137 | |Deployment | Replicas 138 | 139 | |`${APPLICATION_NAME}` | 1 140 | |============ 141 | 142 | 143 | ==== Pod Template 144 | 145 | 146 | 147 | 148 | ===== Image 149 | 150 | |============ 151 | |Deployment | Image 152 | 153 | |`${APPLICATION_NAME}` | jboss-datagrid71-openshift 154 | |============ 155 | 156 | 157 | 158 | ===== Readiness Probe 159 | 160 | 161 | .${APPLICATION_NAME} 162 | ---- 163 | /bin/bash -c /opt/datagrid/bin/readinessProbe.sh 164 | ---- 165 | 166 | 167 | 168 | 169 | ===== Exposed Ports 170 | 171 | |============= 172 | |Deployments | Name | Port | Protocol 173 | 174 | .6+| `${APPLICATION_NAME}` 175 | |jolokia | 8778 | `TCP` 176 | |http | 8080 | `TCP` 177 | |ping | 8888 | `TCP` 178 | |memcached | 11211 | `TCP` 179 | |hotrod-internal | 11222 | `TCP` 180 | |hotrod | 11333 | `TCP` 181 | |============= 182 | 183 | 184 | 185 | ===== Image Environment Variables 186 | 187 | |======================================================================= 188 | |Deployment |Variable name |Description |Example value 189 | 190 | .18+| `${APPLICATION_NAME}` 191 | |`USERNAME` | User name for JDG user. | `${USERNAME}` 192 | |`PASSWORD` | The password to access the JDG Caches. Must be different than username; must not be root, admin, or administrator; must contain at least 8 characters, 1 alphabetic character(s), 1 digit(s), and 1 non-alphanumeric symbol(s). (optional) | `${PASSWORD}` 193 | |`ADMIN_GROUP` | Comma delimited list of roles/groups associated with the JDG user | `${ADMIN_GROUP}` 194 | |`HOTROD_AUTHENTICATION` | Enable Hotrod Authentication | `${HOTROD_AUTHENTICATION}` 195 | |`CONTAINER_SECURITY_ROLE_MAPPER` | Defines which role mapper to use for cache authentication | `${CONTAINER_SECURITY_ROLE_MAPPER}` 196 | |`CONTAINER_SECURITY_ROLES` | Comma delimited list of role names and assigned permissions | `${CONTAINER_SECURITY_ROLES}` 197 | |`JGROUPS_PING_PROTOCOL` | -- | openshift.DNS_PING 198 | |`OPENSHIFT_DNS_PING_SERVICE_NAME` | -- | `${APPLICATION_NAME}-ping` 199 | |`OPENSHIFT_DNS_PING_SERVICE_PORT` | -- | 8888 200 | |`INFINISPAN_CONNECTORS` | Comma-separated list of connector types that should be configured (defaults to 'memcached,hotrod,rest') | `${INFINISPAN_CONNECTORS}` 201 | |`CACHE_NAMES` | Comma-separated list of caches to configure. By default, a distributed-cache, with a mode of SYNC will be configured for each entry. | `${CACHE_NAMES}` 202 | |`DATAVIRT_CACHE_NAMES` | Comma-separated list of caches to configure. By default, a distributed-cache, with a mode of SYNC will be configured for each entry. | `${DATAVIRT_CACHE_NAMES}` 203 | |`CACHE_TYPE_DEFAULT` | Default cache type for all caches. If empty then distributed will be the default | `${CACHE_TYPE_DEFAULT}` 204 | |`ENCRYPTION_REQUIRE_SSL_CLIENT_AUTH` | | `${ENCRYPTION_REQUIRE_SSL_CLIENT_AUTH}` 205 | |`HOTROD_SERVICE_NAME` | -- | `${APPLICATION_NAME}-hotrod` 206 | |`MEMCACHED_CACHE` | The name of the cache to expose through this memcached connector (defaults to 'default') | `${MEMCACHED_CACHE}` 207 | |`REST_SECURITY_DOMAIN` | The domain, declared in the security subsystem, that should be used to authenticate access to the REST endpoint | `${REST_SECURITY_DOMAIN}` 208 | |`JGROUPS_CLUSTER_PASSWORD` | The password to access the JDG Caches. Must be different than username; must not be root, admin, or administrator; must contain at least 8 characters, 1 alphabetic character(s), 1 digit(s), and 1 non-alphanumeric symbol(s). (optional) | `${JGROUPS_CLUSTER_PASSWORD}` 209 | |======================================================================= 210 | 211 | 212 | 213 | 214 | === External Dependencies 215 | 216 | 217 | 218 | 219 | 220 | 221 | 222 | -------------------------------------------------------------------------------- /docs/eap/eap64-basic-s2i.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = eap64-basic-s2i 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | An example EAP 6 application. For more information about using this template, see https://github.com/jboss-openshift/application-templates. 13 | 14 | toc::[] 15 | 16 | 17 | == Parameters 18 | 19 | Templates allow you to define parameters which take on a value. That value is then substituted wherever the parameter is referenced. 20 | References can be defined in any text field in the objects list field. Refer to the 21 | https://docs.okd.io/latest/architecture/core_concepts/templates.html#parameters[OKD documentation] for more information. 22 | 23 | |======================================================================= 24 | |Variable name |Image Environment Variable |Description |Example value |Required 25 | 26 | |`APPLICATION_NAME` | -- | The name for the application. | eap-app | True 27 | |`HOSTNAME_HTTP` | -- | Custom hostname for http service route. Leave blank for default hostname, e.g.: -. | -- | False 28 | |`SOURCE_REPOSITORY_URL` | -- | Git source URI for application | https://github.com/jboss-developer/jboss-eap-quickstarts | True 29 | |`SOURCE_REPOSITORY_REF` | -- | Git branch/tag reference | 6.4.x | False 30 | |`CONTEXT_DIR` | -- | Path within Git project to build; empty for root project directory. | kitchensink | False 31 | |`HORNETQ_QUEUES` | `HORNETQ_QUEUES` | Queue names | `${HORNETQ_QUEUES}` | False 32 | |`HORNETQ_TOPICS` | `HORNETQ_TOPICS` | Topic names | `${HORNETQ_TOPICS}` | False 33 | |`HORNETQ_CLUSTER_PASSWORD` | `HORNETQ_CLUSTER_PASSWORD` | HornetQ cluster admin password | `${HORNETQ_CLUSTER_PASSWORD}` | True 34 | |`GITHUB_WEBHOOK_SECRET` | -- | GitHub trigger secret | secret101 | True 35 | |`GENERIC_WEBHOOK_SECRET` | -- | Generic build trigger secret | secret101 | True 36 | |`IMAGE_STREAM_NAMESPACE` | -- | Namespace in which the ImageStreams for Red Hat Middleware images are installed. These ImageStreams are normally installed in the openshift namespace. You should only need to modify this if you've installed the ImageStreams in a different namespace/project. | openshift | True 37 | |`JGROUPS_CLUSTER_PASSWORD` | `JGROUPS_CLUSTER_PASSWORD` | JGroups cluster password | `${JGROUPS_CLUSTER_PASSWORD}` | True 38 | |`AUTO_DEPLOY_EXPLODED` | `AUTO_DEPLOY_EXPLODED` | Controls whether exploded deployment content should be automatically deployed | false | False 39 | |`MAVEN_MIRROR_URL` | -- | Maven mirror to use for S2I builds | -- | False 40 | |`ARTIFACT_DIR` | -- | List of directories from which archives will be copied into the deployment folder. If unspecified, all archives in /target will be copied. | -- | False 41 | |`MEMORY_LIMIT` | -- | Container memory limit | 1Gi | False 42 | |======================================================================= 43 | 44 | 45 | 46 | == Objects 47 | 48 | The CLI supports various object types. A list of these object types as well as their abbreviations 49 | can be found in the https://docs.okd.io/latest/cli_reference/basic_cli_operations.html#object-types[OKD documentation]. 50 | 51 | 52 | === Services 53 | 54 | A service is an abstraction which defines a logical set of pods and a policy by which to access them. Refer to the 55 | https://docs.okd.io/latest/architecture/core_concepts/pods_and_services.html#services[OKD documentation] for more information. 56 | 57 | |============= 58 | |Service |Port |Name | Description 59 | 60 | .1+| `${APPLICATION_NAME}` 61 | |8080 | -- 62 | .1+| The web server's http port. 63 | .1+| `${APPLICATION_NAME}-ping` 64 | |8888 | ping 65 | .1+| The JGroups ping port for clustering. 66 | |============= 67 | 68 | 69 | 70 | === Routes 71 | 72 | A route is a way to expose a service by giving it an externally-reachable hostname such as `www.example.com`. A defined route and the endpoints 73 | identified by its service can be consumed by a router to provide named connectivity from external clients to your applications. Each route consists 74 | of a route name, service selector, and (optionally) security configuration. Refer to the 75 | https://docs.okd.io/latest/dev_guide/routes.html[OKD documentation] for more information. 76 | 77 | |============= 78 | | Service | Security | Hostname 79 | 80 | |`${APPLICATION_NAME}-http` | none | `${HOSTNAME_HTTP}` 81 | |============= 82 | 83 | 84 | 85 | === Build Configurations 86 | 87 | A `buildConfig` describes a single build definition and a set of triggers for when a new build should be created. 88 | A `buildConfig` is a REST object, which can be used in a POST to the API server to create a new instance. Refer to 89 | the https://docs.okd.io/latest/dev_guide/builds/index.html[OKD documentation] 90 | for more information. 91 | 92 | |============= 93 | | S2I image | link | Build output | BuildTriggers and Settings 94 | 95 | |jboss-eap64-openshift:1.8 | link:../../eap/eap-openshift{outfilesuffix}[`jboss-eap-6/eap64-openshift`] | `${APPLICATION_NAME}:latest` | GitHub, Generic, ImageChange, ConfigChange 96 | |============= 97 | 98 | 99 | === Deployment Configurations 100 | 101 | A deployment in OpenShift is a replication controller based on a user defined template called a deployment configuration. Deployments are created manually or in response to triggered events. 102 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/how_deployments_work.html#creating-a-deployment-configuration[OKD documentation] for more information. 103 | 104 | 105 | ==== Triggers 106 | 107 | A trigger drives the creation of new deployments in response to events, both inside and outside OpenShift. Refer to the 108 | https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#triggers[OKD documentation] for more information. 109 | 110 | |============ 111 | |Deployment | Triggers 112 | 113 | |`${APPLICATION_NAME}` | ImageChange 114 | |============ 115 | 116 | 117 | 118 | ==== Replicas 119 | 120 | A replication controller ensures that a specified number of pod "replicas" are running at any one time. 121 | If there are too many, the replication controller kills some pods. If there are too few, it starts more. 122 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#scaling[OKD documentation] 123 | for more information. 124 | 125 | |============ 126 | |Deployment | Replicas 127 | 128 | |`${APPLICATION_NAME}` | 1 129 | |============ 130 | 131 | 132 | ==== Pod Template 133 | 134 | 135 | 136 | 137 | ===== Image 138 | 139 | |============ 140 | |Deployment | Image 141 | 142 | |`${APPLICATION_NAME}` | `${APPLICATION_NAME}` 143 | |============ 144 | 145 | 146 | 147 | ===== Readiness Probe 148 | 149 | 150 | .${APPLICATION_NAME} 151 | ---- 152 | /bin/bash -c /opt/eap/bin/readinessProbe.sh 153 | ---- 154 | 155 | 156 | 157 | 158 | ===== Exposed Ports 159 | 160 | |============= 161 | |Deployments | Name | Port | Protocol 162 | 163 | .3+| `${APPLICATION_NAME}` 164 | |jolokia | 8778 | `TCP` 165 | |http | 8080 | `TCP` 166 | |ping | 8888 | `TCP` 167 | |============= 168 | 169 | 170 | 171 | ===== Image Environment Variables 172 | 173 | |======================================================================= 174 | |Deployment |Variable name |Description |Example value 175 | 176 | .8+| `${APPLICATION_NAME}` 177 | |`JGROUPS_PING_PROTOCOL` | -- | openshift.DNS_PING 178 | |`OPENSHIFT_DNS_PING_SERVICE_NAME` | -- | `${APPLICATION_NAME}-ping` 179 | |`OPENSHIFT_DNS_PING_SERVICE_PORT` | -- | 8888 180 | |`HORNETQ_CLUSTER_PASSWORD` | HornetQ cluster admin password | `${HORNETQ_CLUSTER_PASSWORD}` 181 | |`HORNETQ_QUEUES` | Queue names | `${HORNETQ_QUEUES}` 182 | |`HORNETQ_TOPICS` | Topic names | `${HORNETQ_TOPICS}` 183 | |`JGROUPS_CLUSTER_PASSWORD` | JGroups cluster password | `${JGROUPS_CLUSTER_PASSWORD}` 184 | |`AUTO_DEPLOY_EXPLODED` | Controls whether exploded deployment content should be automatically deployed | `${AUTO_DEPLOY_EXPLODED}` 185 | |======================================================================= 186 | 187 | 188 | 189 | 190 | === External Dependencies 191 | 192 | 193 | 194 | 195 | 196 | 197 | [[clustering]] 198 | ==== Clustering 199 | 200 | Clustering in OpenShift EAP is achieved through one of two discovery mechanisms: 201 | Kubernetes or DNS. This is done by configuring the JGroups protocol stack in 202 | standalone-openshift.xml with either the `` or `` 203 | elements. The templates are configured to use `DNS_PING`, however `KUBE_PING`is 204 | the default used by the image. 205 | 206 | The discovery mechanism used is specified by the `JGROUPS_PING_PROTOCOL` environment 207 | variable which can be set to either `openshift.DNS_PING` or `openshift.KUBE_PING`. 208 | `openshift.KUBE_PING` is the default used by the image if no value is specified 209 | for `JGROUPS_PING_PROTOCOL`. 210 | 211 | For DNS_PING to work, the following steps must be taken: 212 | 213 | . The `OPENSHIFT_DNS_PING_SERVICE_NAME` environment variable must be set to the 214 | name of the ping service for the cluster (see table above). If not set, the 215 | server will act as if it is a single-node cluster (a "cluster of one"). 216 | . The `OPENSHIFT_DNS_PING_SERVICE_PORT` environment variables should be set to 217 | the port number on which the ping service is exposed (see table above). The 218 | `DNS_PING` protocol will attempt to discern the port from the SRV records, if 219 | it can, otherwise it will default to 8888. 220 | . A ping service which exposes the ping port must be defined. This service 221 | should be "headless" (ClusterIP=None) and must have the following: 222 | .. The port must be named for port discovery to work. 223 | .. It must be annotated with `service.alpha.kubernetes.io/tolerate-unready-endpoints` 224 | set to `"true"`. Omitting this annotation will result in each node forming 225 | their own "cluster of one" during startup, then merging their cluster into 226 | the other nodes' clusters after startup (as the other nodes are not detected 227 | until after they have started). 228 | 229 | .Example ping service for use with DNS_PING 230 | [source,yaml] 231 | ---- 232 | kind: Service 233 | apiVersion: v1 234 | spec: 235 | clusterIP: None 236 | ports: 237 | - name: ping 238 | port: 8888 239 | selector: 240 | deploymentConfig: eap-app 241 | metadata: 242 | name: eap-app-ping 243 | annotations: 244 | service.alpha.kubernetes.io/tolerate-unready-endpoints: "true" 245 | description: "The JGroups ping port for clustering." 246 | ---- 247 | 248 | For `KUBE_PING` to work, the following steps must be taken: 249 | 250 | . The `OPENSHIFT_KUBE_PING_NAMESPACE` environment variable must be set (see table above). 251 | If not set, the server will act as if it is a single-node cluster (a "cluster of one"). 252 | . The `OPENSHIFT_KUBE_PING_LABELS` environment variables should be set (see table above). 253 | If not set, pods outside of your application (albeit in your namespace) will try to join. 254 | . Authorization must be granted to the service account the pod is running under to be 255 | allowed to access Kubernetes' REST api. This is done on the command line. 256 | 257 | .Policy commands 258 | ==== 259 | Using the default service account in the myproject namespace: 260 | .... 261 | oc policy add-role-to-user view system:serviceaccount:myproject:default -n myproject 262 | .... 263 | Using the eap-service-account in the myproject namespace: 264 | .... 265 | oc policy add-role-to-user view system:serviceaccount:myproject:eap-service-account -n myproject 266 | .... 267 | ==== 268 | 269 | 270 | -------------------------------------------------------------------------------- /docs/eap/eap71-basic-s2i.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = eap71-basic-s2i 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | An example EAP 7 application. For more information about using this template, see https://github.com/jboss-openshift/application-templates. 13 | 14 | toc::[] 15 | 16 | 17 | == Parameters 18 | 19 | Templates allow you to define parameters which take on a value. That value is then substituted wherever the parameter is referenced. 20 | References can be defined in any text field in the objects list field. Refer to the 21 | https://docs.okd.io/latest/architecture/core_concepts/templates.html#parameters[OKD documentation] for more information. 22 | 23 | |======================================================================= 24 | |Variable name |Image Environment Variable |Description |Example value |Required 25 | 26 | |`APPLICATION_NAME` | -- | The name for the application. | eap-app | True 27 | |`HOSTNAME_HTTP` | -- | Custom hostname for http service route. Leave blank for default hostname, e.g.: -. | -- | False 28 | |`SOURCE_REPOSITORY_URL` | -- | Git source URI for application | https://github.com/jboss-developer/jboss-eap-quickstarts | True 29 | |`SOURCE_REPOSITORY_REF` | -- | Git branch/tag reference | 7.1.0.GA | False 30 | |`CONTEXT_DIR` | -- | Path within Git project to build; empty for root project directory. | kitchensink | False 31 | |`MQ_QUEUES` | `MQ_QUEUES` | Queue names | `${MQ_QUEUES}` | False 32 | |`MQ_TOPICS` | `MQ_TOPICS` | Topic names | `${MQ_TOPICS}` | False 33 | |`MQ_CLUSTER_PASSWORD` | `MQ_CLUSTER_PASSWORD` | A-MQ cluster admin password | `${MQ_CLUSTER_PASSWORD}` | True 34 | |`GITHUB_WEBHOOK_SECRET` | -- | GitHub trigger secret | secret101 | True 35 | |`GENERIC_WEBHOOK_SECRET` | -- | Generic build trigger secret | secret101 | True 36 | |`IMAGE_STREAM_NAMESPACE` | -- | Namespace in which the ImageStreams for Red Hat Middleware images are installed. These ImageStreams are normally installed in the openshift namespace. You should only need to modify this if you've installed the ImageStreams in a different namespace/project. | openshift | True 37 | |`JGROUPS_CLUSTER_PASSWORD` | `JGROUPS_CLUSTER_PASSWORD` | JGroups cluster password | `${JGROUPS_CLUSTER_PASSWORD}` | True 38 | |`AUTO_DEPLOY_EXPLODED` | `AUTO_DEPLOY_EXPLODED` | Controls whether exploded deployment content should be automatically deployed | false | False 39 | |`MAVEN_MIRROR_URL` | -- | Maven mirror to use for S2I builds | -- | False 40 | |`MAVEN_ARGS_APPEND` | -- | Maven additional arguments to use for S2I builds | -Dcom.redhat.xpaas.repo.jbossorg | False 41 | |`ARTIFACT_DIR` | -- | List of directories from which archives will be copied into the deployment folder. If unspecified, all archives in /target will be copied. | -- | False 42 | |`MEMORY_LIMIT` | -- | Container memory limit | 1Gi | False 43 | |======================================================================= 44 | 45 | 46 | 47 | == Objects 48 | 49 | The CLI supports various object types. A list of these object types as well as their abbreviations 50 | can be found in the https://docs.okd.io/latest/cli_reference/basic_cli_operations.html#object-types[OKD documentation]. 51 | 52 | 53 | === Services 54 | 55 | A service is an abstraction which defines a logical set of pods and a policy by which to access them. Refer to the 56 | https://docs.okd.io/latest/architecture/core_concepts/pods_and_services.html#services[OKD documentation] for more information. 57 | 58 | |============= 59 | |Service |Port |Name | Description 60 | 61 | .1+| `${APPLICATION_NAME}` 62 | |8080 | -- 63 | .1+| The web server's http port. 64 | .1+| `${APPLICATION_NAME}-ping` 65 | |8888 | ping 66 | .1+| The JGroups ping port for clustering. 67 | |============= 68 | 69 | 70 | 71 | === Routes 72 | 73 | A route is a way to expose a service by giving it an externally-reachable hostname such as `www.example.com`. A defined route and the endpoints 74 | identified by its service can be consumed by a router to provide named connectivity from external clients to your applications. Each route consists 75 | of a route name, service selector, and (optionally) security configuration. Refer to the 76 | https://docs.okd.io/latest/dev_guide/routes.html[OKD documentation] for more information. 77 | 78 | |============= 79 | | Service | Security | Hostname 80 | 81 | |`${APPLICATION_NAME}-http` | none | `${HOSTNAME_HTTP}` 82 | |============= 83 | 84 | 85 | 86 | === Build Configurations 87 | 88 | A `buildConfig` describes a single build definition and a set of triggers for when a new build should be created. 89 | A `buildConfig` is a REST object, which can be used in a POST to the API server to create a new instance. Refer to 90 | the https://docs.okd.io/latest/dev_guide/builds/index.html[OKD documentation] 91 | for more information. 92 | 93 | |============= 94 | | S2I image | link | Build output | BuildTriggers and Settings 95 | 96 | |jboss-eap71-openshift:1.3 | link:../../eap/eap-openshift{outfilesuffix}[`jboss-eap-7/eap71-openshift`] | `${APPLICATION_NAME}:latest` | GitHub, Generic, ImageChange, ConfigChange 97 | |============= 98 | 99 | 100 | === Deployment Configurations 101 | 102 | A deployment in OpenShift is a replication controller based on a user defined template called a deployment configuration. Deployments are created manually or in response to triggered events. 103 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/how_deployments_work.html#creating-a-deployment-configuration[OKD documentation] for more information. 104 | 105 | 106 | ==== Triggers 107 | 108 | A trigger drives the creation of new deployments in response to events, both inside and outside OpenShift. Refer to the 109 | https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#triggers[OKD documentation] for more information. 110 | 111 | |============ 112 | |Deployment | Triggers 113 | 114 | |`${APPLICATION_NAME}` | ImageChange 115 | |============ 116 | 117 | 118 | 119 | ==== Replicas 120 | 121 | A replication controller ensures that a specified number of pod "replicas" are running at any one time. 122 | If there are too many, the replication controller kills some pods. If there are too few, it starts more. 123 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#scaling[OKD documentation] 124 | for more information. 125 | 126 | |============ 127 | |Deployment | Replicas 128 | 129 | |`${APPLICATION_NAME}` | 1 130 | |============ 131 | 132 | 133 | ==== Pod Template 134 | 135 | 136 | 137 | 138 | ===== Image 139 | 140 | |============ 141 | |Deployment | Image 142 | 143 | |`${APPLICATION_NAME}` | `${APPLICATION_NAME}` 144 | |============ 145 | 146 | 147 | 148 | ===== Readiness Probe 149 | 150 | 151 | .${APPLICATION_NAME} 152 | ---- 153 | /bin/bash -c /opt/eap/bin/readinessProbe.sh 154 | ---- 155 | 156 | 157 | 158 | 159 | ===== Exposed Ports 160 | 161 | |============= 162 | |Deployments | Name | Port | Protocol 163 | 164 | .3+| `${APPLICATION_NAME}` 165 | |jolokia | 8778 | `TCP` 166 | |http | 8080 | `TCP` 167 | |ping | 8888 | `TCP` 168 | |============= 169 | 170 | 171 | 172 | ===== Image Environment Variables 173 | 174 | |======================================================================= 175 | |Deployment |Variable name |Description |Example value 176 | 177 | .8+| `${APPLICATION_NAME}` 178 | |`JGROUPS_PING_PROTOCOL` | -- | openshift.DNS_PING 179 | |`OPENSHIFT_DNS_PING_SERVICE_NAME` | -- | `${APPLICATION_NAME}-ping` 180 | |`OPENSHIFT_DNS_PING_SERVICE_PORT` | -- | 8888 181 | |`MQ_CLUSTER_PASSWORD` | A-MQ cluster admin password | `${MQ_CLUSTER_PASSWORD}` 182 | |`MQ_QUEUES` | Queue names | `${MQ_QUEUES}` 183 | |`MQ_TOPICS` | Topic names | `${MQ_TOPICS}` 184 | |`JGROUPS_CLUSTER_PASSWORD` | JGroups cluster password | `${JGROUPS_CLUSTER_PASSWORD}` 185 | |`AUTO_DEPLOY_EXPLODED` | Controls whether exploded deployment content should be automatically deployed | `${AUTO_DEPLOY_EXPLODED}` 186 | |======================================================================= 187 | 188 | 189 | 190 | 191 | === External Dependencies 192 | 193 | 194 | 195 | 196 | 197 | 198 | [[clustering]] 199 | ==== Clustering 200 | 201 | Clustering in OpenShift EAP is achieved through one of two discovery mechanisms: 202 | Kubernetes or DNS. This is done by configuring the JGroups protocol stack in 203 | standalone-openshift.xml with either the `` or `` 204 | elements. The templates are configured to use `DNS_PING`, however `KUBE_PING`is 205 | the default used by the image. 206 | 207 | The discovery mechanism used is specified by the `JGROUPS_PING_PROTOCOL` environment 208 | variable which can be set to either `openshift.DNS_PING` or `openshift.KUBE_PING`. 209 | `openshift.KUBE_PING` is the default used by the image if no value is specified 210 | for `JGROUPS_PING_PROTOCOL`. 211 | 212 | For DNS_PING to work, the following steps must be taken: 213 | 214 | . The `OPENSHIFT_DNS_PING_SERVICE_NAME` environment variable must be set to the 215 | name of the ping service for the cluster (see table above). If not set, the 216 | server will act as if it is a single-node cluster (a "cluster of one"). 217 | . The `OPENSHIFT_DNS_PING_SERVICE_PORT` environment variables should be set to 218 | the port number on which the ping service is exposed (see table above). The 219 | `DNS_PING` protocol will attempt to discern the port from the SRV records, if 220 | it can, otherwise it will default to 8888. 221 | . A ping service which exposes the ping port must be defined. This service 222 | should be "headless" (ClusterIP=None) and must have the following: 223 | .. The port must be named for port discovery to work. 224 | .. It must be annotated with `service.alpha.kubernetes.io/tolerate-unready-endpoints` 225 | set to `"true"`. Omitting this annotation will result in each node forming 226 | their own "cluster of one" during startup, then merging their cluster into 227 | the other nodes' clusters after startup (as the other nodes are not detected 228 | until after they have started). 229 | 230 | .Example ping service for use with DNS_PING 231 | [source,yaml] 232 | ---- 233 | kind: Service 234 | apiVersion: v1 235 | spec: 236 | clusterIP: None 237 | ports: 238 | - name: ping 239 | port: 8888 240 | selector: 241 | deploymentConfig: eap-app 242 | metadata: 243 | name: eap-app-ping 244 | annotations: 245 | service.alpha.kubernetes.io/tolerate-unready-endpoints: "true" 246 | description: "The JGroups ping port for clustering." 247 | ---- 248 | 249 | For `KUBE_PING` to work, the following steps must be taken: 250 | 251 | . The `OPENSHIFT_KUBE_PING_NAMESPACE` environment variable must be set (see table above). 252 | If not set, the server will act as if it is a single-node cluster (a "cluster of one"). 253 | . The `OPENSHIFT_KUBE_PING_LABELS` environment variables should be set (see table above). 254 | If not set, pods outside of your application (albeit in your namespace) will try to join. 255 | . Authorization must be granted to the service account the pod is running under to be 256 | allowed to access Kubernetes' REST api. This is done on the command line. 257 | 258 | .Policy commands 259 | ==== 260 | Using the default service account in the myproject namespace: 261 | .... 262 | oc policy add-role-to-user view system:serviceaccount:myproject:default -n myproject 263 | .... 264 | Using the eap-service-account in the myproject namespace: 265 | .... 266 | oc policy add-role-to-user view system:serviceaccount:myproject:eap-service-account -n myproject 267 | .... 268 | ==== 269 | 270 | 271 | -------------------------------------------------------------------------------- /docs/openjdk/openjdk18-web-basic-s2i.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = openjdk18-web-basic-s2i 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | An example Java application using OpenJDK 8. For more information about using this template, see https://github.com/jboss-openshift/application-templates. 13 | 14 | toc::[] 15 | 16 | 17 | == Parameters 18 | 19 | Templates allow you to define parameters which take on a value. That value is then substituted wherever the parameter is referenced. 20 | References can be defined in any text field in the objects list field. Refer to the 21 | https://docs.okd.io/latest/architecture/core_concepts/templates.html#parameters[OKD documentation] for more information. 22 | 23 | |======================================================================= 24 | |Variable name |Image Environment Variable |Description |Example value |Required 25 | 26 | |`APPLICATION_NAME` | -- | The name for the application. | openjdk-app | True 27 | |`HOSTNAME_HTTP` | -- | Custom hostname for http service route. Leave blank for default hostname, e.g.: -. | -- | False 28 | |`SOURCE_REPOSITORY_URL` | -- | Git source URI for application | https://github.com/jboss-openshift/openshift-quickstarts | True 29 | |`SOURCE_REPOSITORY_REF` | -- | Git branch/tag reference | master | False 30 | |`CONTEXT_DIR` | -- | Path within Git project to build; empty for root project directory. | undertow-servlet | False 31 | |`GITHUB_WEBHOOK_SECRET` | -- | GitHub trigger secret | secret101 | True 32 | |`GENERIC_WEBHOOK_SECRET` | -- | Generic build trigger secret | secret101 | True 33 | |`IMAGE_STREAM_NAMESPACE` | -- | Namespace in which the ImageStreams for Red Hat Middleware images are installed. These ImageStreams are normally installed in the openshift namespace. You should only need to modify this if you've installed the ImageStreams in a different namespace/project. | openshift | True 34 | |======================================================================= 35 | 36 | 37 | 38 | == Objects 39 | 40 | The CLI supports various object types. A list of these object types as well as their abbreviations 41 | can be found in the https://docs.okd.io/latest/cli_reference/basic_cli_operations.html#object-types[OKD documentation]. 42 | 43 | 44 | === Services 45 | 46 | A service is an abstraction which defines a logical set of pods and a policy by which to access them. Refer to the 47 | https://docs.okd.io/latest/architecture/core_concepts/pods_and_services.html#services[OKD documentation] for more information. 48 | 49 | |============= 50 | |Service |Port |Name | Description 51 | 52 | .1+| `${APPLICATION_NAME}` 53 | |8080 | -- 54 | .1+| The application's http port. 55 | |============= 56 | 57 | 58 | 59 | === Routes 60 | 61 | A route is a way to expose a service by giving it an externally-reachable hostname such as `www.example.com`. A defined route and the endpoints 62 | identified by its service can be consumed by a router to provide named connectivity from external clients to your applications. Each route consists 63 | of a route name, service selector, and (optionally) security configuration. Refer to the 64 | https://docs.okd.io/latest/dev_guide/routes.html[OKD documentation] for more information. 65 | 66 | |============= 67 | | Service | Security | Hostname 68 | 69 | |`${APPLICATION_NAME}-http` | none | `${HOSTNAME_HTTP}` 70 | |============= 71 | 72 | 73 | 74 | === Build Configurations 75 | 76 | A `buildConfig` describes a single build definition and a set of triggers for when a new build should be created. 77 | A `buildConfig` is a REST object, which can be used in a POST to the API server to create a new instance. Refer to 78 | the https://docs.okd.io/latest/dev_guide/builds/index.html[OKD documentation] 79 | for more information. 80 | 81 | |============= 82 | | S2I image | link | Build output | BuildTriggers and Settings 83 | 84 | |java:8 | link:../../openjdk/openjdk-openshift{outfilesuffix}[`redhat-openjdk-18/openjdk18-openshift`] | `${APPLICATION_NAME}:latest` | GitHub, Generic, ImageChange, ConfigChange 85 | |============= 86 | 87 | 88 | === Deployment Configurations 89 | 90 | A deployment in OpenShift is a replication controller based on a user defined template called a deployment configuration. Deployments are created manually or in response to triggered events. 91 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/how_deployments_work.html#creating-a-deployment-configuration[OKD documentation] for more information. 92 | 93 | 94 | ==== Triggers 95 | 96 | A trigger drives the creation of new deployments in response to events, both inside and outside OpenShift. Refer to the 97 | https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#triggers[OKD documentation] for more information. 98 | 99 | |============ 100 | |Deployment | Triggers 101 | 102 | |`${APPLICATION_NAME}` | ImageChange 103 | |============ 104 | 105 | 106 | 107 | ==== Replicas 108 | 109 | A replication controller ensures that a specified number of pod "replicas" are running at any one time. 110 | If there are too many, the replication controller kills some pods. If there are too few, it starts more. 111 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#scaling[OKD documentation] 112 | for more information. 113 | 114 | |============ 115 | |Deployment | Replicas 116 | 117 | |`${APPLICATION_NAME}` | 1 118 | |============ 119 | 120 | 121 | ==== Pod Template 122 | 123 | 124 | 125 | 126 | ===== Image 127 | 128 | |============ 129 | |Deployment | Image 130 | 131 | |`${APPLICATION_NAME}` | `${APPLICATION_NAME}` 132 | |============ 133 | 134 | 135 | 136 | ===== Readiness Probe 137 | 138 | 139 | 140 | 141 | 142 | ===== Exposed Ports 143 | 144 | |============= 145 | |Deployments | Name | Port | Protocol 146 | 147 | .3+| `${APPLICATION_NAME}` 148 | |jolokia | 8778 | `TCP` 149 | |http | 8080 | `TCP` 150 | |https | 8443 | `TCP` 151 | |============= 152 | 153 | 154 | 155 | ===== Image Environment Variables 156 | 157 | |======================================================================= 158 | |Deployment |Variable name |Description |Example value 159 | 160 | .0+| `${APPLICATION_NAME}` 161 | |======================================================================= 162 | 163 | 164 | 165 | 166 | === External Dependencies 167 | 168 | 169 | 170 | 171 | 172 | 173 | 174 | -------------------------------------------------------------------------------- /docs/secrets/amq-app-secret.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = amq-app-secret 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | Examples that can be installed into your project to allow you to test the A-MQ template. You should replace the contents with data that is more appropriate for your deployment. 13 | 14 | toc::[] 15 | 16 | 17 | 18 | 19 | -------------------------------------------------------------------------------- /docs/secrets/datagrid-app-secret.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = datagrid-app-secret 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | Examples that can be installed into your project to allow you to test the JDG template. You should replace the contents with data that is more appropriate for your deployment. 13 | 14 | toc::[] 15 | 16 | 17 | 18 | 19 | -------------------------------------------------------------------------------- /docs/secrets/datavirt-app-secret.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = datavirt-app-secret 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | Examples that can be installed into your project to allow you to test the JBoss Data Virtualization templates. You should replace the contents with data that is more appropriate for your deployment. 13 | 14 | toc::[] 15 | 16 | 17 | 18 | 19 | -------------------------------------------------------------------------------- /docs/secrets/eap-app-secret.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = eap-app-secret 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | Examples that can be installed into your project to allow you to test the EAP template. You should replace the contents with data that is more appropriate for your deployment. 13 | 14 | toc::[] 15 | 16 | 17 | 18 | 19 | -------------------------------------------------------------------------------- /docs/secrets/eap7-app-secret.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = eap7-app-secret 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | Examples that can be installed into your project to allow you to test the EAP7 template. You should replace the contents with data that is more appropriate for your deployment. 13 | 14 | toc::[] 15 | 16 | 17 | 18 | 19 | -------------------------------------------------------------------------------- /docs/secrets/jws-app-secret.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = jws-app-secret 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | Examples that can be installed into your project to allow you to test the JWS template. You should replace the contents with data that is more appropriate for your deployment. 13 | 14 | toc::[] 15 | 16 | 17 | 18 | 19 | -------------------------------------------------------------------------------- /docs/secrets/sso-app-secret.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = sso-secret 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | Examples that can be installed into your project to allow you to test the EAP template. You should replace the contents with data that is more appropriate for your deployment. 13 | 14 | toc::[] 15 | 16 | 17 | 18 | 19 | -------------------------------------------------------------------------------- /docs/sso/README.md: -------------------------------------------------------------------------------- 1 | # Documentation for Red Hat Single Sign-On 7.2 Application Templates 2 | 3 | Documentation for OpenShift v3 application templates which support applications based on Red Hat Single Sign-On 7.2 product was moved. The new location can be found [here](https://github.com/jboss-container-images/redhat-sso-7-openshift-image/tree/sso72-dev/docs). 4 | -------------------------------------------------------------------------------- /docs/webserver/jws31-tomcat7-basic-s2i.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = jws31-tomcat7-basic-s2i 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | Application template for JWS applications built using S2I. 13 | 14 | toc::[] 15 | 16 | 17 | == Parameters 18 | 19 | Templates allow you to define parameters which take on a value. That value is then substituted wherever the parameter is referenced. 20 | References can be defined in any text field in the objects list field. Refer to the 21 | https://docs.okd.io/latest/architecture/core_concepts/templates.html#parameters[OKD documentation] for more information. 22 | 23 | |======================================================================= 24 | |Variable name |Image Environment Variable |Description |Example value |Required 25 | 26 | |`APPLICATION_NAME` | -- | The name for the application. | jws-app | True 27 | |`HOSTNAME_HTTP` | -- | Custom hostname for http service route. Leave blank for default hostname, e.g.: -. | -- | False 28 | |`SOURCE_REPOSITORY_URL` | -- | Git source URI for application | https://github.com/jboss-openshift/openshift-quickstarts.git | True 29 | |`SOURCE_REPOSITORY_REF` | -- | Git branch/tag reference | 1.2 | False 30 | |`CONTEXT_DIR` | -- | Path within Git project to build; empty for root project directory. | tomcat-websocket-chat | False 31 | |`JWS_ADMIN_USERNAME` | `JWS_ADMIN_USERNAME` | JWS Admin User | `${JWS_ADMIN_USERNAME}` | True 32 | |`JWS_ADMIN_PASSWORD` | `JWS_ADMIN_PASSWORD` | JWS Admin Password | `${JWS_ADMIN_PASSWORD}` | True 33 | |`GITHUB_WEBHOOK_SECRET` | -- | GitHub trigger secret | secret101 | True 34 | |`GENERIC_WEBHOOK_SECRET` | -- | Generic build trigger secret | secret101 | True 35 | |`IMAGE_STREAM_NAMESPACE` | -- | Namespace in which the ImageStreams for Red Hat Middleware images are installed. These ImageStreams are normally installed in the openshift namespace. You should only need to modify this if you've installed the ImageStreams in a different namespace/project. | openshift | True 36 | |`MAVEN_MIRROR_URL` | -- | Maven mirror to use for S2I builds | -- | False 37 | |`ARTIFACT_DIR` | -- | List of directories from which archives will be copied into the deployment folder. If unspecified, all archives in /target will be copied. | -- | False 38 | |======================================================================= 39 | 40 | 41 | 42 | == Objects 43 | 44 | The CLI supports various object types. A list of these object types as well as their abbreviations 45 | can be found in the https://docs.okd.io/latest/cli_reference/basic_cli_operations.html#object-types[OKD documentation]. 46 | 47 | 48 | === Services 49 | 50 | A service is an abstraction which defines a logical set of pods and a policy by which to access them. Refer to the 51 | https://docs.okd.io/latest/architecture/core_concepts/pods_and_services.html#services[OKD documentation] for more information. 52 | 53 | |============= 54 | |Service |Port |Name | Description 55 | 56 | .1+| `${APPLICATION_NAME}` 57 | |8080 | -- 58 | .1+| The web server's http port. 59 | |============= 60 | 61 | 62 | 63 | === Routes 64 | 65 | A route is a way to expose a service by giving it an externally-reachable hostname such as `www.example.com`. A defined route and the endpoints 66 | identified by its service can be consumed by a router to provide named connectivity from external clients to your applications. Each route consists 67 | of a route name, service selector, and (optionally) security configuration. Refer to the 68 | https://docs.okd.io/latest/dev_guide/routes.html[OKD documentation] for more information. 69 | 70 | |============= 71 | | Service | Security | Hostname 72 | 73 | |`${APPLICATION_NAME}-http` | none | `${HOSTNAME_HTTP}` 74 | |============= 75 | 76 | 77 | 78 | === Build Configurations 79 | 80 | A `buildConfig` describes a single build definition and a set of triggers for when a new build should be created. 81 | A `buildConfig` is a REST object, which can be used in a POST to the API server to create a new instance. Refer to 82 | the https://docs.okd.io/latest/dev_guide/builds/index.html[OKD documentation] 83 | for more information. 84 | 85 | |============= 86 | | S2I image | link | Build output | BuildTriggers and Settings 87 | 88 | |jboss-webserver31-tomcat7-openshift:1.3 | link:../../webserver/tomcat7-openshift{outfilesuffix}[`jboss-webserver-3/webserver31-tomcat7-openshift`] | `${APPLICATION_NAME}:latest` | GitHub, Generic, ImageChange, ConfigChange 89 | |============= 90 | 91 | 92 | === Deployment Configurations 93 | 94 | A deployment in OpenShift is a replication controller based on a user defined template called a deployment configuration. Deployments are created manually or in response to triggered events. 95 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/how_deployments_work.html#creating-a-deployment-configuration[OKD documentation] for more information. 96 | 97 | 98 | ==== Triggers 99 | 100 | A trigger drives the creation of new deployments in response to events, both inside and outside OpenShift. Refer to the 101 | https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#triggers[OKD documentation] for more information. 102 | 103 | |============ 104 | |Deployment | Triggers 105 | 106 | |`${APPLICATION_NAME}` | ImageChange 107 | |============ 108 | 109 | 110 | 111 | ==== Replicas 112 | 113 | A replication controller ensures that a specified number of pod "replicas" are running at any one time. 114 | If there are too many, the replication controller kills some pods. If there are too few, it starts more. 115 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#scaling[OKD documentation] 116 | for more information. 117 | 118 | |============ 119 | |Deployment | Replicas 120 | 121 | |`${APPLICATION_NAME}` | 1 122 | |============ 123 | 124 | 125 | ==== Pod Template 126 | 127 | 128 | 129 | 130 | ===== Image 131 | 132 | |============ 133 | |Deployment | Image 134 | 135 | |`${APPLICATION_NAME}` | `${APPLICATION_NAME}` 136 | |============ 137 | 138 | 139 | 140 | ===== Readiness Probe 141 | 142 | 143 | .${APPLICATION_NAME} 144 | ---- 145 | /bin/bash -c curl --noproxy '*' -s -u ${JWS_ADMIN_USERNAME}:${JWS_ADMIN_PASSWORD} 'http://localhost:8080/manager/jmxproxy/?get=Catalina%3Atype%3DServer&att=stateName' |grep -iq 'stateName *= *STARTED' 146 | ---- 147 | 148 | 149 | 150 | 151 | ===== Exposed Ports 152 | 153 | |============= 154 | |Deployments | Name | Port | Protocol 155 | 156 | .2+| `${APPLICATION_NAME}` 157 | |jolokia | 8778 | `TCP` 158 | |http | 8080 | `TCP` 159 | |============= 160 | 161 | 162 | 163 | ===== Image Environment Variables 164 | 165 | |======================================================================= 166 | |Deployment |Variable name |Description |Example value 167 | 168 | .2+| `${APPLICATION_NAME}` 169 | |`JWS_ADMIN_USERNAME` | JWS Admin User | `${JWS_ADMIN_USERNAME}` 170 | |`JWS_ADMIN_PASSWORD` | JWS Admin Password | `${JWS_ADMIN_PASSWORD}` 171 | |======================================================================= 172 | 173 | 174 | 175 | 176 | === External Dependencies 177 | 178 | 179 | 180 | 181 | 182 | 183 | 184 | -------------------------------------------------------------------------------- /docs/webserver/jws31-tomcat7-https-s2i.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = jws31-tomcat7-https-s2i 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | An example JBoss Web Server application configured for use with https. For more information about using this template, see https://github.com/jboss-openshift/application-templates. 13 | 14 | toc::[] 15 | 16 | 17 | == Parameters 18 | 19 | Templates allow you to define parameters which take on a value. That value is then substituted wherever the parameter is referenced. 20 | References can be defined in any text field in the objects list field. Refer to the 21 | https://docs.okd.io/latest/architecture/core_concepts/templates.html#parameters[OKD documentation] for more information. 22 | 23 | |======================================================================= 24 | |Variable name |Image Environment Variable |Description |Example value |Required 25 | 26 | |`APPLICATION_NAME` | -- | The name for the application. | jws-app | True 27 | |`HOSTNAME_HTTP` | -- | Custom hostname for http service route. Leave blank for default hostname, e.g.: -. | -- | False 28 | |`HOSTNAME_HTTPS` | -- | Custom hostname for https service route. Leave blank for default hostname, e.g.: secure--. | -- | False 29 | |`SOURCE_REPOSITORY_URL` | -- | Git source URI for application | https://github.com/jboss-openshift/openshift-quickstarts.git | True 30 | |`SOURCE_REPOSITORY_REF` | -- | Git branch/tag reference | 1.2 | False 31 | |`CONTEXT_DIR` | -- | Path within Git project to build; empty for root project directory. | tomcat-websocket-chat | False 32 | |`JWS_HTTPS_SECRET` | -- | The name of the secret containing the certificate files | jws-app-secret | True 33 | |`JWS_HTTPS_CERTIFICATE` | `JWS_HTTPS_CERTIFICATE_DIR` | The name of the certificate file within the secret | server.crt | False 34 | |`JWS_HTTPS_CERTIFICATE_KEY` | `JWS_HTTPS_CERTIFICATE` | The name of the certificate key file within the secret | server.key | False 35 | |`JWS_HTTPS_CERTIFICATE_PASSWORD` | `JWS_HTTPS_CERTIFICATE` | The certificate password | `${JWS_HTTPS_CERTIFICATE}` | False 36 | |`JWS_ADMIN_USERNAME` | `JWS_ADMIN_USERNAME` | JWS Admin User | `${JWS_ADMIN_USERNAME}` | True 37 | |`JWS_ADMIN_PASSWORD` | `JWS_ADMIN_PASSWORD` | JWS Admin Password | `${JWS_ADMIN_PASSWORD}` | True 38 | |`GITHUB_WEBHOOK_SECRET` | -- | GitHub trigger secret | secret101 | True 39 | |`GENERIC_WEBHOOK_SECRET` | -- | Generic build trigger secret | secret101 | True 40 | |`IMAGE_STREAM_NAMESPACE` | -- | Namespace in which the ImageStreams for Red Hat Middleware images are installed. These ImageStreams are normally installed in the openshift namespace. You should only need to modify this if you've installed the ImageStreams in a different namespace/project. | openshift | True 41 | |`MAVEN_MIRROR_URL` | -- | Maven mirror to use for S2I builds | -- | False 42 | |`ARTIFACT_DIR` | -- | List of directories from which archives will be copied into the deployment folder. If unspecified, all archives in /target will be copied. | -- | False 43 | |======================================================================= 44 | 45 | 46 | 47 | == Objects 48 | 49 | The CLI supports various object types. A list of these object types as well as their abbreviations 50 | can be found in the https://docs.okd.io/latest/cli_reference/basic_cli_operations.html#object-types[OKD documentation]. 51 | 52 | 53 | === Services 54 | 55 | A service is an abstraction which defines a logical set of pods and a policy by which to access them. Refer to the 56 | https://docs.okd.io/latest/architecture/core_concepts/pods_and_services.html#services[OKD documentation] for more information. 57 | 58 | |============= 59 | |Service |Port |Name | Description 60 | 61 | .1+| `${APPLICATION_NAME}` 62 | |8080 | -- 63 | .1+| The web server's http port. 64 | .1+| `secure-${APPLICATION_NAME}` 65 | |8443 | -- 66 | .1+| The web server's https port. 67 | |============= 68 | 69 | 70 | 71 | === Routes 72 | 73 | A route is a way to expose a service by giving it an externally-reachable hostname such as `www.example.com`. A defined route and the endpoints 74 | identified by its service can be consumed by a router to provide named connectivity from external clients to your applications. Each route consists 75 | of a route name, service selector, and (optionally) security configuration. Refer to the 76 | https://docs.okd.io/latest/dev_guide/routes.html[OKD documentation] for more information. 77 | 78 | |============= 79 | | Service | Security | Hostname 80 | 81 | |`${APPLICATION_NAME}-http` | none | `${HOSTNAME_HTTP}` 82 | |`${APPLICATION_NAME}-https` | TLS passthrough | `${HOSTNAME_HTTPS}` 83 | |============= 84 | 85 | 86 | 87 | === Build Configurations 88 | 89 | A `buildConfig` describes a single build definition and a set of triggers for when a new build should be created. 90 | A `buildConfig` is a REST object, which can be used in a POST to the API server to create a new instance. Refer to 91 | the https://docs.okd.io/latest/dev_guide/builds/index.html[OKD documentation] 92 | for more information. 93 | 94 | |============= 95 | | S2I image | link | Build output | BuildTriggers and Settings 96 | 97 | |jboss-webserver31-tomcat7-openshift:1.3 | link:../../webserver/tomcat7-openshift{outfilesuffix}[`jboss-webserver-3/webserver31-tomcat7-openshift`] | `${APPLICATION_NAME}:latest` | GitHub, Generic, ImageChange, ConfigChange 98 | |============= 99 | 100 | 101 | === Deployment Configurations 102 | 103 | A deployment in OpenShift is a replication controller based on a user defined template called a deployment configuration. Deployments are created manually or in response to triggered events. 104 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/how_deployments_work.html#creating-a-deployment-configuration[OKD documentation] for more information. 105 | 106 | 107 | ==== Triggers 108 | 109 | A trigger drives the creation of new deployments in response to events, both inside and outside OpenShift. Refer to the 110 | https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#triggers[OKD documentation] for more information. 111 | 112 | |============ 113 | |Deployment | Triggers 114 | 115 | |`${APPLICATION_NAME}` | ImageChange 116 | |============ 117 | 118 | 119 | 120 | ==== Replicas 121 | 122 | A replication controller ensures that a specified number of pod "replicas" are running at any one time. 123 | If there are too many, the replication controller kills some pods. If there are too few, it starts more. 124 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#scaling[OKD documentation] 125 | for more information. 126 | 127 | |============ 128 | |Deployment | Replicas 129 | 130 | |`${APPLICATION_NAME}` | 1 131 | |============ 132 | 133 | 134 | ==== Pod Template 135 | 136 | 137 | 138 | 139 | ===== Image 140 | 141 | |============ 142 | |Deployment | Image 143 | 144 | |`${APPLICATION_NAME}` | `${APPLICATION_NAME}` 145 | |============ 146 | 147 | 148 | 149 | ===== Readiness Probe 150 | 151 | 152 | .${APPLICATION_NAME} 153 | ---- 154 | /bin/bash -c curl --noproxy '*' -s -u ${JWS_ADMIN_USERNAME}:${JWS_ADMIN_PASSWORD} 'http://localhost:8080/manager/jmxproxy/?get=Catalina%3Atype%3DServer&att=stateName' |grep -iq 'stateName *= *STARTED' 155 | ---- 156 | 157 | 158 | 159 | 160 | ===== Exposed Ports 161 | 162 | |============= 163 | |Deployments | Name | Port | Protocol 164 | 165 | .3+| `${APPLICATION_NAME}` 166 | |jolokia | 8778 | `TCP` 167 | |http | 8080 | `TCP` 168 | |https | 8443 | `TCP` 169 | |============= 170 | 171 | 172 | 173 | ===== Image Environment Variables 174 | 175 | |======================================================================= 176 | |Deployment |Variable name |Description |Example value 177 | 178 | .6+| `${APPLICATION_NAME}` 179 | |`JWS_HTTPS_CERTIFICATE_DIR` | The name of the certificate file within the secret | `/etc/jws-secret-volume` 180 | |`JWS_HTTPS_CERTIFICATE` | The name of the certificate file within the secret | `${JWS_HTTPS_CERTIFICATE}` 181 | |`JWS_HTTPS_CERTIFICATE_KEY` | The name of the certificate file within the secret | `${JWS_HTTPS_CERTIFICATE_KEY}` 182 | |`JWS_HTTPS_CERTIFICATE_PASSWORD` | The name of the certificate file within the secret | `${JWS_HTTPS_CERTIFICATE_PASSWORD}` 183 | |`JWS_ADMIN_USERNAME` | JWS Admin User | `${JWS_ADMIN_USERNAME}` 184 | |`JWS_ADMIN_PASSWORD` | JWS Admin Password | `${JWS_ADMIN_PASSWORD}` 185 | |======================================================================= 186 | 187 | 188 | 189 | ===== Volumes 190 | 191 | |============= 192 | |Deployment |Name | mountPath | Purpose | readOnly 193 | 194 | |`${APPLICATION_NAME}` | jws-certificate-volume | `/etc/jws-secret-volume` | ssl certs | True 195 | |============= 196 | 197 | 198 | === External Dependencies 199 | 200 | 201 | 202 | 203 | 204 | 205 | 206 | -------------------------------------------------------------------------------- /docs/webserver/jws31-tomcat8-basic-s2i.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = jws31-tomcat8-basic-s2i 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | An example JBoss Web Server application. For more information about using this template, see https://github.com/jboss-openshift/application-templates. 13 | 14 | toc::[] 15 | 16 | 17 | == Parameters 18 | 19 | Templates allow you to define parameters which take on a value. That value is then substituted wherever the parameter is referenced. 20 | References can be defined in any text field in the objects list field. Refer to the 21 | https://docs.okd.io/latest/architecture/core_concepts/templates.html#parameters[OKD documentation] for more information. 22 | 23 | |======================================================================= 24 | |Variable name |Image Environment Variable |Description |Example value |Required 25 | 26 | |`APPLICATION_NAME` | -- | The name for the application. | jws-app | True 27 | |`HOSTNAME_HTTP` | -- | Custom hostname for http service route. Leave blank for default hostname, e.g.: -. | -- | False 28 | |`SOURCE_REPOSITORY_URL` | -- | Git source URI for application | https://github.com/jboss-openshift/openshift-quickstarts.git | True 29 | |`SOURCE_REPOSITORY_REF` | -- | Git branch/tag reference | 1.2 | False 30 | |`CONTEXT_DIR` | -- | Path within Git project to build; empty for root project directory. | tomcat-websocket-chat | False 31 | |`JWS_ADMIN_USERNAME` | `JWS_ADMIN_USERNAME` | JWS Admin User | `${JWS_ADMIN_USERNAME}` | True 32 | |`JWS_ADMIN_PASSWORD` | `JWS_ADMIN_PASSWORD` | JWS Admin Password | `${JWS_ADMIN_PASSWORD}` | True 33 | |`GITHUB_WEBHOOK_SECRET` | -- | GitHub trigger secret | secret101 | True 34 | |`GENERIC_WEBHOOK_SECRET` | -- | Generic build trigger secret | secret101 | True 35 | |`IMAGE_STREAM_NAMESPACE` | -- | Namespace in which the ImageStreams for Red Hat Middleware images are installed. These ImageStreams are normally installed in the openshift namespace. You should only need to modify this if you've installed the ImageStreams in a different namespace/project. | openshift | True 36 | |`MAVEN_MIRROR_URL` | -- | Maven mirror to use for S2I builds | -- | False 37 | |`ARTIFACT_DIR` | -- | List of directories from which archives will be copied into the deployment folder. If unspecified, all archives in /target will be copied. | -- | False 38 | |======================================================================= 39 | 40 | 41 | 42 | == Objects 43 | 44 | The CLI supports various object types. A list of these object types as well as their abbreviations 45 | can be found in the https://docs.okd.io/latest/cli_reference/basic_cli_operations.html#object-types[OKD documentation]. 46 | 47 | 48 | === Services 49 | 50 | A service is an abstraction which defines a logical set of pods and a policy by which to access them. Refer to the 51 | https://docs.okd.io/latest/architecture/core_concepts/pods_and_services.html#services[OKD documentation] for more information. 52 | 53 | |============= 54 | |Service |Port |Name | Description 55 | 56 | .1+| `${APPLICATION_NAME}` 57 | |8080 | -- 58 | .1+| The web server's http port. 59 | |============= 60 | 61 | 62 | 63 | === Routes 64 | 65 | A route is a way to expose a service by giving it an externally-reachable hostname such as `www.example.com`. A defined route and the endpoints 66 | identified by its service can be consumed by a router to provide named connectivity from external clients to your applications. Each route consists 67 | of a route name, service selector, and (optionally) security configuration. Refer to the 68 | https://docs.okd.io/latest/dev_guide/routes.html[OKD documentation] for more information. 69 | 70 | |============= 71 | | Service | Security | Hostname 72 | 73 | |`${APPLICATION_NAME}-http` | none | `${HOSTNAME_HTTP}` 74 | |============= 75 | 76 | 77 | 78 | === Build Configurations 79 | 80 | A `buildConfig` describes a single build definition and a set of triggers for when a new build should be created. 81 | A `buildConfig` is a REST object, which can be used in a POST to the API server to create a new instance. Refer to 82 | the https://docs.okd.io/latest/dev_guide/builds/index.html[OKD documentation] 83 | for more information. 84 | 85 | |============= 86 | | S2I image | link | Build output | BuildTriggers and Settings 87 | 88 | |jboss-webserver31-tomcat8-openshift:1.3 | link:../../webserver/tomcat8-openshift{outfilesuffix}[`jboss-webserver-3/webserver31-tomcat8-openshift`] | `${APPLICATION_NAME}:latest` | GitHub, Generic, ImageChange, ConfigChange 89 | |============= 90 | 91 | 92 | === Deployment Configurations 93 | 94 | A deployment in OpenShift is a replication controller based on a user defined template called a deployment configuration. Deployments are created manually or in response to triggered events. 95 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/how_deployments_work.html#creating-a-deployment-configuration[OKD documentation] for more information. 96 | 97 | 98 | ==== Triggers 99 | 100 | A trigger drives the creation of new deployments in response to events, both inside and outside OpenShift. Refer to the 101 | https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#triggers[OKD documentation] for more information. 102 | 103 | |============ 104 | |Deployment | Triggers 105 | 106 | |`${APPLICATION_NAME}` | ImageChange 107 | |============ 108 | 109 | 110 | 111 | ==== Replicas 112 | 113 | A replication controller ensures that a specified number of pod "replicas" are running at any one time. 114 | If there are too many, the replication controller kills some pods. If there are too few, it starts more. 115 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#scaling[OKD documentation] 116 | for more information. 117 | 118 | |============ 119 | |Deployment | Replicas 120 | 121 | |`${APPLICATION_NAME}` | 1 122 | |============ 123 | 124 | 125 | ==== Pod Template 126 | 127 | 128 | 129 | 130 | ===== Image 131 | 132 | |============ 133 | |Deployment | Image 134 | 135 | |`${APPLICATION_NAME}` | `${APPLICATION_NAME}` 136 | |============ 137 | 138 | 139 | 140 | ===== Readiness Probe 141 | 142 | 143 | .${APPLICATION_NAME} 144 | ---- 145 | /bin/bash -c curl --noproxy '*' -s -u ${JWS_ADMIN_USERNAME}:${JWS_ADMIN_PASSWORD} 'http://localhost:8080/manager/jmxproxy/?get=Catalina%3Atype%3DServer&att=stateName' |grep -iq 'stateName *= *STARTED' 146 | ---- 147 | 148 | 149 | 150 | 151 | ===== Exposed Ports 152 | 153 | |============= 154 | |Deployments | Name | Port | Protocol 155 | 156 | .2+| `${APPLICATION_NAME}` 157 | |jolokia | 8778 | `TCP` 158 | |http | 8080 | `TCP` 159 | |============= 160 | 161 | 162 | 163 | ===== Image Environment Variables 164 | 165 | |======================================================================= 166 | |Deployment |Variable name |Description |Example value 167 | 168 | .2+| `${APPLICATION_NAME}` 169 | |`JWS_ADMIN_USERNAME` | JWS Admin User | `${JWS_ADMIN_USERNAME}` 170 | |`JWS_ADMIN_PASSWORD` | JWS Admin Password | `${JWS_ADMIN_PASSWORD}` 171 | |======================================================================= 172 | 173 | 174 | 175 | 176 | === External Dependencies 177 | 178 | 179 | 180 | 181 | 182 | 183 | 184 | -------------------------------------------------------------------------------- /docs/webserver/jws31-tomcat8-https-s2i.adoc: -------------------------------------------------------------------------------- 1 | //// 2 | AUTOGENERATED FILE - this file was generated via ./gen_template_docs.py. 3 | Changes to .adoc or HTML files may be overwritten! Please change the 4 | generator or the input template (./*.in) 5 | //// 6 | 7 | = jws31-tomcat8-https-s2i 8 | :toc: 9 | :toc-placement!: 10 | :toclevels: 5 11 | 12 | An example JBoss Web Server application. For more information about using this template, see https://github.com/jboss-openshift/application-templates. 13 | 14 | toc::[] 15 | 16 | 17 | == Parameters 18 | 19 | Templates allow you to define parameters which take on a value. That value is then substituted wherever the parameter is referenced. 20 | References can be defined in any text field in the objects list field. Refer to the 21 | https://docs.okd.io/latest/architecture/core_concepts/templates.html#parameters[OKD documentation] for more information. 22 | 23 | |======================================================================= 24 | |Variable name |Image Environment Variable |Description |Example value |Required 25 | 26 | |`APPLICATION_NAME` | -- | The name for the application. | jws-app | True 27 | |`HOSTNAME_HTTP` | -- | Custom hostname for http service route. Leave blank for default hostname, e.g.: -. | -- | False 28 | |`HOSTNAME_HTTPS` | -- | Custom hostname for https service route. Leave blank for default hostname, e.g.: secure--. | -- | False 29 | |`SOURCE_REPOSITORY_URL` | -- | Git source URI for application | https://github.com/jboss-openshift/openshift-quickstarts.git | True 30 | |`SOURCE_REPOSITORY_REF` | -- | Git branch/tag reference | 1.2 | False 31 | |`CONTEXT_DIR` | -- | Path within Git project to build; empty for root project directory. | tomcat-websocket-chat | False 32 | |`JWS_HTTPS_SECRET` | -- | The name of the secret containing the certificate files | jws-app-secret | True 33 | |`JWS_HTTPS_CERTIFICATE` | `JWS_HTTPS_CERTIFICATE_DIR` | The name of the certificate file within the secret | server.crt | False 34 | |`JWS_HTTPS_CERTIFICATE_KEY` | `JWS_HTTPS_CERTIFICATE` | The name of the certificate key file within the secret | server.key | False 35 | |`JWS_HTTPS_CERTIFICATE_PASSWORD` | `JWS_HTTPS_CERTIFICATE` | The certificate password | `${JWS_HTTPS_CERTIFICATE}` | False 36 | |`JWS_ADMIN_USERNAME` | `JWS_ADMIN_USERNAME` | JWS Admin User | `${JWS_ADMIN_USERNAME}` | True 37 | |`JWS_ADMIN_PASSWORD` | `JWS_ADMIN_PASSWORD` | JWS Admin Password | `${JWS_ADMIN_PASSWORD}` | True 38 | |`GITHUB_WEBHOOK_SECRET` | -- | GitHub trigger secret | secret101 | True 39 | |`GENERIC_WEBHOOK_SECRET` | -- | Generic build trigger secret | secret101 | True 40 | |`IMAGE_STREAM_NAMESPACE` | -- | Namespace in which the ImageStreams for Red Hat Middleware images are installed. These ImageStreams are normally installed in the openshift namespace. You should only need to modify this if you've installed the ImageStreams in a different namespace/project. | openshift | True 41 | |`MAVEN_MIRROR_URL` | -- | Maven mirror to use for S2I builds | -- | False 42 | |`ARTIFACT_DIR` | -- | List of directories from which archives will be copied into the deployment folder. If unspecified, all archives in /target will be copied. | -- | False 43 | |======================================================================= 44 | 45 | 46 | 47 | == Objects 48 | 49 | The CLI supports various object types. A list of these object types as well as their abbreviations 50 | can be found in the https://docs.okd.io/latest/cli_reference/basic_cli_operations.html#object-types[OKD documentation]. 51 | 52 | 53 | === Services 54 | 55 | A service is an abstraction which defines a logical set of pods and a policy by which to access them. Refer to the 56 | https://docs.okd.io/latest/architecture/core_concepts/pods_and_services.html#services[OKD documentation] for more information. 57 | 58 | |============= 59 | |Service |Port |Name | Description 60 | 61 | .1+| `${APPLICATION_NAME}` 62 | |8080 | -- 63 | .1+| The web server's http port. 64 | .1+| `secure-${APPLICATION_NAME}` 65 | |8443 | -- 66 | .1+| The web server's https port. 67 | |============= 68 | 69 | 70 | 71 | === Routes 72 | 73 | A route is a way to expose a service by giving it an externally-reachable hostname such as `www.example.com`. A defined route and the endpoints 74 | identified by its service can be consumed by a router to provide named connectivity from external clients to your applications. Each route consists 75 | of a route name, service selector, and (optionally) security configuration. Refer to the 76 | https://docs.okd.io/latest/dev_guide/routes.html[OKD documentation] for more information. 77 | 78 | |============= 79 | | Service | Security | Hostname 80 | 81 | |`${APPLICATION_NAME}-http` | none | `${HOSTNAME_HTTP}` 82 | |`${APPLICATION_NAME}-https` | TLS passthrough | `${HOSTNAME_HTTPS}` 83 | |============= 84 | 85 | 86 | 87 | === Build Configurations 88 | 89 | A `buildConfig` describes a single build definition and a set of triggers for when a new build should be created. 90 | A `buildConfig` is a REST object, which can be used in a POST to the API server to create a new instance. Refer to 91 | the https://docs.okd.io/latest/dev_guide/builds/index.html[OKD documentation] 92 | for more information. 93 | 94 | |============= 95 | | S2I image | link | Build output | BuildTriggers and Settings 96 | 97 | |jboss-webserver31-tomcat8-openshift:1.3 | link:../../webserver/tomcat8-openshift{outfilesuffix}[`jboss-webserver-3/webserver31-tomcat8-openshift`] | `${APPLICATION_NAME}:latest` | GitHub, Generic, ImageChange, ConfigChange 98 | |============= 99 | 100 | 101 | === Deployment Configurations 102 | 103 | A deployment in OpenShift is a replication controller based on a user defined template called a deployment configuration. Deployments are created manually or in response to triggered events. 104 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/how_deployments_work.html#creating-a-deployment-configuration[OKD documentation] for more information. 105 | 106 | 107 | ==== Triggers 108 | 109 | A trigger drives the creation of new deployments in response to events, both inside and outside OpenShift. Refer to the 110 | https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#triggers[OKD documentation] for more information. 111 | 112 | |============ 113 | |Deployment | Triggers 114 | 115 | |`${APPLICATION_NAME}` | ImageChange 116 | |============ 117 | 118 | 119 | 120 | ==== Replicas 121 | 122 | A replication controller ensures that a specified number of pod "replicas" are running at any one time. 123 | If there are too many, the replication controller kills some pods. If there are too few, it starts more. 124 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#scaling[OKD documentation] 125 | for more information. 126 | 127 | |============ 128 | |Deployment | Replicas 129 | 130 | |`${APPLICATION_NAME}` | 1 131 | |============ 132 | 133 | 134 | ==== Pod Template 135 | 136 | 137 | 138 | 139 | ===== Image 140 | 141 | |============ 142 | |Deployment | Image 143 | 144 | |`${APPLICATION_NAME}` | `${APPLICATION_NAME}` 145 | |============ 146 | 147 | 148 | 149 | ===== Readiness Probe 150 | 151 | 152 | .${APPLICATION_NAME} 153 | ---- 154 | /bin/bash -c curl --noproxy '*' -s -u ${JWS_ADMIN_USERNAME}:${JWS_ADMIN_PASSWORD} 'http://localhost:8080/manager/jmxproxy/?get=Catalina%3Atype%3DServer&att=stateName' |grep -iq 'stateName *= *STARTED' 155 | ---- 156 | 157 | 158 | 159 | 160 | ===== Exposed Ports 161 | 162 | |============= 163 | |Deployments | Name | Port | Protocol 164 | 165 | .3+| `${APPLICATION_NAME}` 166 | |jolokia | 8778 | `TCP` 167 | |http | 8080 | `TCP` 168 | |https | 8443 | `TCP` 169 | |============= 170 | 171 | 172 | 173 | ===== Image Environment Variables 174 | 175 | |======================================================================= 176 | |Deployment |Variable name |Description |Example value 177 | 178 | .6+| `${APPLICATION_NAME}` 179 | |`JWS_HTTPS_CERTIFICATE_DIR` | The name of the certificate file within the secret | `/etc/jws-secret-volume` 180 | |`JWS_HTTPS_CERTIFICATE` | The name of the certificate file within the secret | `${JWS_HTTPS_CERTIFICATE}` 181 | |`JWS_HTTPS_CERTIFICATE_KEY` | The name of the certificate file within the secret | `${JWS_HTTPS_CERTIFICATE_KEY}` 182 | |`JWS_HTTPS_CERTIFICATE_PASSWORD` | The name of the certificate file within the secret | `${JWS_HTTPS_CERTIFICATE_PASSWORD}` 183 | |`JWS_ADMIN_USERNAME` | JWS Admin User | `${JWS_ADMIN_USERNAME}` 184 | |`JWS_ADMIN_PASSWORD` | JWS Admin Password | `${JWS_ADMIN_PASSWORD}` 185 | |======================================================================= 186 | 187 | 188 | 189 | ===== Volumes 190 | 191 | |============= 192 | |Deployment |Name | mountPath | Purpose | readOnly 193 | 194 | |`${APPLICATION_NAME}` | jws-certificate-volume | `/etc/jws-secret-volume` | ssl certs | True 195 | |============= 196 | 197 | 198 | === External Dependencies 199 | 200 | 201 | 202 | 203 | 204 | 205 | 206 | -------------------------------------------------------------------------------- /eap/README_SSO.adoc: -------------------------------------------------------------------------------- 1 | [[application-templates]] 2 | Application Templates 3 | --------------------- 4 | 5 | This project contains OpenShift v3 application templates which support 6 | Red Hat SSO/Keycloak-enabled applications 7 | 8 | [[structure]] 9 | Structure 10 | ~~~~~~~~~ 11 | 12 | One template is provided: 13 | 14 | * eap64-sso-s2i.json: SSO/Keycloak-enabled EAP template 15 | 16 | Templates are configured with the following basic parameters in addition 17 | to the standard EAP parameters: 18 | 19 | * `SSO_URL`: URL of the SSO/Keycloak server 20 | * `SSO_REALM`: SSO/Keycloak realm for the deployed application(s) 21 | * `SSO_PUBLIC_KEY`: Public key of the SSO/Keycloak Realm. This field is 22 | optional but if omitted can leave the applications vulnerable to 23 | man-in-middle attacks 24 | * `SSO_USERNAME`: SSO/Keycloak User required to access the SSO/Keycloak 25 | REST API 26 | * `SSO_PASSWORD`: Password for SSO_USERNAME 27 | * `SSO_SAML_KEYSTORE_SECRET`: Secret to use for access to SAML keystore 28 | (defaults to sso-app-secret) 29 | * `SSO_SAML_KEYSTORE`: Keystore location for SAML (defaults to 30 | /etc/sso-saml-secret-volume/keystore.jks) 31 | * `SSO_SAML_KEYSTORE_PASSWORD`: Keystore password for SAML (defaults to 32 | mykeystorepass) 33 | * `SSO_SAML_CERTIFICATE_NAME`: Alias for keys/certificate to use for 34 | SAML (default to jboss) 35 | 36 | Upon startup, the image reads the deployment WAR's `web.xml` and looks for the 37 | `auth-method key`. If it's "KEYCLOAK", Open ID Connect is enabled. If it's 38 | "KEYCLOAK-SAML", SAML client registration and adapter configuration is 39 | performed. 40 | 41 | [[example]] 42 | Example 43 | ~~~~~~~ 44 | 45 | Once the SSO/Keycloak server has been instantiated (see sso/README) and 46 | configured with the appropriate Realm, Role(s), and User(s) ... 47 | 48 | * Create Realm (e.g demo) 49 | * Create Role that corresponds to JEE Role (e.g. user) 50 | * Create User with permanent password credential (e.g. 51 | mgmtuser/mgmtpass). Add all "realm-management" Roles. This User is used 52 | to automatically configure the SSO Clients in the SSO Server. 53 | * Create User with permanent password credential (e.g. 54 | demouser/demopass). Add Roles to User: JEE Role from #2. This User is 55 | used to authenticate access to user applications. 56 | 57 | Copy the Realm Public Key from the SSO/Keycloak console and use as the 58 | value of `SSO_PUBLIC_KEY` below. Set `SSO_URL` according to the location 59 | of the SSO server. 60 | 61 | .Create Secrets and SSO/Keycloak-enabled EAP in user (e.g. "myproject") project/namespace: 62 | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 63 | $ oc create -n myproject -f secrets/eap-app-secret.json 64 | $ oc create -n myproject -f secrets/sso-app-secret.json 65 | $ oc process -f eap/eap64-sso-s2i.json -v APPLICATION_NAME=helloworld,SOURCE_REPOSITORY_URL=https://github.com/keycloak/keycloak-examples,SOURCE_REPOSITORY_REF=0.4-openshift,CONTEXT_DIR=,SSO_URL=https://secure-sso-demo.hostname/auth,SSO_REALM=demo,SSO_USERNAME=mgmtuser,SSO_PASSWORD=mgmtpass,SSO_PUBLIC_KEY=XXX | oc create -n myproject -f - 66 | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 67 | 68 | After executing the above, you should be able to access the 69 | SSO/Keycloak-enabled applications at 70 | http://helloworld-myproject.hostname/app-context and 71 | https://secure-helloworld-myproject.hostname/app-context where 72 | app-context is app-jee, app-profile-jee, app-profile-jee-saml, or 73 | service depending on the example application. Note the app-html5 and 74 | app-profile-html5 example applications are not deployed or functional. 75 | -------------------------------------------------------------------------------- /eap/eap70-image-stream.json: -------------------------------------------------------------------------------- 1 | { 2 | "kind": "List", 3 | "apiVersion": "v1", 4 | "metadata": { 5 | "name": "eap70-image-stream", 6 | "annotations": { 7 | "description": "ImageStream definition for Red Hat JBoss EAP 7.0.", 8 | "openshift.io/provider-display-name": "Red Hat, Inc." 9 | } 10 | }, 11 | "items": [ 12 | { 13 | "kind": "ImageStream", 14 | "apiVersion": "v1", 15 | "metadata": { 16 | "name": "jboss-eap70-openshift", 17 | "annotations": { 18 | "openshift.io/display-name": "Red Hat JBoss EAP 7.0", 19 | "openshift.io/provider-display-name": "Red Hat, Inc.", 20 | "version": "1.4.18" 21 | } 22 | }, 23 | "labels": { 24 | "xpaas": "1.4.18" 25 | }, 26 | "spec": { 27 | "tags": [ 28 | { 29 | "name": "1.3", 30 | "annotations": { 31 | "description": "JBoss EAP 7.0 S2I images.", 32 | "iconClass": "icon-eap", 33 | "tags": "builder,eap,javaee,java,jboss,hidden", 34 | "supports": "eap:7.0,javaee:7,java:8", 35 | "sampleRepo": "https://github.com/jboss-developer/jboss-eap-quickstarts.git", 36 | "sampleContextDir": "kitchensink", 37 | "sampleRef": "7.0.0.GA", 38 | "version": "1.3", 39 | "openshift.io/display-name": "Red Hat JBoss EAP 7.0" 40 | }, 41 | "referencePolicy": { 42 | "type": "Local" 43 | }, 44 | "from": { 45 | "kind": "DockerImage", 46 | "name": "registry.redhat.io/jboss-eap-7/eap70-openshift:1.3" 47 | } 48 | }, 49 | { 50 | "name": "1.4", 51 | "annotations": { 52 | "description": "JBoss EAP 7.0 S2I images.", 53 | "iconClass": "icon-eap", 54 | "tags": "builder,eap,javaee,java,jboss,hidden", 55 | "supports": "eap:7.0,javaee:7,java:8", 56 | "sampleRepo": "https://github.com/jboss-developer/jboss-eap-quickstarts.git", 57 | "sampleContextDir": "kitchensink", 58 | "sampleRef": "7.0.0.GA", 59 | "version": "1.4", 60 | "openshift.io/display-name": "Red Hat JBoss EAP 7.0" 61 | }, 62 | "referencePolicy": { 63 | "type": "Local" 64 | }, 65 | "from": { 66 | "kind": "DockerImage", 67 | "name": "registry.redhat.io/jboss-eap-7/eap70-openshift:1.4" 68 | } 69 | }, 70 | { 71 | "name": "1.5", 72 | "annotations": { 73 | "description": "JBoss EAP 7.0 S2I images.", 74 | "iconClass": "icon-eap", 75 | "tags": "builder,eap,javaee,java,jboss,hidden", 76 | "supports": "eap:7.0,javaee:7,java:8", 77 | "sampleRepo": "https://github.com/jboss-developer/jboss-eap-quickstarts.git", 78 | "sampleContextDir": "kitchensink", 79 | "sampleRef": "7.0.0.GA", 80 | "version": "1.5", 81 | "openshift.io/display-name": "Red Hat JBoss EAP 7.0" 82 | }, 83 | "referencePolicy": { 84 | "type": "Local" 85 | }, 86 | "from": { 87 | "kind": "DockerImage", 88 | "name": "registry.redhat.io/jboss-eap-7/eap70-openshift:1.5" 89 | } 90 | }, 91 | { 92 | "name": "1.6", 93 | "annotations": { 94 | "description": "JBoss EAP 7.0 S2I images.", 95 | "iconClass": "icon-eap", 96 | "tags": "builder,eap,javaee,java,jboss,hidden", 97 | "supports": "eap:7.0,javaee:7,java:8", 98 | "sampleRepo": "https://github.com/jboss-developer/jboss-eap-quickstarts.git", 99 | "sampleContextDir": "kitchensink", 100 | "sampleRef": "7.0.0.GA", 101 | "version": "1.6", 102 | "openshift.io/display-name": "Red Hat JBoss EAP 7.0" 103 | }, 104 | "referencePolicy": { 105 | "type": "Local" 106 | }, 107 | "from": { 108 | "kind": "DockerImage", 109 | "name": "registry.redhat.io/jboss-eap-7/eap70-openshift:1.6" 110 | } 111 | }, 112 | { 113 | "name": "1.7", 114 | "annotations": { 115 | "description": "JBoss EAP 7.0 S2I images.", 116 | "iconClass": "icon-eap", 117 | "tags": "builder,eap,javaee,java,jboss,hidden", 118 | "supports": "eap:7.0,javaee:7,java:8", 119 | "sampleRepo": "https://github.com/jboss-developer/jboss-eap-quickstarts.git", 120 | "sampleContextDir": "kitchensink", 121 | "sampleRef": "7.0.0.GA", 122 | "version": "1.7", 123 | "openshift.io/display-name": "Red Hat JBoss EAP 7.0" 124 | }, 125 | "referencePolicy": { 126 | "type": "Local" 127 | }, 128 | "from": { 129 | "kind": "DockerImage", 130 | "name": "registry.redhat.io/jboss-eap-7/eap70-openshift:1.7" 131 | } 132 | } 133 | ] 134 | } 135 | } 136 | ] 137 | } 138 | -------------------------------------------------------------------------------- /eap/eap71-image-stream.json: -------------------------------------------------------------------------------- 1 | { 2 | "kind": "List", 3 | "apiVersion": "v1", 4 | "metadata": { 5 | "name": "eap71-image-stream", 6 | "annotations": { 7 | "description": "ImageStream definition for Red Hat JBoss EAP 7.1.", 8 | "openshift.io/provider-display-name": "Red Hat, Inc." 9 | } 10 | }, 11 | "items": [ 12 | { 13 | "kind": "ImageStream", 14 | "apiVersion": "v1", 15 | "metadata": { 16 | "name": "jboss-eap71-openshift", 17 | "annotations": { 18 | "openshift.io/display-name": "Red Hat JBoss EAP 7.1", 19 | "openshift.io/provider-display-name": "Red Hat, Inc.", 20 | "version": "1.4.18" 21 | } 22 | }, 23 | "labels": { 24 | "xpaas": "1.4.18" 25 | }, 26 | "spec": { 27 | "tags": [ 28 | { 29 | "name": "latest", 30 | "annotations": { 31 | "description": "JBoss EAP 7.1 S2I image (latest).", 32 | "iconClass": "icon-eap", 33 | "tags": "builder,eap,javaee,java,jboss,hidden", 34 | "supports": "eap:7.1,javaee:7,java:8", 35 | "sampleRepo": "https://github.com/jboss-developer/jboss-eap-quickstarts.git", 36 | "sampleContextDir": "kitchensink", 37 | "sampleRef": "7.1.0.GA", 38 | "version": "latest", 39 | "openshift.io/display-name": "Red Hat JBoss EAP 7.1" 40 | }, 41 | "referencePolicy": { 42 | "type": "Local" 43 | }, 44 | "from": { 45 | "kind": "DockerImage", 46 | "name": "registry.redhat.io/jboss-eap-7/eap71-openshift:latest" 47 | } 48 | }, 49 | { 50 | "name": "1.1", 51 | "annotations": { 52 | "description": "JBoss EAP 7.1 S2I image.", 53 | "iconClass": "icon-eap", 54 | "tags": "builder,eap,javaee,java,jboss,hidden", 55 | "supports": "eap:7.1,javaee:7,java:8", 56 | "sampleRepo": "https://github.com/jboss-developer/jboss-eap-quickstarts.git", 57 | "sampleContextDir": "kitchensink", 58 | "sampleRef": "7.1.0.GA", 59 | "version": "1.0", 60 | "openshift.io/display-name": "Red Hat JBoss EAP 7.1" 61 | }, 62 | "referencePolicy": { 63 | "type": "Local" 64 | }, 65 | "from": { 66 | "kind": "DockerImage", 67 | "name": "registry.redhat.io/jboss-eap-7/eap71-openshift:1.1" 68 | } 69 | }, 70 | { 71 | "name": "1.2", 72 | "annotations": { 73 | "description": "JBoss EAP 7.1 S2I image.", 74 | "iconClass": "icon-eap", 75 | "tags": "builder,eap,javaee,java,jboss,hidden", 76 | "supports": "eap:7.1,javaee:7,java:8", 77 | "sampleRepo": "https://github.com/jboss-developer/jboss-eap-quickstarts.git", 78 | "sampleContextDir": "kitchensink", 79 | "sampleRef": "7.1.0.GA", 80 | "version": "1.2", 81 | "openshift.io/display-name": "Red Hat JBoss EAP 7.1" 82 | }, 83 | "referencePolicy": { 84 | "type": "Local" 85 | }, 86 | "from": { 87 | "kind": "DockerImage", 88 | "name": "registry.redhat.io/jboss-eap-7/eap71-openshift:1.2" 89 | } 90 | }, 91 | { 92 | "name": "1.3", 93 | "annotations": { 94 | "description": "JBoss EAP 7.1 S2I image.", 95 | "iconClass": "icon-eap", 96 | "tags": "builder,eap,javaee,java,jboss,hidden", 97 | "supports": "eap:7.1,javaee:7,java:8", 98 | "sampleRepo": "https://github.com/jboss-developer/jboss-eap-quickstarts.git", 99 | "sampleContextDir": "kitchensink", 100 | "sampleRef": "7.1.0.GA", 101 | "version": "1.3", 102 | "openshift.io/display-name": "Red Hat JBoss EAP 7.1" 103 | }, 104 | "referencePolicy": { 105 | "type": "Local" 106 | }, 107 | "from": { 108 | "kind": "DockerImage", 109 | "name": "registry.redhat.io/jboss-eap-7/eap71-openshift:1.3" 110 | } 111 | }, 112 | { 113 | "name": "1.4", 114 | "annotations": { 115 | "description": "JBoss EAP 7.1 S2I image.", 116 | "iconClass": "icon-eap", 117 | "tags": "builder,eap,javaee,java,jboss,hidden", 118 | "supports": "eap:7.1,javaee:7,java:8", 119 | "sampleRepo": "https://github.com/jboss-developer/jboss-eap-quickstarts.git", 120 | "sampleContextDir": "kitchensink", 121 | "sampleRef": "7.1.0.GA", 122 | "version": "1.4", 123 | "openshift.io/display-name": "Red Hat JBoss EAP 7.1" 124 | }, 125 | "referencePolicy": { 126 | "type": "Local" 127 | }, 128 | "from": { 129 | "kind": "DockerImage", 130 | "name": "registry.redhat.io/jboss-eap-7/eap71-openshift:1.4" 131 | } 132 | } 133 | ] 134 | } 135 | } 136 | ] 137 | } 138 | -------------------------------------------------------------------------------- /openjdk/README.md: -------------------------------------------------------------------------------- 1 | These files have moved to the [OpenJDK Container Source Repository](https://github.com/jboss-container-images/openjdk) 2 | -------------------------------------------------------------------------------- /release-notes.adoc.in: -------------------------------------------------------------------------------- 1 | 2 | //// 3 | the source for the release notes part of this page is in the file 4 | ./release-notes.adoc.in 5 | //// 6 | 7 | == Release Notes 8 | 9 | === Relese 1.4.19 10 | * Red Hat JBoss BRMS Decision Server 6 streams, templates, secrets, and documentation were moved to dedicated link:https://github.com/jboss-container-images/jboss-decisionserver-6-openshift-image[Red Hat JBoss BRMS Decision Server 6 OpenShift container images] repository 11 | * Red Hat JBoss BPM Suite Intelligent Process Server 6 streams, templates, secrets, and documentation were moved to dedicated link:https://github.com/jboss-container-images/jboss-processserver-6-openshift-image[Red Hat JBoss BPM Suite Intelligent Process Server 6 OpenShift container images] repository 12 | 13 | === Relese 1.4.17 14 | * RH-SSO 7.2 templates and related documentation for these templates were moved to dedicated link:https://github.com/jboss-container-images/redhat-sso-7-openshift-image[Red Hat Single Sign-On 7 OpenShift container images] repository 15 | 16 | === Release 1.4.16 17 | * Changed image stream URLs from registry.access.redhat.com to registry.redhat.io 18 | * Removed JBoss Data Grid 6.5 resources 19 | * Removed Jboss Data Virtualization 6.3 resources 20 | 21 | === Release 1.4.10 22 | 23 | === Release 1.4.9 24 | * Add probes for DB pods 25 | * Update datavirt secret to use correct location for database files 26 | * Add support for SSO 7.2 27 | * Update EAP templates to reference AMQ 6.3, from 6.2 28 | * Split jboss-image-streams.json into separate files, e.g. eap/eap64-image-sream.json 29 | 30 | === Release 1.4.8 31 | * Update default volume capacity to 1G 32 | * Add emptyDir volumes for non-persistent databases 33 | * Add parameter for configuring memory limits (default 1G) 34 | * Move from KUBE_PING to DNS_PING for clustering in AMQ and EAP based products 35 | * Removed service accounts (DNS_PING requires no special privileges). 36 | * Added templates for automated TX recovery in EAP (tech-preview) 37 | 38 | === Release 1.4.7 39 | * Support clean shutdown on TERM for EAP 7.x based products 40 | * Remove JWS 3.0 templates 41 | * Remove BxMS 6.3 templates 42 | * Deprecate SSO 7.0 43 | * Add support for configuring queue memory limit (AMQ) 44 | 45 | === Release 1.4.5 46 | * Add support for JDG 7.1 47 | 48 | === Release 1.4.4 49 | * Add templates for AMQ message migration 50 | 51 | === Release 1.4.1 52 | * Update BxMS templates to reference AMQ 6.3, from 6.2 53 | 54 | === Release 1.4.0 55 | * Add parameter for specifying DB version 56 | 57 | === Release 1.3.7 58 | * Add client images for datavirt and datagrid 59 | 60 | === Release 1.3.6 61 | * Add support for Java S2I image 62 | 63 | === Release 1.3.5 64 | * Updated datavirt templates to reference new quickstart 65 | * Modified datavirt-app-secret to include secret for datasource configuration 66 | * datavirt-app-secret.json renamed datavirt-app-secret.yaml to improve readability 67 | 68 | === Release 1.3.4 69 | 70 | * New image definitions for: 71 | ** Red Hat JBoss Data Virtualization 6.3 72 | 73 | === Release 1.3.3 74 | 75 | * New image definitions for: 76 | ** Red Hat JBoss BPM Suite 6.3 intelligent process server 77 | ** Red Hat JBoss BRMS 6.3 decision server 78 | 79 | === Release 1.3.2 80 | 81 | * New image definitions for: 82 | ** EAP 6.4 83 | ** EAP 7 84 | ** Red Hat SS0 7 GA 85 | * Added support for configuring EAP timer service to use an external data source 86 | * Service account name is specified using a parameter in EAP and SSO templates 87 | * Added ability to deploy exploded archives 88 | 89 | === Release 1.3.1 90 | 91 | * New image definitions for: 92 | ** EAP 7 GA 93 | ** A-MQ 6 94 | * A-MQ persistent templates now support meshing. Use AMQ_SPLIT=true to use separate storage directories for each pod in a cluster. 95 | 96 | === Release 1.3.0 97 | 98 | * New image definitions for: 99 | ** Red Hat SSO 100 | ** EAP 7 Beta 101 | ** Red Hat SSO support in EAP 6.4 and 7 beta 102 | * Switch templates using deprecated key serviceAccount to serviceAccountName 103 | 104 | === Release 1.2.0 105 | * Added support for JBoss Data Grid 106 | * Added support for JBoss Decision Server 107 | * Added liveness probe to EAP templates 108 | * Encrypt JGroups communication (EAP based templates) 109 | * JMS physical names 110 | * Add Jolokia port to templates 111 | * Renamed APPLICATION_DOMAIN to HOSTNAME_HTTP and HOSTNAME_HTTPS to correspond to http and https routes 112 | 113 | === Release 1.1.0 114 | * Added terminationGracePeriodSeconds to pod templates 115 | * Renamed templates: 116 | ** Include product minor version in names (e.g. eap6-basic-s2i => eap64-basic-s2i) 117 | ** Replaced sti with s2i 118 | * Add ConfigChange trigger to DeploymentConfig in all templates 119 | * Set appropriate defaults so all templates can be instantiated as-is 120 | * Image names and tags have changed from product release to xPaaS release (e.g. jboss-eap-6/eap6-openshift:6.4 => jboss-eap-6/eap64-openshift:1.1) 121 | * ImageStream names have changed to include minor version in names (e.g. jboss-eap6-openshift => jboss-eap64-openshift) 122 | * Use Kubernetes to locate cluster nodes instead of DNS (e.g. KUBE_PING vs DNS_PING in JGroups configuration) 123 | * Add ConfigChange trigger to BuildConfig in all templates 124 | * Add forcePull=true to BuildConfig in all templates 125 | * Add required=true to all required parameters 126 | * Fix inconsistency in A-MQ templates, MQ_PROTOCOL and AMQ_TRANSPORTS 127 | * Modified route names to produce better default hostnames 128 | * Updated source parameter names to be consistent with other OpenShift templates (e.g. GIT_URI => SOURCE_REPOSITORY_URL) 129 | * Add missing mqtt+ssl port to A-MQ templates 130 | * Add parameter to select ImageStream namespace, defaulting to "openshift" 131 | 132 | === Release 1.0.2 133 | * Fix capitalization of GitHub trigger type 134 | 135 | === Release 1.0.1 136 | * Shorten port names 137 | * update deprecated items in BuildConfig 138 | 139 | === Release 1.0.0 140 | * Initial release with support for JBoss EAP, JBoss Web Server, and JBoss A-MQ 141 | -------------------------------------------------------------------------------- /secrets/amq-app-secret.json: -------------------------------------------------------------------------------- 1 | { 2 | "kind": "List", 3 | "apiVersion": "v1", 4 | "metadata": { 5 | "annotations": { 6 | "description": "Examples that can be installed into your project to allow you to test the A-MQ template. You should replace the contents with data that is more appropriate for your deployment." 7 | } 8 | }, 9 | "labels": { 10 | "template": "amq-app-secret" 11 | }, 12 | "items": [ 13 | { 14 | "kind": "Secret", 15 | "apiVersion": "v1", 16 | "metadata": { 17 | "annotations": { 18 | "description": "Default secret file containing A-MQ 'broker.ks' and 'broker.ts'. The password for the keystore is 'password' and the password for the truststore is 'password'" 19 | }, 20 | "name": "amq-app-secret" 21 | }, 22 | "data": { 23 | "broker.ks": "/u3+7QAAAAIAAAABAAAAAQAQYnJva2VyLWxvY2FsaG9zdAAAAVUVuc4XAAAFAzCCBP8wDgYKKwYBBAEqAhEBAQUABIIE64C6A2ZZAxBQdRDjTb7RvVB+LaO/BqpXf1bPqNrnjfEPXvUgWXLZwP/GeGDjMhDGkFyFIpLTxK2V9kp8Kv52MuCrV60PTc9BwbJIlmbVlOsmknaMENkrSvogPfS112WXIlVC4qVs9PAJwZZs1V3mPDM3E/PU8AouxMiHR0OEb3SRAWey4tWfDDbIsLGryXrA8PwvfgSuKEqaNMR1BFwSTVjP/Ss5T40ne+pArbIC80rS/XlBHkwebfErmD0UgInmheQlzKLcWu6C/d2hBH8NgdQiWYlJ0nRr2AB0W0Yf6kzuVm93z4trj90/rpF9iNTChZodrTlrKgoRUGzYoZ//0lZY+O+Qn9qbbjPbteKBFhiED2X5w8Stw1iuOER6HWbpqupTARj7NaWzTnnEGTAhFZvUspZpNkR5l6jztEEa4WzIrE9yQ0tBOKy+33oH1+HEoZtf0xkjBhHeHczRfyKxqfB+rO/0bxRzeK4SBR79KcZifGCzgGZhM2rQDeg9Uakdad+CkfeQGg4l9Qcu0c2Ao9sjqoLRrLMdEIJXJxYM/JAEbpDQr8QElWRGwddPAeCGUVQqlNObYmtoxdO7AcedXyE4tSlkqev8VSk/1ARXkToWerzZzVCFhfG+iMpnLCQNvBMmytcmZFUkPEEx68AHuZL35ZxAOxS9L6qBozjjArvaO49mKMX/4WlJgrmOZoP0YY4Zjea/+bGAQMJKUudJUF8azlJ4R+oqB3lR4DGrXLmTRFTPWbc/RL9lYbdO5IY+SxY/gIrJ2Z8fCUeB6MgTQ7mrc38yiFro5sn7kKtyEjdN7cTGmTStOO8Ef850z6K6KuYGmDf1HNycZRQmdiXHs6NcaG0JhVJwhv3iKn89MlOdpa/y6MaeUbtJHOxfKjSf/ng0RVr8+sXoBLiP14k6LWC0MSjp7AELLHewZE+R1DfH+Diq2IDd3C8/DF/2MP0rrC89BYo2kzapkQ5sxL7Zi6xUjlYa3uT27BdSaCsKBeCNtKB1t+sBOt1NtG4BEZY9u/KfTcKSRjxVLigPaRjHV+Rj8Gx56TbDtYESolwaIDfmfOoOoCRmURc2vvqsTuJxclcZO5YZUtUUKkTIvyZjct7bPUeyPi1A8HJgs66Qaj5DSjMv8+QJrY6SaxW2FDJCpM3q1kMqWFlBiKB37I/I75cYl8SYrXip+t0j1KCyY8jQ0mONRBc6r5v047UzsdL8sH7OVXsvbTQQyz3hWsfNQLCmVtsKoza7eoHj930lQc/X3ewE0BdbOLhU0QmTwHbg31pUxgXjeE+QTgd5b010ZVizbxBKpsYcPhvYcIq2YeirGlQ4teYhkn+K5T/LV52eYYZ07bYcgoUJswzOVM865xNF/5UDBY0zie/1tWWqNoc6Hf9UapG5+aJQAwxEV9eBv22SHATTJFq2EbbZp1+kFCupBjIOhEjfHOJJ8vCZBX+VphAEkfEXLYlZVafx3AbD5dklDsESiPdp8acD/qjBe8nvTswKohBthjjKc5GDB7mbdir8QUheFIIvaZLmhxvtdVB+eTIgqKGv1YYOA09nGy2UUeK2/6xhuNyqLT4B0H13H2zpese+7F00Yghb8ArRzG78cDxcdfEH4v2PauOD7CdWATPxb1WAas19nXyi5n1XF6Oo7wwdzPZ2qbvO05gSK7Ht6IT7/rIGJqc9AAAAAQAFWC41MDkAAAN9MIIDeTCCAmGgAwIBAgIEBlVblDANBgkqhkiG9w0BAQsFADBtMRAwDgYDVQQGEwdVbmtub3duMRAwDgYDVQQIEwdVbmtub3duMRAwDgYDVQQHEwdVbmtub3duMRAwDgYDVQQKEwdVbmtub3duMQ8wDQYDVQQLEwZicm9rZXIxEjAQBgNVBAMTCWxvY2FsaG9zdDAeFw0xNjA2MDMxMDA1NDNaFw0yNjA2MDExMDA1NDNaMG0xEDAOBgNVBAYTB1Vua25vd24xEDAOBgNVBAgTB1Vua25vd24xEDAOBgNVBAcTB1Vua25vd24xEDAOBgNVBAoTB1Vua25vd24xDzANBgNVBAsTBmJyb2tlcjESMBAGA1UEAxMJbG9jYWxob3N0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvp+LNiCZyL7QCOYkVry34CVIPgWNJtmu6FXDkqorCxWw86uLh1ngw0Jj7vzcVESeCRl9EDPm9kTdr8lN/UcuIsdUsq+oMl24sdQd9T/03K1+/7tTSqzlgZuN7cFgGd/XjZQpDxptte0PgaI30IrLrzH/5wVVAeRAzwEhgDzjq7klzXJ+Ajt7zNm3+mLVTsp7LQ8+oM7XzlCUfBvz0kTK4FGg4YBz5UBh07pmB1s3gENeo42bmCbelz1/iTAnUMh9rqUy9fHMhcTE1I3ZRT5XozTt+DqP0TmZGV67/LCbpfInwuB0zA6rO7T0Hy6x37IrDZc84U5ZCzSAGvwjje1PwwIDAQABoyEwHzAdBgNVHQ4EFgQUxzPy4ljc8y/CEgo0h3IlhO/2oIgwDQYJKoZIhvcNAQELBQADggEBAFLqQQ8g/ZTtvwa1NY+uvtZlmv8uNeYz+Ypm802X2MTrPJReZNkjfZQNONT6+0sjFUAG9GW/cG8/kA0Vka5L797OE6QlorcOTw6Sq2ZmwCprLMmpuNscN+9jkP3WAE2yxTFmQtnen507bCPSYzNbNMg0SGEOOwiP2d479RsSDwxzmpF4JGntIsfLtM+ju71vIDj6yM8FwMRCrvs091N2cfWkodkwQt+qpmMRFC7ZRFF8I/GcE773PgyEUb36pDkc7rHI5W0j5HmWd07dj0nfYxcUnTuv4YHRdW1L9Y4ZmPdw32qfkLAOzT2r3uFMKNSUb0DXicTNgyDwwuFHFLCWbZM2tnWoVSPHwE/FB48TF8zR9SuZOQ==", 24 | "broker.ts": "/u3+7QAAAAIAAAABAAAAAgAQYnJva2VyLWxvY2FsaG9zdAAAAVUVu3mCAAVYLjUwOQAAA30wggN5MIICYaADAgECAgQGVVuUMA0GCSqGSIb3DQEBCwUAMG0xEDAOBgNVBAYTB1Vua25vd24xEDAOBgNVBAgTB1Vua25vd24xEDAOBgNVBAcTB1Vua25vd24xEDAOBgNVBAoTB1Vua25vd24xDzANBgNVBAsTBmJyb2tlcjESMBAGA1UEAxMJbG9jYWxob3N0MB4XDTE2MDYwMzEwMDU0M1oXDTI2MDYwMTEwMDU0M1owbTEQMA4GA1UEBhMHVW5rbm93bjEQMA4GA1UECBMHVW5rbm93bjEQMA4GA1UEBxMHVW5rbm93bjEQMA4GA1UEChMHVW5rbm93bjEPMA0GA1UECxMGYnJva2VyMRIwEAYDVQQDEwlsb2NhbGhvc3QwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC+n4s2IJnIvtAI5iRWvLfgJUg+BY0m2a7oVcOSqisLFbDzq4uHWeDDQmPu/NxURJ4JGX0QM+b2RN2vyU39Ry4ix1Syr6gyXbix1B31P/TcrX7/u1NKrOWBm43twWAZ39eNlCkPGm217Q+BojfQisuvMf/nBVUB5EDPASGAPOOruSXNcn4CO3vM2bf6YtVOynstDz6gztfOUJR8G/PSRMrgUaDhgHPlQGHTumYHWzeAQ16jjZuYJt6XPX+JMCdQyH2upTL18cyFxMTUjdlFPlejNO34Oo/ROZkZXrv8sJul8ifC4HTMDqs7tPQfLrHfsisNlzzhTlkLNIAa/CON7U/DAgMBAAGjITAfMB0GA1UdDgQWBBTHM/LiWNzzL8ISCjSHciWE7/agiDANBgkqhkiG9w0BAQsFAAOCAQEAUupBDyD9lO2/BrU1j66+1mWa/y415jP5imbzTZfYxOs8lF5k2SN9lA041Pr7SyMVQAb0Zb9wbz+QDRWRrkvv3s4TpCWitw5PDpKrZmbAKmssyam42xw372OQ/dYATbLFMWZC2d6fnTtsI9JjM1s0yDRIYQ47CI/Z3jv1GxIPDHOakXgkae0ix8u0z6O7vW8gOPrIzwXAxEKu+zT3U3Zx9aSh2TBC36qmYxEULtlEUXwj8ZwTvvc+DIRRvfqkORzuscjlbSPkeZZ3Tt2PSd9jFxSdO6/hgdF1bUv1jhmY93Dfap+QsA7NPave4Uwo1JRvQNeJxM2DIPDC4UcUsJZtk+JHAUlQDRcPQSoLELpWtIbidpxJ" 25 | } 26 | } 27 | ] 28 | } 29 | -------------------------------------------------------------------------------- /secrets/datagrid-app-secret.json: -------------------------------------------------------------------------------- 1 | { 2 | "kind": "List", 3 | "apiVersion": "v1", 4 | "metadata": { 5 | "annotations": { 6 | "description": "Examples that can be installed into your project to allow you to test the JDG template. You should replace the contents with data that is more appropriate for your deployment." 7 | } 8 | }, 9 | "labels": { 10 | "template": "datagrid-app-secret" 11 | }, 12 | "items": [ 13 | { 14 | "kind": "Secret", 15 | "apiVersion": "v1", 16 | "metadata": { 17 | "annotations": { 18 | "description": "Default HTTPS keystore (keystore.jks) with name 'jboss' and password 'mykeystorepass' and JGoups keystore (jgroups.jceks) with name 'secret-key' and password 'password'" 19 | }, 20 | "name": "datagrid-app-secret" 21 | }, 22 | "data": { 23 | "keystore.jks": "/u3+7QAAAAIAAAABAAAAAQAFamJvc3MAAAFVFbYp5AAABQIwggT+MA4GCisGAQQBKgIRAQEFAASCBOqe/lTeehnds9ffJp/EYKY2K7o9CvvyvgiqvdaGqiZxwWjmoYBEuBxJBUkr7uyYr2g3Viui18djJh9paWdBfPRCEWsLxbMBmig+5OXe1U536PTNZlzkdrwSJpusiwwWLiog/kQ+Gp82VzHxsueNVkewKZ6LvdAq+5Pw7148cxgfnm+2j0La1YnX4/TAtY6A33HjU3HxPxpkLCBP66THxjJvm+n5xg+6eAPu6n/c3mWShhudf0k7FAHLgqMqZt22GMlIv73azdz5kf+opcF8nHN/SDnrgmBbX+GBFvMQ64a3zfLGMnCH8R7L2v5K0uH4AvOHHU9+g7KGk/obPOFyqjloPGIGwzyX4UhxsxP9+wU45RVg02SdoOsqsKYeF7JV1t+uj1+WXDkEaxGYx9u5bFIpkQOuuh6kyf6P6MK8gP6u8cRJeLU/LZCkNMSHq6afbgu/Uu0ZlPFKMLBiX6aKYO0nhp/h3QBzLOVCrWB5nnj90WnZ6Ug8bUjozTTKcdOu8oU47cOesSxPsZzs/KXEuqNP+T34fb4iOKjDXpTZDhIDYanfXb+GMHi/XdY5Q5Xu5w+6ES4ue9grlqfXtMa3G/FgUuJ6dLIXCDAHtS6nxvN3VBd3+pkQKG3iiBMbmBSg03bau5stsD8ol6NGQkoqIhvr1cxFHz+wVzh3UE6FOF+T96rqSuK17UNWnNTSFntHpMYUq+CbD1sTsAmaZ1tIbWBVYEw9G0hpzfFgIqndnEOJ2hD1Z30cStVvSamTlY1hYwxw9/qVUGxzRyQF1a4U8wuYyJNSLZmLwF4jmtkP/kvzhOJ9nr9ZHpuZcW8v5OuHpeTGb+bq+23T+1w0uK3x+O0TnZAFKN4UyZN6JWH2LI+jS+95sTt1fgV1gpY7/qtgX26BWPGQw6+ynRT68EREneUH7c8z3W8mkyfeOl+ffi3n4BYmkki6feSJNbkNdRncpFO83qIk3EtE9RNOMjU1ih8w+KrzZXm2LIINYqc6FkR+tACeGcJwPRkv7paGE3fI7JacYPrJsIf8C055NqbW1HFhplhY/zTbSuGH0SaseZ2lzkGVaVG8pzsNBlBX8eR4oL7LWAXhos1uJdg9cVIC2UZ+bBkBlUpEeWi7LryLL+Glg//iMp3W93nm+S6UJVUipVMgCMgHrXZjWQN0tGvPOxBUIM5IrxcrWsjEA0OJDsa0KCbI8R397FP3QZqB9hJPDs6Lb+64XGmkmAixLYLP2LczlmmoJ6pnGTdzqGjf/au1FzTq/Pikundn47Lt0ZsA9D5Wq958zr0U8Zc3X2OewAd/MKh7u5TOAJs870wHZPIjZss9lTwYJ1VfCP9/x4c8wfoas1mLrxoaTx4axIiTn8bMK60fq5s2DLpnDNgGS0g2tsyqw6+BPCKuwNj1dc5dl0fupIZxLB4+FeTcr7WaDslBl5QIyrM6ljknzd+r3U5ndtBiTBnFutD4+YFOcGPXm1qE7R/1Olmt+ZwnB8O7CtOGldTv/Imoa+en8YFT0TH9gPstso6ERJIP4UbIxxxJF+soqNVkK5fY0qRSksosJJJTKdD8BNl9skcPo8S9J7TRtcBsbPytU/1DhnL19D+bp0o5NRLAWse2sTOv3dSZiBPIAeL5oSaSBkJ9GbZcVc95d7ga3cNgbZuvcNPLov+F1WsEYYZcM/zjhvevAAAAAQAFWC41MDkAAAOBMIIDfTCCAmWgAwIBAgIEHPuEUDANBgkqhkiG9w0BAQsFADBvMQswCQYDVQQGEwJVUzEQMA4GA1UECBMHTXlTdGF0ZTEPMA0GA1UEBxMGTXlDaXR5MRcwFQYDVQQKEw5NeU9yZ2FuaXphdGlvbjESMBAGA1UECxMJTXlPcmdVbml0MRAwDgYDVQQDEwdFeGFtcGxlMB4XDTE2MDYwMzEwMDE0NVoXDTI2MDYwMTEwMDE0NVowbzELMAkGA1UEBhMCVVMxEDAOBgNVBAgTB015U3RhdGUxDzANBgNVBAcTBk15Q2l0eTEXMBUGA1UEChMOTXlPcmdhbml6YXRpb24xEjAQBgNVBAsTCU15T3JnVW5pdDEQMA4GA1UEAxMHRXhhbXBsZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL12YRIsnxFfnXSOLn8GtCWf0pJr/NzSFDV7M1I0nLlytu7dD/XAwvRTV6CFEvZJ8a4Q5NmKDkB1XofN7uebEhIANcizwtu61JXyic26kQB3IhK4nb5BChIgJbvfXg4IiazbWIHR6cAyRWT/M6rXVVUNDIPRZ84O7rng2vKvZezGHS9BbsoewyhF71fWTmvu2s7Dcm1sI6bRxJnF4BCQdMEc8dfPqjWCQUqkvkPN4wyHUzVlQE0/pbOW4YN668dBSmTGHTWaUvEXgX333gAlG07YcbJtjqJznurkCKLrGssX2ozGQg84GKg9+Sq+nwN5a09Rfhn4UBRGrJ4MpZDpKAkCAwEAAaMhMB8wHQYDVR0OBBYEFJMKA17Zl2R5M8pqpmdUWFEERulHMA0GCSqGSIb3DQEBCwUAA4IBAQCFJQeVl+7XD9Is6lGHPgOr8Ep8pSHwCBY+95C4I7KPYapXB+U9gi9bKvVElfDD+IMPfqg2hRuFCnW3MQId/6QU+/c7+fwOnqE0oi6xo8nl7qx48Y/Ih3jXo3q7JON6CfrJHMSw47+gYi8c66S6EOePi2aGySQNBwqop85kEUhDEl6eGAAEo66+BrCUjwPNK3R5mGtx38FM54OibLkmDMS8pFfBN7qQ1C35JUdFDDJcNEBZ1WGIbkLxyIFsogJa1x6j235Fst9MASxeu5+xO3/WVHcLHQAZqJ/xZadEJAg2+YkPEhsrIEoFhRr3Hg13ECqD1W6aSW5kE5wPoWjru1gNUXYHaE8+iikx9yyc8V8V4CG63qk=", 24 | "jgroups.jceks": "zs7OzgAAAAIAAAABAAAAAwAKc2VjcmV0LWtleQAAAVDQhuHmrO0ABXNyADNjb20uc3VuLmNyeXB0by5wcm92aWRlci5TZWFsZWRPYmplY3RGb3JLZXlQcm90ZWN0b3LNV8pZ5zC7UwIAAHhyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAJMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAN4cHVyAAJbQqzzF/gGCFTgAgAAeHAAAAAPMA0ECHcwLGK6EDyLAgEUdXEAfgAFAAAAmCu9wRKf1aYYUOEWe406ncPtIdm3147G7MJyWUu2kJVY15a2QxeZi9w5J3AF6T64CvylUuQjpcC4DWXwVn9BefntkBR8CzTiH7VxEqVOQ/OkFS29Inoq8t7/NBaTgTdmMkb4ETV1gIsy/+W6kk7QTqxItCkdKKGFE90Be/7yL3tG16TCy/ABKl7CO6PHa44CqK2PUE1oaJ+WdAAWUEJFV2l0aE1ENUFuZFRyaXBsZURFU3QAFlBCRVdpdGhNRDVBbmRUcmlwbGVERVMN658veJP01V2j9y8bQCYIzViutw==" 25 | } 26 | } 27 | ] 28 | } 29 | -------------------------------------------------------------------------------- /secrets/datavirt-app-secret.yaml: -------------------------------------------------------------------------------- 1 | kind: List 2 | apiVersion: v1 3 | metadata: 4 | annotations: 5 | description: Examples that can be installed into your project to allow you to test the JBoss Data Virtualization templates. You should replace the contents with data that is more appropriate for your deployment. 6 | labels: 7 | template: datavirt-app-secret 8 | items: 9 | 10 | - kind: Secret 11 | apiVersion: v1 12 | metadata: 13 | name: datavirt-app-secret 14 | annotations: 15 | description: Default HTTPS keystore (keystore.jks) with name 'jboss' and password 'mykeystorepass' and JGoups keystore (jgroups.jceks) with name 'secret-key' and password 'password' 16 | data: 17 | keystore.jks: /u3+7QAAAAIAAAABAAAAAQAFamJvc3MAAAFVFbYp5AAABQIwggT+MA4GCisGAQQBKgIRAQEFAASCBOqe/lTeehnds9ffJp/EYKY2K7o9CvvyvgiqvdaGqiZxwWjmoYBEuBxJBUkr7uyYr2g3Viui18djJh9paWdBfPRCEWsLxbMBmig+5OXe1U536PTNZlzkdrwSJpusiwwWLiog/kQ+Gp82VzHxsueNVkewKZ6LvdAq+5Pw7148cxgfnm+2j0La1YnX4/TAtY6A33HjU3HxPxpkLCBP66THxjJvm+n5xg+6eAPu6n/c3mWShhudf0k7FAHLgqMqZt22GMlIv73azdz5kf+opcF8nHN/SDnrgmBbX+GBFvMQ64a3zfLGMnCH8R7L2v5K0uH4AvOHHU9+g7KGk/obPOFyqjloPGIGwzyX4UhxsxP9+wU45RVg02SdoOsqsKYeF7JV1t+uj1+WXDkEaxGYx9u5bFIpkQOuuh6kyf6P6MK8gP6u8cRJeLU/LZCkNMSHq6afbgu/Uu0ZlPFKMLBiX6aKYO0nhp/h3QBzLOVCrWB5nnj90WnZ6Ug8bUjozTTKcdOu8oU47cOesSxPsZzs/KXEuqNP+T34fb4iOKjDXpTZDhIDYanfXb+GMHi/XdY5Q5Xu5w+6ES4ue9grlqfXtMa3G/FgUuJ6dLIXCDAHtS6nxvN3VBd3+pkQKG3iiBMbmBSg03bau5stsD8ol6NGQkoqIhvr1cxFHz+wVzh3UE6FOF+T96rqSuK17UNWnNTSFntHpMYUq+CbD1sTsAmaZ1tIbWBVYEw9G0hpzfFgIqndnEOJ2hD1Z30cStVvSamTlY1hYwxw9/qVUGxzRyQF1a4U8wuYyJNSLZmLwF4jmtkP/kvzhOJ9nr9ZHpuZcW8v5OuHpeTGb+bq+23T+1w0uK3x+O0TnZAFKN4UyZN6JWH2LI+jS+95sTt1fgV1gpY7/qtgX26BWPGQw6+ynRT68EREneUH7c8z3W8mkyfeOl+ffi3n4BYmkki6feSJNbkNdRncpFO83qIk3EtE9RNOMjU1ih8w+KrzZXm2LIINYqc6FkR+tACeGcJwPRkv7paGE3fI7JacYPrJsIf8C055NqbW1HFhplhY/zTbSuGH0SaseZ2lzkGVaVG8pzsNBlBX8eR4oL7LWAXhos1uJdg9cVIC2UZ+bBkBlUpEeWi7LryLL+Glg//iMp3W93nm+S6UJVUipVMgCMgHrXZjWQN0tGvPOxBUIM5IrxcrWsjEA0OJDsa0KCbI8R397FP3QZqB9hJPDs6Lb+64XGmkmAixLYLP2LczlmmoJ6pnGTdzqGjf/au1FzTq/Pikundn47Lt0ZsA9D5Wq958zr0U8Zc3X2OewAd/MKh7u5TOAJs870wHZPIjZss9lTwYJ1VfCP9/x4c8wfoas1mLrxoaTx4axIiTn8bMK60fq5s2DLpnDNgGS0g2tsyqw6+BPCKuwNj1dc5dl0fupIZxLB4+FeTcr7WaDslBl5QIyrM6ljknzd+r3U5ndtBiTBnFutD4+YFOcGPXm1qE7R/1Olmt+ZwnB8O7CtOGldTv/Imoa+en8YFT0TH9gPstso6ERJIP4UbIxxxJF+soqNVkK5fY0qRSksosJJJTKdD8BNl9skcPo8S9J7TRtcBsbPytU/1DhnL19D+bp0o5NRLAWse2sTOv3dSZiBPIAeL5oSaSBkJ9GbZcVc95d7ga3cNgbZuvcNPLov+F1WsEYYZcM/zjhvevAAAAAQAFWC41MDkAAAOBMIIDfTCCAmWgAwIBAgIEHPuEUDANBgkqhkiG9w0BAQsFADBvMQswCQYDVQQGEwJVUzEQMA4GA1UECBMHTXlTdGF0ZTEPMA0GA1UEBxMGTXlDaXR5MRcwFQYDVQQKEw5NeU9yZ2FuaXphdGlvbjESMBAGA1UECxMJTXlPcmdVbml0MRAwDgYDVQQDEwdFeGFtcGxlMB4XDTE2MDYwMzEwMDE0NVoXDTI2MDYwMTEwMDE0NVowbzELMAkGA1UEBhMCVVMxEDAOBgNVBAgTB015U3RhdGUxDzANBgNVBAcTBk15Q2l0eTEXMBUGA1UEChMOTXlPcmdhbml6YXRpb24xEjAQBgNVBAsTCU15T3JnVW5pdDEQMA4GA1UEAxMHRXhhbXBsZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL12YRIsnxFfnXSOLn8GtCWf0pJr/NzSFDV7M1I0nLlytu7dD/XAwvRTV6CFEvZJ8a4Q5NmKDkB1XofN7uebEhIANcizwtu61JXyic26kQB3IhK4nb5BChIgJbvfXg4IiazbWIHR6cAyRWT/M6rXVVUNDIPRZ84O7rng2vKvZezGHS9BbsoewyhF71fWTmvu2s7Dcm1sI6bRxJnF4BCQdMEc8dfPqjWCQUqkvkPN4wyHUzVlQE0/pbOW4YN668dBSmTGHTWaUvEXgX333gAlG07YcbJtjqJznurkCKLrGssX2ozGQg84GKg9+Sq+nwN5a09Rfhn4UBRGrJ4MpZDpKAkCAwEAAaMhMB8wHQYDVR0OBBYEFJMKA17Zl2R5M8pqpmdUWFEERulHMA0GCSqGSIb3DQEBCwUAA4IBAQCFJQeVl+7XD9Is6lGHPgOr8Ep8pSHwCBY+95C4I7KPYapXB+U9gi9bKvVElfDD+IMPfqg2hRuFCnW3MQId/6QU+/c7+fwOnqE0oi6xo8nl7qx48Y/Ih3jXo3q7JON6CfrJHMSw47+gYi8c66S6EOePi2aGySQNBwqop85kEUhDEl6eGAAEo66+BrCUjwPNK3R5mGtx38FM54OibLkmDMS8pFfBN7qQ1C35JUdFDDJcNEBZ1WGIbkLxyIFsogJa1x6j235Fst9MASxeu5+xO3/WVHcLHQAZqJ/xZadEJAg2+YkPEhsrIEoFhRr3Hg13ECqD1W6aSW5kE5wPoWjru1gNUXYHaE8+iikx9yyc8V8V4CG63qk= 18 | jgroups.jceks: zs7OzgAAAAIAAAABAAAAAwAKc2VjcmV0LWtleQAAAVDQhuHmrO0ABXNyADNjb20uc3VuLmNyeXB0by5wcm92aWRlci5TZWFsZWRPYmplY3RGb3JLZXlQcm90ZWN0b3LNV8pZ5zC7UwIAAHhyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAJMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAN4cHVyAAJbQqzzF/gGCFTgAgAAeHAAAAAPMA0ECHcwLGK6EDyLAgEUdXEAfgAFAAAAmCu9wRKf1aYYUOEWe406ncPtIdm3147G7MJyWUu2kJVY15a2QxeZi9w5J3AF6T64CvylUuQjpcC4DWXwVn9BefntkBR8CzTiH7VxEqVOQ/OkFS29Inoq8t7/NBaTgTdmMkb4ETV1gIsy/+W6kk7QTqxItCkdKKGFE90Be/7yL3tG16TCy/ABKl7CO6PHa44CqK2PUE1oaJ+WdAAWUEJFV2l0aE1ENUFuZFRyaXBsZURFU3QAFlBCRVdpdGhNRDVBbmRUcmlwbGVERVMN658veJP01V2j9y8bQCYIzViutw== 19 | 20 | - kind: Secret 21 | apiVersion: v1 22 | metadata: 23 | name: datavirt-app-config 24 | annotations: 25 | description: Datasource configuration for use with JDV h2 example. 26 | stringData: 27 | datasources.env: | 28 | # The type of DB the quickstart is using. This configures the translator used 29 | # by the VDB, as well as which datasource gets created. It is also used to 30 | # specify part of the datasource env prefix set on DATASOURCES. If QS_DB_TYPE 31 | # isn't specified, we'll use h2 (same as stock JDV quickstart). 32 | QS_DB_TYPE=${QS_DB_TYPE:-h2} 33 | 34 | # datasource definitions 35 | DATASOURCES=ACCOUNTS_${QS_DB_TYPE^^} 36 | 37 | # The "accounts" databases. 38 | # 39 | # h2 40 | ACCOUNTS_H2_DATABASE=accounts 41 | ACCOUNTS_H2_JNDI=java:/accounts-ds 42 | ACCOUNTS_H2_DRIVER=h2 43 | ACCOUNTS_H2_JTA=true 44 | ACCOUNTS_H2_NONXA=true 45 | ACCOUNTS_H2_USERNAME=sa 46 | ACCOUNTS_H2_PASSWORD=sa 47 | ACCOUNTS_H2_URL="jdbc:h2:/opt/eap/standalone/data/databases/h2/accounts" 48 | # required, but unused... 49 | ACCOUNTS_H2_SERVICE_HOST=dummy 50 | ACCOUNTS_H2_SERVICE_PORT=12345 51 | 52 | # derby 53 | ACCOUNTS_DERBY_DATABASE=accounts 54 | ACCOUNTS_DERBY_JNDI=java:/accounts-ds 55 | ACCOUNTS_DERBY_DRIVER=derby 56 | ACCOUNTS_DERBY_USERNAME=derby 57 | ACCOUNTS_DERBY_PASSWORD=derby 58 | ACCOUNTS_DERBY_TX_ISOLATION=TRANSACTION_READ_UNCOMMITTED 59 | ACCOUNTS_DERBY_JTA=true 60 | # Connection info for xa datasource 61 | ACCOUNTS_DERBY_XA_CONNECTION_PROPERTY_DatabaseName=/opt/eap/standalone/data/databases/derby/accounts 62 | # _HOST and _PORT are required, but not used 63 | ACCOUNTS_DERBY_SERVICE_HOST=dummy 64 | ACCOUNTS_DERBY_SERVICE_PORT=1527 65 | 66 | # postgresql 67 | # 68 | # Created from one of the PostgreSQL templates, e.g. postgresql-ephemeral, using 69 | # the following parameter settings: 70 | # 71 | # DATABASE_SERVICE_NAME=accounts-postgresql 72 | # POSTGRESQL_USER=pguser 73 | # POSTGRESQL_PASSWORD=pgpass 74 | # POSTGRESQL_DATABASE=accounts 75 | # 76 | # See the README.md in the postgresql folder for details on seeding the database. 77 | ACCOUNTS_POSTGRESQL_DATABASE=accounts 78 | ACCOUNTS_POSTGRESQL_JNDI=java:/accounts-ds 79 | ACCOUNTS_POSTGRESQL_DRIVER=postgresql 80 | ACCOUNTS_POSTGRESQL_USERNAME=pguser 81 | ACCOUNTS_POSTGRESQL_PASSWORD=pgpass 82 | ACCOUNTS_POSTGRESQL_TX_ISOLATION=TRANSACTION_READ_UNCOMMITTED 83 | ACCOUNTS_POSTGRESQL_JTA=true 84 | # ACCOUNTS_POSTGRESQL_SERVICE_HOST - injected by OpenShift 85 | # ACCOUNTS_POSTGRESQL_SERVICE_PORT - injected by OpenShift 86 | 87 | # mysql - note, the translator is set to mysql5. 88 | # 89 | # Created from one of the MySQL templates, e.g. mysql-ephemeral, using 90 | # the following parameter settings: 91 | # 92 | # DATABASE_SERVICE_NAME=accounts-mysql5 93 | # MYSQL_USER=myuser 94 | # MYSQL_PASSWORD=mypass 95 | # MYSQL_DATABASE=accounts 96 | # 97 | # See the README.md in the mysql folder for details on seeding the database. 98 | ACCOUNTS_MYSQL5_DATABASE=accounts 99 | ACCOUNTS_MYSQL5_JNDI=java:/accounts-ds 100 | ACCOUNTS_MYSQL5_DRIVER=mysql 101 | ACCOUNTS_MYSQL5_USERNAME=myuser 102 | ACCOUNTS_MYSQL5_PASSWORD=mypass 103 | ACCOUNTS_MYSQL5_TX_ISOLATION=TRANSACTION_READ_UNCOMMITTED 104 | ACCOUNTS_MYSQL5_JTA=true 105 | # ACCOUNTS_MYSQL5_SERVICE_HOST - injected by OpenShift 106 | # ACCOUNTS_MYSQL5_SERVICE_PORT - injected by OpenShift 107 | 108 | # resource adapters 109 | RESOURCE_ADAPTERS=MARKETDATA,EXCEL 110 | 111 | # Automatically add in the MAT_CACHE configuration, if we've included the 112 | # materialization VDB 113 | if [ -f "/deployments/jdg-remote-cache-mat-vdb.xml" ]; then 114 | RESOURCE_ADAPTERS=${RESOURCE_ADAPTERS},MAT_CACHE 115 | fi 116 | 117 | # The "market data" files. 118 | # 119 | MARKETDATA_ID=fileQS 120 | MARKETDATA_MODULE_ID=org.jboss.teiid.resource-adapter.file 121 | MARKETDATA_MODULE_SLOT=main 122 | MARKETDATA_CONNECTION_CLASS=org.teiid.resource.adapter.file.FileManagedConnectionFactory 123 | MARKETDATA_CONNECTION_JNDI=java:/marketdata-file 124 | MARKETDATA_PROPERTY_ParentDirectory='/opt/eap/standalone/data/teiidfiles/data' 125 | MARKETDATA_PROPERTY_AllowParentPaths=true 126 | 127 | # The "Excel" files. 128 | # 129 | EXCEL_ID=fileQSExcel 130 | EXCEL_MODULE_SLOT=main 131 | EXCEL_MODULE_ID=org.jboss.teiid.resource-adapter.file 132 | EXCEL_CONNECTION_CLASS=org.teiid.resource.adapter.file.FileManagedConnectionFactory 133 | EXCEL_CONNECTION_JNDI=java:/excel-file 134 | EXCEL_PROPERTY_ParentDirectory='/opt/eap/standalone/data/teiidfiles/excelFiles/' 135 | EXCEL_PROPERTY_AllowParentPaths=true 136 | 137 | # JDG configuration for materialization cache 138 | # 139 | # The following are required when using JDG as a datasource. 140 | MAT_CACHE_ID=infinispanRemQSDSL 141 | MAT_CACHE_MODULE_SLOT=main 142 | MAT_CACHE_MODULE_ID=org.jboss.teiid.resource-adapter.infinispan.dsl 143 | MAT_CACHE_CONNECTION_CLASS=org.teiid.resource.adapter.infinispan.dsl.InfinispanManagedConnectionFactory 144 | MAT_CACHE_CONNECTION_JNDI=java:/infinispanRemoteDSL 145 | MAT_CACHE_PROPERTY_CacheTypeMap="addressbook:org.jboss.as.quickstarts.datagrid.hotrod.query.domain.Person;id" 146 | MAT_CACHE_PROPERTY_ProtobufDefinitionFile=/quickstart/addressbook.proto 147 | MAT_CACHE_PROPERTY_MessageDescriptor=quickstart.Person 148 | MAT_CACHE_PROPERTY_Module=com.client.quickstart.addressbook.pojos 149 | MAT_CACHE_PROPERTY_MessageMarshallers=org.jboss.as.quickstarts.datagrid.hotrod.query.domain.Person:org.jboss.as.quickstarts.datagrid.hotrod.query.marshallers.PersonMarshaller,org.jboss.as.quickstarts.datagrid.hotrod.query.domain.PhoneNumber:org.jboss.as.quickstarts.datagrid.hotrod.query.marshallers.PhoneNumberMarshaller,org.jboss.as.quickstarts.datagrid.hotrod.query.domain.PhoneType:org.jboss.as.quickstarts.datagrid.hotrod.query.marshallers.PhoneTypeMarshaller 150 | MAT_CACHE_PROPERTY_RemoteServerList=${DATAGRID_APP_HOTROD_SERVICE_HOST}:${DATAGRID_APP_HOTROD_SERVICE_PORT} 151 | # Additionally, the following are required when using JDG to materialize views 152 | MAT_CACHE_PROPERTY_StagingCacheName=addressbook_staging 153 | MAT_CACHE_PROPERTY_AliasCacheName=addressbook_alias 154 | -------------------------------------------------------------------------------- /secrets/eap-app-secret.json: -------------------------------------------------------------------------------- 1 | { 2 | "kind": "List", 3 | "apiVersion": "v1", 4 | "metadata": { 5 | "annotations": { 6 | "description": "Examples that can be installed into your project to allow you to test the EAP template. You should replace the contents with data that is more appropriate for your deployment." 7 | } 8 | }, 9 | "labels": { 10 | "template": "eap-app-secret" 11 | }, 12 | "items": [ 13 | { 14 | "kind": "Secret", 15 | "apiVersion": "v1", 16 | "metadata": { 17 | "annotations": { 18 | "description": "Default HTTPS keystore (keystore.jks) with name 'jboss' and password 'mykeystorepass' and JGoups keystore (jgroups.jceks) with name 'secret-key' and password 'password'" 19 | }, 20 | "name": "eap-app-secret" 21 | }, 22 | "data": { 23 | "keystore.jks": "/u3+7QAAAAIAAAABAAAAAQAFamJvc3MAAAFVFbYp5AAABQIwggT+MA4GCisGAQQBKgIRAQEFAASCBOqe/lTeehnds9ffJp/EYKY2K7o9CvvyvgiqvdaGqiZxwWjmoYBEuBxJBUkr7uyYr2g3Viui18djJh9paWdBfPRCEWsLxbMBmig+5OXe1U536PTNZlzkdrwSJpusiwwWLiog/kQ+Gp82VzHxsueNVkewKZ6LvdAq+5Pw7148cxgfnm+2j0La1YnX4/TAtY6A33HjU3HxPxpkLCBP66THxjJvm+n5xg+6eAPu6n/c3mWShhudf0k7FAHLgqMqZt22GMlIv73azdz5kf+opcF8nHN/SDnrgmBbX+GBFvMQ64a3zfLGMnCH8R7L2v5K0uH4AvOHHU9+g7KGk/obPOFyqjloPGIGwzyX4UhxsxP9+wU45RVg02SdoOsqsKYeF7JV1t+uj1+WXDkEaxGYx9u5bFIpkQOuuh6kyf6P6MK8gP6u8cRJeLU/LZCkNMSHq6afbgu/Uu0ZlPFKMLBiX6aKYO0nhp/h3QBzLOVCrWB5nnj90WnZ6Ug8bUjozTTKcdOu8oU47cOesSxPsZzs/KXEuqNP+T34fb4iOKjDXpTZDhIDYanfXb+GMHi/XdY5Q5Xu5w+6ES4ue9grlqfXtMa3G/FgUuJ6dLIXCDAHtS6nxvN3VBd3+pkQKG3iiBMbmBSg03bau5stsD8ol6NGQkoqIhvr1cxFHz+wVzh3UE6FOF+T96rqSuK17UNWnNTSFntHpMYUq+CbD1sTsAmaZ1tIbWBVYEw9G0hpzfFgIqndnEOJ2hD1Z30cStVvSamTlY1hYwxw9/qVUGxzRyQF1a4U8wuYyJNSLZmLwF4jmtkP/kvzhOJ9nr9ZHpuZcW8v5OuHpeTGb+bq+23T+1w0uK3x+O0TnZAFKN4UyZN6JWH2LI+jS+95sTt1fgV1gpY7/qtgX26BWPGQw6+ynRT68EREneUH7c8z3W8mkyfeOl+ffi3n4BYmkki6feSJNbkNdRncpFO83qIk3EtE9RNOMjU1ih8w+KrzZXm2LIINYqc6FkR+tACeGcJwPRkv7paGE3fI7JacYPrJsIf8C055NqbW1HFhplhY/zTbSuGH0SaseZ2lzkGVaVG8pzsNBlBX8eR4oL7LWAXhos1uJdg9cVIC2UZ+bBkBlUpEeWi7LryLL+Glg//iMp3W93nm+S6UJVUipVMgCMgHrXZjWQN0tGvPOxBUIM5IrxcrWsjEA0OJDsa0KCbI8R397FP3QZqB9hJPDs6Lb+64XGmkmAixLYLP2LczlmmoJ6pnGTdzqGjf/au1FzTq/Pikundn47Lt0ZsA9D5Wq958zr0U8Zc3X2OewAd/MKh7u5TOAJs870wHZPIjZss9lTwYJ1VfCP9/x4c8wfoas1mLrxoaTx4axIiTn8bMK60fq5s2DLpnDNgGS0g2tsyqw6+BPCKuwNj1dc5dl0fupIZxLB4+FeTcr7WaDslBl5QIyrM6ljknzd+r3U5ndtBiTBnFutD4+YFOcGPXm1qE7R/1Olmt+ZwnB8O7CtOGldTv/Imoa+en8YFT0TH9gPstso6ERJIP4UbIxxxJF+soqNVkK5fY0qRSksosJJJTKdD8BNl9skcPo8S9J7TRtcBsbPytU/1DhnL19D+bp0o5NRLAWse2sTOv3dSZiBPIAeL5oSaSBkJ9GbZcVc95d7ga3cNgbZuvcNPLov+F1WsEYYZcM/zjhvevAAAAAQAFWC41MDkAAAOBMIIDfTCCAmWgAwIBAgIEHPuEUDANBgkqhkiG9w0BAQsFADBvMQswCQYDVQQGEwJVUzEQMA4GA1UECBMHTXlTdGF0ZTEPMA0GA1UEBxMGTXlDaXR5MRcwFQYDVQQKEw5NeU9yZ2FuaXphdGlvbjESMBAGA1UECxMJTXlPcmdVbml0MRAwDgYDVQQDEwdFeGFtcGxlMB4XDTE2MDYwMzEwMDE0NVoXDTI2MDYwMTEwMDE0NVowbzELMAkGA1UEBhMCVVMxEDAOBgNVBAgTB015U3RhdGUxDzANBgNVBAcTBk15Q2l0eTEXMBUGA1UEChMOTXlPcmdhbml6YXRpb24xEjAQBgNVBAsTCU15T3JnVW5pdDEQMA4GA1UEAxMHRXhhbXBsZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL12YRIsnxFfnXSOLn8GtCWf0pJr/NzSFDV7M1I0nLlytu7dD/XAwvRTV6CFEvZJ8a4Q5NmKDkB1XofN7uebEhIANcizwtu61JXyic26kQB3IhK4nb5BChIgJbvfXg4IiazbWIHR6cAyRWT/M6rXVVUNDIPRZ84O7rng2vKvZezGHS9BbsoewyhF71fWTmvu2s7Dcm1sI6bRxJnF4BCQdMEc8dfPqjWCQUqkvkPN4wyHUzVlQE0/pbOW4YN668dBSmTGHTWaUvEXgX333gAlG07YcbJtjqJznurkCKLrGssX2ozGQg84GKg9+Sq+nwN5a09Rfhn4UBRGrJ4MpZDpKAkCAwEAAaMhMB8wHQYDVR0OBBYEFJMKA17Zl2R5M8pqpmdUWFEERulHMA0GCSqGSIb3DQEBCwUAA4IBAQCFJQeVl+7XD9Is6lGHPgOr8Ep8pSHwCBY+95C4I7KPYapXB+U9gi9bKvVElfDD+IMPfqg2hRuFCnW3MQId/6QU+/c7+fwOnqE0oi6xo8nl7qx48Y/Ih3jXo3q7JON6CfrJHMSw47+gYi8c66S6EOePi2aGySQNBwqop85kEUhDEl6eGAAEo66+BrCUjwPNK3R5mGtx38FM54OibLkmDMS8pFfBN7qQ1C35JUdFDDJcNEBZ1WGIbkLxyIFsogJa1x6j235Fst9MASxeu5+xO3/WVHcLHQAZqJ/xZadEJAg2+YkPEhsrIEoFhRr3Hg13ECqD1W6aSW5kE5wPoWjru1gNUXYHaE8+iikx9yyc8V8V4CG63qk=", 24 | "jgroups.jceks": "zs7OzgAAAAIAAAABAAAAAwAKc2VjcmV0LWtleQAAAVDQhuHmrO0ABXNyADNjb20uc3VuLmNyeXB0by5wcm92aWRlci5TZWFsZWRPYmplY3RGb3JLZXlQcm90ZWN0b3LNV8pZ5zC7UwIAAHhyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAJMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAN4cHVyAAJbQqzzF/gGCFTgAgAAeHAAAAAPMA0ECHcwLGK6EDyLAgEUdXEAfgAFAAAAmCu9wRKf1aYYUOEWe406ncPtIdm3147G7MJyWUu2kJVY15a2QxeZi9w5J3AF6T64CvylUuQjpcC4DWXwVn9BefntkBR8CzTiH7VxEqVOQ/OkFS29Inoq8t7/NBaTgTdmMkb4ETV1gIsy/+W6kk7QTqxItCkdKKGFE90Be/7yL3tG16TCy/ABKl7CO6PHa44CqK2PUE1oaJ+WdAAWUEJFV2l0aE1ENUFuZFRyaXBsZURFU3QAFlBCRVdpdGhNRDVBbmRUcmlwbGVERVMN658veJP01V2j9y8bQCYIzViutw==" 25 | } 26 | } 27 | ] 28 | } 29 | -------------------------------------------------------------------------------- /secrets/eap7-app-secret.json: -------------------------------------------------------------------------------- 1 | { 2 | "kind": "List", 3 | "apiVersion": "v1", 4 | "metadata": { 5 | "annotations": { 6 | "description": "Examples that can be installed into your project to allow you to test the EAP7 template. You should replace the contents with data that is more appropriate for your deployment." 7 | } 8 | }, 9 | "labels": { 10 | "template": "eap7-app-secret" 11 | }, 12 | "items": [ 13 | { 14 | "kind": "Secret", 15 | "apiVersion": "v1", 16 | "metadata": { 17 | "annotations": { 18 | "description": "Default HTTPS keystore (keystore.jks) with name 'jboss' and password 'mykeystorepass' and JGoups keystore (jgroups.jceks) with name 'secret-key' and password 'password'" 19 | }, 20 | "name": "eap7-app-secret" 21 | }, 22 | "data": { 23 | "keystore.jks": "/u3+7QAAAAIAAAABAAAAAQAFamJvc3MAAAFVFbYp5AAABQIwggT+MA4GCisGAQQBKgIRAQEFAASCBOqe/lTeehnds9ffJp/EYKY2K7o9CvvyvgiqvdaGqiZxwWjmoYBEuBxJBUkr7uyYr2g3Viui18djJh9paWdBfPRCEWsLxbMBmig+5OXe1U536PTNZlzkdrwSJpusiwwWLiog/kQ+Gp82VzHxsueNVkewKZ6LvdAq+5Pw7148cxgfnm+2j0La1YnX4/TAtY6A33HjU3HxPxpkLCBP66THxjJvm+n5xg+6eAPu6n/c3mWShhudf0k7FAHLgqMqZt22GMlIv73azdz5kf+opcF8nHN/SDnrgmBbX+GBFvMQ64a3zfLGMnCH8R7L2v5K0uH4AvOHHU9+g7KGk/obPOFyqjloPGIGwzyX4UhxsxP9+wU45RVg02SdoOsqsKYeF7JV1t+uj1+WXDkEaxGYx9u5bFIpkQOuuh6kyf6P6MK8gP6u8cRJeLU/LZCkNMSHq6afbgu/Uu0ZlPFKMLBiX6aKYO0nhp/h3QBzLOVCrWB5nnj90WnZ6Ug8bUjozTTKcdOu8oU47cOesSxPsZzs/KXEuqNP+T34fb4iOKjDXpTZDhIDYanfXb+GMHi/XdY5Q5Xu5w+6ES4ue9grlqfXtMa3G/FgUuJ6dLIXCDAHtS6nxvN3VBd3+pkQKG3iiBMbmBSg03bau5stsD8ol6NGQkoqIhvr1cxFHz+wVzh3UE6FOF+T96rqSuK17UNWnNTSFntHpMYUq+CbD1sTsAmaZ1tIbWBVYEw9G0hpzfFgIqndnEOJ2hD1Z30cStVvSamTlY1hYwxw9/qVUGxzRyQF1a4U8wuYyJNSLZmLwF4jmtkP/kvzhOJ9nr9ZHpuZcW8v5OuHpeTGb+bq+23T+1w0uK3x+O0TnZAFKN4UyZN6JWH2LI+jS+95sTt1fgV1gpY7/qtgX26BWPGQw6+ynRT68EREneUH7c8z3W8mkyfeOl+ffi3n4BYmkki6feSJNbkNdRncpFO83qIk3EtE9RNOMjU1ih8w+KrzZXm2LIINYqc6FkR+tACeGcJwPRkv7paGE3fI7JacYPrJsIf8C055NqbW1HFhplhY/zTbSuGH0SaseZ2lzkGVaVG8pzsNBlBX8eR4oL7LWAXhos1uJdg9cVIC2UZ+bBkBlUpEeWi7LryLL+Glg//iMp3W93nm+S6UJVUipVMgCMgHrXZjWQN0tGvPOxBUIM5IrxcrWsjEA0OJDsa0KCbI8R397FP3QZqB9hJPDs6Lb+64XGmkmAixLYLP2LczlmmoJ6pnGTdzqGjf/au1FzTq/Pikundn47Lt0ZsA9D5Wq958zr0U8Zc3X2OewAd/MKh7u5TOAJs870wHZPIjZss9lTwYJ1VfCP9/x4c8wfoas1mLrxoaTx4axIiTn8bMK60fq5s2DLpnDNgGS0g2tsyqw6+BPCKuwNj1dc5dl0fupIZxLB4+FeTcr7WaDslBl5QIyrM6ljknzd+r3U5ndtBiTBnFutD4+YFOcGPXm1qE7R/1Olmt+ZwnB8O7CtOGldTv/Imoa+en8YFT0TH9gPstso6ERJIP4UbIxxxJF+soqNVkK5fY0qRSksosJJJTKdD8BNl9skcPo8S9J7TRtcBsbPytU/1DhnL19D+bp0o5NRLAWse2sTOv3dSZiBPIAeL5oSaSBkJ9GbZcVc95d7ga3cNgbZuvcNPLov+F1WsEYYZcM/zjhvevAAAAAQAFWC41MDkAAAOBMIIDfTCCAmWgAwIBAgIEHPuEUDANBgkqhkiG9w0BAQsFADBvMQswCQYDVQQGEwJVUzEQMA4GA1UECBMHTXlTdGF0ZTEPMA0GA1UEBxMGTXlDaXR5MRcwFQYDVQQKEw5NeU9yZ2FuaXphdGlvbjESMBAGA1UECxMJTXlPcmdVbml0MRAwDgYDVQQDEwdFeGFtcGxlMB4XDTE2MDYwMzEwMDE0NVoXDTI2MDYwMTEwMDE0NVowbzELMAkGA1UEBhMCVVMxEDAOBgNVBAgTB015U3RhdGUxDzANBgNVBAcTBk15Q2l0eTEXMBUGA1UEChMOTXlPcmdhbml6YXRpb24xEjAQBgNVBAsTCU15T3JnVW5pdDEQMA4GA1UEAxMHRXhhbXBsZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL12YRIsnxFfnXSOLn8GtCWf0pJr/NzSFDV7M1I0nLlytu7dD/XAwvRTV6CFEvZJ8a4Q5NmKDkB1XofN7uebEhIANcizwtu61JXyic26kQB3IhK4nb5BChIgJbvfXg4IiazbWIHR6cAyRWT/M6rXVVUNDIPRZ84O7rng2vKvZezGHS9BbsoewyhF71fWTmvu2s7Dcm1sI6bRxJnF4BCQdMEc8dfPqjWCQUqkvkPN4wyHUzVlQE0/pbOW4YN668dBSmTGHTWaUvEXgX333gAlG07YcbJtjqJznurkCKLrGssX2ozGQg84GKg9+Sq+nwN5a09Rfhn4UBRGrJ4MpZDpKAkCAwEAAaMhMB8wHQYDVR0OBBYEFJMKA17Zl2R5M8pqpmdUWFEERulHMA0GCSqGSIb3DQEBCwUAA4IBAQCFJQeVl+7XD9Is6lGHPgOr8Ep8pSHwCBY+95C4I7KPYapXB+U9gi9bKvVElfDD+IMPfqg2hRuFCnW3MQId/6QU+/c7+fwOnqE0oi6xo8nl7qx48Y/Ih3jXo3q7JON6CfrJHMSw47+gYi8c66S6EOePi2aGySQNBwqop85kEUhDEl6eGAAEo66+BrCUjwPNK3R5mGtx38FM54OibLkmDMS8pFfBN7qQ1C35JUdFDDJcNEBZ1WGIbkLxyIFsogJa1x6j235Fst9MASxeu5+xO3/WVHcLHQAZqJ/xZadEJAg2+YkPEhsrIEoFhRr3Hg13ECqD1W6aSW5kE5wPoWjru1gNUXYHaE8+iikx9yyc8V8V4CG63qk=", 24 | "jgroups.jceks": "zs7OzgAAAAIAAAABAAAAAwAKc2VjcmV0LWtleQAAAVDQhuHmrO0ABXNyADNjb20uc3VuLmNyeXB0by5wcm92aWRlci5TZWFsZWRPYmplY3RGb3JLZXlQcm90ZWN0b3LNV8pZ5zC7UwIAAHhyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAJMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAN4cHVyAAJbQqzzF/gGCFTgAgAAeHAAAAAPMA0ECHcwLGK6EDyLAgEUdXEAfgAFAAAAmCu9wRKf1aYYUOEWe406ncPtIdm3147G7MJyWUu2kJVY15a2QxeZi9w5J3AF6T64CvylUuQjpcC4DWXwVn9BefntkBR8CzTiH7VxEqVOQ/OkFS29Inoq8t7/NBaTgTdmMkb4ETV1gIsy/+W6kk7QTqxItCkdKKGFE90Be/7yL3tG16TCy/ABKl7CO6PHa44CqK2PUE1oaJ+WdAAWUEJFV2l0aE1ENUFuZFRyaXBsZURFU3QAFlBCRVdpdGhNRDVBbmRUcmlwbGVERVMN658veJP01V2j9y8bQCYIzViutw==" 25 | } 26 | } 27 | ] 28 | } 29 | -------------------------------------------------------------------------------- /secrets/jws-app-secret.json: -------------------------------------------------------------------------------- 1 | { 2 | "kind": "List", 3 | "apiVersion": "v1", 4 | "metadata": { 5 | "annotations": { 6 | "description": "Examples that can be installed into your project to allow you to test the JWS template. You should replace the contents with data that is more appropriate for your deployment." 7 | } 8 | }, 9 | "labels": { 10 | "template": "jws-app-secret" 11 | }, 12 | "items": [ 13 | { 14 | "kind": "Secret", 15 | "apiVersion": "v1", 16 | "metadata": { 17 | "annotations": { 18 | "description": "Default server certificate 'server.crt' and private key 'server.key' with no certificate password" 19 | }, 20 | "name": "jws-app-secret" 21 | }, 22 | "data": { 23 | "server.crt": "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSURhakNDQWxLZ0F3SUJBZ0lKQUlTd2g5UGtlUUhNTUEwR0NTcUdTSWIzRFFFQkJRVUFNQ3d4Q3pBSkJnTlYKQkFZVEFrTkJNUXN3Q1FZRFZRUUlFd0pDUXpFUU1BNEdBMVVFQ2hNSFVtVmtJRWhoZERBZUZ3MHhOVEE1TVRZeQpNRFEzTXpSYUZ3MHhPREE1TVRVeU1EUTNNelJhTUN3eEN6QUpCZ05WQkFZVEFrTkJNUXN3Q1FZRFZRUUlFd0pDClF6RVFNQTRHQTFVRUNoTUhVbVZrSUVoaGREQ0NBU0l3RFFZSktvWklodmNOQVFFQkJRQURnZ0VQQURDQ0FRb0MKZ2dFQkFLVWRnNFhkSXhONVBFQlZGOG1GcXZCZk12Z3JaOXEveVJLZnNNdGVIdjdPNjJsdVNFSmhyalFCNnRULwpxODkxL3FnbnYvN2RuamlBek5udU5OeVFmMHIzTTNjV3dkRzhLY0pQUmVzcmF3TUZUaVo3KzRnTUlSa3lsOUZkCno4Z05rYktWOTBjQjZteWpNZ2hkTVY0aGh4K0Y4VHA5dGh2ek5kVmcrNHpPQkNTUkdkYWNHTFoxbzJadjZzVjMKb2tqSzRLNVBuVllFR0R3ODFoeE5NRnVGMXAwN1ViQjlVQitadjI0SmUxTXpFWWxtbmZiTSsybVNoSXNxWlJrUgp3NTErUVJnWDlrNXQzL0I3MzZ2QUdZU3BuUktnc3ZPQUFpdmY4NnQ4MWVFSExFY3NnQjZUWUwyamJoVW1yVGFPCmpDcS9RZ1lIbzdVdnlSVTNrRTg2bWlFdW5ia0NBd0VBQWFPQmpqQ0JpekFkQmdOVkhRNEVGZ1FVL2V4QlppRGYKaU9ISHhscmczZzdPMkYvelU4Y3dYQVlEVlIwakJGVXdVNEFVL2V4QlppRGZpT0hIeGxyZzNnN08yRi96VThlaApNS1F1TUN3eEN6QUpCZ05WQkFZVEFrTkJNUXN3Q1FZRFZRUUlFd0pDUXpFUU1BNEdBMVVFQ2hNSFVtVmtJRWhoCmRJSUpBSVN3aDlQa2VRSE1NQXdHQTFVZEV3UUZNQU1CQWY4d0RRWUpLb1pJaHZjTkFRRUZCUUFEZ2dFQkFIbm8KUU1aeXYzTEQzNi9WV1JOOHMyYm5ZVzN2N3Y5YUNJNUNBbyswQklsZExyaTNVWlR3M0NQaVdpbHVwTUxweENQZQpVbGF0RHJ3Nkx2NVdRajlyN3EzR0tHQW1ZS3hva2VKMmZuL2wweVF2R1grVkRKZW9kTWgyZXl3YW1yLytjdjllCnhWOGtpeWozVFNSNC9hUWgwUUxlUytaMjhoanp3bFBiVkxpTW90L083R3dmM042WDhtWGs5ODczK3psT1FPZncKN0NQeEl4SStYNnNmMlkvOXlkV05jdWdnYStkK3JOam5Rd1ViZ1hWUytxWjZGc1FjQk8wMm5WbDBSMmFDS3pMUQpWd0tXZUJLRlN6Q2lKKy9lUmlaREQ2VHh3K3B1WERVR1hjNWR0TE5leEhrR1dmdUx5T1hmNzNvbEgzTVRsZW8wClcxZzJVeEVJdXRuWU5qQWpwT1E9Ci0tLS0tRU5EIENFUlRJRklDQVRFLS0tLS0K", 24 | "server.key": "LS0tLS1CRUdJTiBSU0EgUFJJVkFURSBLRVktLS0tLQpNSUlFb3dJQkFBS0NBUUVBcFIyRGhkMGpFM2s4UUZVWHlZV3E4Rjh5K0N0bjJyL0pFcCt3eTE0ZS9zN3JhVzVJClFtR3VOQUhxMVArcnozWCtxQ2UvL3QyZU9JRE0yZTQwM0pCL1N2Y3pkeGJCMGJ3cHdrOUY2eXRyQXdWT0pudjcKaUF3aEdUS1gwVjNQeUEyUnNwWDNSd0hxYktNeUNGMHhYaUdISDRYeE9uMjJHL00xMVdEN2pNNEVKSkVaMXB3WQp0bldqWm0vcXhYZWlTTXJncmsrZFZnUVlQRHpXSEUwd1c0WFduVHRSc0gxUUg1bS9iZ2w3VXpNUmlXYWQ5c3o3CmFaS0VpeXBsR1JIRG5YNUJHQmYyVG0zZjhIdmZxOEFaaEttZEVxQ3k4NEFDSzkvenEzelY0UWNzUnl5QUhwTmcKdmFOdUZTYXRObzZNS3I5Q0JnZWp0Uy9KRlRlUVR6cWFJUzZkdVFJREFRQUJBb0lCQUJ4ZnJBQk85ZjRjc1V2awowNGVmM3JZYnhlaDduUWNzT2VObmFid28ybTZ6SkNVai9HcmIybEc1bXA4cnFGeW9URENkVkJMNkJueHpOY0NsCmZKUUNpTDFiS1k3bmJEc2NlSmlaZ3N4YzA3RGJNb2pPZVhUeGtLYUIyVER6VEFkMnZYalE2SU5kUXVtVVNiN0MKTlArV0IyQlZaaFRGRVl4UUNRbzM5a0pHRE5RempFL0NQSXl3UVVIYXJkYmMra1F4cVRlSGt3endXWjZGV0UweApDb1hiWHR5U2pxYThTQzRxVFZOZHNTNWt4RzR3VjdudUlkWVBOeGd2eEZkR0NJR2Nid09kakd6eDB6cjNmWC83ClQxaEdUL0FOQnpqWlZnSWFUMHNSYUFsdWl1WGdRNjNvMzJWWXYrMG5qU0JaVVNleW9EZWttUEdLZko0S0hSUGsKNmNTUDRoa0NnWUVBMnFFejVoSnJPaW1sOWkrWDFjMTdyVzlvZFU4aHUvaVhxMnJkK2N1eW8rdUpZR20yZ0RNRwpNR2JDMlpyMTREd2FjLzU0V0VZeFBOTy9UK0laUWNiTUxoNU8vTnowcTJRUWdxOUw4TkY0MkRzcE5oQ0s5THYvCmRLcEVNR2RzRUY4cEtZSEJhNXJ2T24yVDNWcGtFN0QwVE1YQ2lXMEZBUi9BZUhVaUtIcTZheThDZ1lFQXdWYWcKczJwVWo5VXVXQVhJM0NQQUFaNXlpQlBtY0htdHBrczBOWXFOd3FGTDJlRVoyZ0cwbnlFMlFMTlVpcWpqR2cxSwp4dlZaRWhXTlFqNlpsaFBkN213em9QWTM5bUlUeXFkcmxQUzF2Z09XeUZ0M1NJMGFLQXlHaTFDaGd3R0pYMHEvCllROFBqVzJyT0JBSFZ0c1dlUzF1RFJnM2pXKytOMzVseUpZdnE1Y0NnWUVBa0lTSW91ZS8rNFYyVUFMcjBnZHYKWHBqTEt1Z3crMmo3RVBPbVlhMjFtMGRoMnRwbUtkNFFsRVFKUHdDQTBVWEprcTArYmRPUVRvNEY0MDhvdE9NdApLcnNjS1dnQlQ1M29rQXBDSDZESHlkOXBnWFJ6OWd5amMwSHRxelZpS0h4TzRFSUdVaFByV1BXVG5YbFh0L0I3CnZKZm8zU0MwY3liQytwMHJCQ2tFT3o4Q2dZQUdzOW9lWGpGUVN6T3dHWU05SG9BcGpqU3FRd1phSDkzRlJoWXAKUlFSbEd2Sm1PMGVLSjBUN3Ywc0NNelZiR1QvR1IyK3dOaEZBYno3V2JSVWwvc3BTMmExd2h4aXBrZnpkcWJBeApHY3F6SzZ5dWhYMDlKcWNoZkUydHhyM1NyTnIyVXNFUHZGWHRzVCtlVWUvdk11azBpajZtZFpCM2RzaEJaRUJqCkU5SFRRUUtCZ0VSUFVoNFFvZnI1Wk9JWjMwMXhjazFVTjRuSzFNOGl5cU9vSHREZzg1OFNoTEUvZ2pZL0xvWHgKNi9vUmhTdjFtT2ZRUUYzS1ZZek5FbE5YLzhzbUF6M2s1U3I2RDNhM1BSQk9MUzc0aTgyd083aWFiU1JHbk41YQpSaktYMXhJaGkzTjhMK0ttOUgwUDhIK01SdnIxMkplV09GNU9sdGtuSSthN1VRUkxvK3RRCi0tLS0tRU5EIFJTQSBQUklWQVRFIEtFWS0tLS0tCg==" 25 | } 26 | } 27 | ] 28 | } 29 | -------------------------------------------------------------------------------- /secrets/sso-app-secret.json: -------------------------------------------------------------------------------- 1 | { 2 | "kind": "List", 3 | "apiVersion": "v1", 4 | "metadata": { 5 | "annotations": { 6 | "description": "Examples that can be installed into your project to allow you to test the EAP template. You should replace the contents with data that is more appropriate for your deployment." 7 | } 8 | }, 9 | "labels": { 10 | "template": "sso-secret" 11 | }, 12 | "items": [ 13 | { 14 | "kind": "Secret", 15 | "apiVersion": "v1", 16 | "metadata": { 17 | "annotations": { 18 | "description": "Default secret file with name 'jboss' and password 'mykeystorepass'" 19 | }, 20 | "name": "sso-app-secret" 21 | }, 22 | "data": { 23 | "keystore.jks": "/u3+7QAAAAIAAAABAAAAAQAFamJvc3MAAAFShRzrOgAABQEwggT9MA4GCisGAQQBKgIRAQEFAASCBOmDfoVpQxGg4sIk+si6Fl16ZJDq+8FzpEtqsYLEzwmUHe/UMviPkxiH1FRwNzZ0axZ8uvI/zM73xGEYgAyFnVnEbxOf9llHJBbo1LNm7vLlhkVMRQLw6IM9GQVQGMRp40yWyd16+8NHWX1fC8TwduN0bkl8Sv50/meyEimyaM3WGiyfi1KqFNO2TaUAZNHMEWtsgb0BnoQRXQ9BX4HMSm71Kc4+LlvDfbGpRkSQ5hB4jwWf0vHTVualysOV7LdzLWXs/qvHKPpbZtBnXczDW20LJevoTYkjrS80ew/Jpj6z640OxGj1rpH+a4cRN1WkSfYo27zJf4p021fqFtNays3o4jegUK2oXTCZ4ZWIhk4sL/+dBlt3+pKaMst6h4tpdWPUqa7yZuOokl5Y9agA4Z8aBjj4w6VCReNYHVLayvk4V9E5w9cafVguzfKTlWFfUh40nQwkfIXXau+C4HICXCaECXLOju3/0oRqFaC2F6p1Tvkl+poaO+MnC4ShgOXVgOgQSO6FrYtSQzMbp0yWHBQsXLSks1Z48z9zlz4eSQMlV+f3EkIioD+Yb0uUI7fOrFfBUfSOKDJoDg51UVSRBY7Jko4BqCHeFnAnCCwxA0wQbd1HGAUlXJk2xL4M11vGQyOijmWKR0fp5g/ngKyJoDUhwwXYq2jONlbVxWghqoAnvkwzEkkCC1jWErM2lv66EVUfFYRZ/FuVIC2tUOTKs+ZcY7P6ya9F1OOpiQX80JtXL71OR1xqMqyelnoEeH1SymSlIPV8HpzVXzQtqVTgqMiqxDmv+JZMl5jjuFW6oQq26UN/H1oYIZyQDHSL4FunAPh983+wLzjj/Q2dVTZT12md/JTTdozTb0vozbTWGOdTTO+SV7DXyPUQg6xz0stL/6HsLhpVzZBJnufIr7MPl7O9AxI0KdaD4JeFuk63tqMfMSdt5s8D7qcSKuMFzh648NNwoZOFwyn9rIEMw99D9fCybqoLNAuefFialQfimF1jv9wZWriRt7YstUvYC2aZZmGmeUBklrEx77gWaghT+HJv7Dfr4uFw4a6lbpb21aknPx0JmfxmdkyH5sRG2MUojV7LYs3WEhC3UvHWR6MczFWcG7JpC2RYx36R5IIYOD6164erIOUCIETabRjyq2xzXgnkcV8mUI6IKMM62gBi+6HxG/Ls2blKx2hZJeOTiHOVzjV3gZ6VB7Gu9BfAW5bPZMOq7/Z+hQ4xdhf6JPOoRKcieb6CU+LjthZycaEDjvoekessmkgFjX/tMtM9ARjxwwlLtUO0wQRrVETVmxCO0cPHa+UIPgFcAGa9gOlIjYEZmwBRW8tCjCgHKXJXVymQHuBAu6nSmYu/26lbaz7S0a+4yD027KvD7y88ZGH22Uf/bjsPvnRvttIl+p0OHX7qzdaFd2Qfz3P7/vyNoK0vw/kZLXuVbEPkKCYVqFwm1MO5GjrDikOMSb7hm+9PLg4k3Ib80OVv9gJ47hn5QotivHnat02Ga89jsVCN6oxplL5bymQCzsV1wtFEkUzhnyRunvfZ1Z/Z22DouR27fltvbzxC4VMQ+cDZpxVxk4WowgRNP4oLSb08LQoMvIKx54uTu/IBmZxJinvOX11ODtKMgEdHFPEfNgNFSgvIdqo6H0h7w4KxelJT8IxPt3ZvoILX9+0MLrxCE6HSg0oAAAABAAVYLjUwOQAAA0MwggM/MIICJ6ADAgECAgR29XPcMA0GCSqGSIb3DQEBCwUAMFAxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDQTELMAkGA1UEBxMCU0QxCzAJBgNVBAoTAlJIMQswCQYDVQQLEwJDRTENMAsGA1UEAxMEQmlsbDAeFw0xNjAxMjcyMjAzMjdaFw0xNjA0MjYyMjAzMjdaMFAxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDQTELMAkGA1UEBxMCU0QxCzAJBgNVBAoTAlJIMQswCQYDVQQLEwJDRTENMAsGA1UEAxMEQmlsbDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAKuWH7G9DWZrnnW64VVrck1BjBGEWYMVDCVI8ADklap1UT1DHfdZ1CywMDtxOShp+8ZBO6gVfOoBmJ8SAd6roHFI9/N4X4Sl3VLfL/i6HEsxDIhI06bi8VbqzrrM3M6zlhG9B/JaVHkurWwsc2sxkgiGEO1bfYk+26LEM5LD3hmnFtQ7B8Cw5/Qpi0IPUe3gqQvSeAoeXhHtFsD0FgrnF1OwBh5pyG+T9SPJov/iyV9OQMg6QrtOGL/BtAAiqkFGdXOuNWSoOZTBFtq3L8HSwQl0n9Z2QC7X2pgclUbMJQsgc0gwAjCzXscxyDdW0qHLBsvvtghEGRN0BEYO3X4/Au0CAwEAAaMhMB8wHQYDVR0OBBYEFGt3cWZ4Bu0zb9CUY5lJq97rD3cWMA0GCSqGSIb3DQEBCwUAA4IBAQAKF2D2ajXngELf5iNNBOjdexYo7mWAsrD5Eep57oBil440Uoz5pB44hljQ3ItOZz7pyOoF3R+Gx4k5zLykqyU+WYF8PaMHsV6j+/+++dwyVMiIJxdkxPgcGrh/+LEFuSa6aTlyg8A2sHJiQcluJ4Ktn6/X5Yz8JD/h3TrEv8qKUgE719EE+Drqk3hxQxLzYx3v63uvQAWJ7zmk6dFLdLDHYCnrwe0E50Jzd0ZKd/M4ZStFPWqLDajhm9mOaBgU3HmpNoJYMXq+forhGPIF1QttZEoLZhaTzxDh3xvFPBb06rT2pja5mEDQtJR9eJ47H72W5UI8INqohqRK662r/F/bObGzQmqxXoafHVUvT0IS40Rn8GA=", 24 | "jgroups.jceks": "zs7OzgAAAAIAAAABAAAAAwAKc2VjcmV0LWtleQAAAVDQhuHmrO0ABXNyADNjb20uc3VuLmNyeXB0by5wcm92aWRlci5TZWFsZWRPYmplY3RGb3JLZXlQcm90ZWN0b3LNV8pZ5zC7UwIAAHhyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAJMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAN4cHVyAAJbQqzzF/gGCFTgAgAAeHAAAAAPMA0ECHcwLGK6EDyLAgEUdXEAfgAFAAAAmCu9wRKf1aYYUOEWe406ncPtIdm3147G7MJyWUu2kJVY15a2QxeZi9w5J3AF6T64CvylUuQjpcC4DWXwVn9BefntkBR8CzTiH7VxEqVOQ/OkFS29Inoq8t7/NBaTgTdmMkb4ETV1gIsy/+W6kk7QTqxItCkdKKGFE90Be/7yL3tG16TCy/ABKl7CO6PHa44CqK2PUE1oaJ+WdAAWUEJFV2l0aE1ENUFuZFRyaXBsZURFU3QAFlBCRVdpdGhNRDVBbmRUcmlwbGVERVMN658veJP01V2j9y8bQCYIzViutw==" 25 | } 26 | } 27 | ] 28 | } 29 | -------------------------------------------------------------------------------- /sso/README.md: -------------------------------------------------------------------------------- 1 | # Red Hat Single Sign-On 7.2 Application Templates 2 | 3 | OpenShift v3 application templates which support applications based on Red Hat Single Sign-On 7.2 product were moved. The new location can be found [here](https://github.com/jboss-container-images/redhat-sso-7-openshift-image/tree/sso72-dev/templates). 4 | -------------------------------------------------------------------------------- /template.adoc.in: -------------------------------------------------------------------------------- 1 | = {template} 2 | :toc: 3 | :toc-placement!: 4 | :toclevels: 5 5 | 6 | {description} 7 | 8 | toc::[] 9 | 10 | {#parameters} 11 | == Parameters 12 | 13 | Templates allow you to define parameters which take on a value. That value is then substituted wherever the parameter is referenced. 14 | References can be defined in any text field in the objects list field. Refer to the 15 | https://docs.okd.io/latest/architecture/core_concepts/templates.html#parameters[OKD documentation] for more information. 16 | 17 | |======================================================================= 18 | |Variable name |Image Environment Variable |Description |Example value |Required 19 | {parametertable} 20 | |======================================================================= 21 | {/parameters} 22 | 23 | {#objects} 24 | == Objects 25 | 26 | The CLI supports various object types. A list of these object types as well as their abbreviations 27 | can be found in the https://docs.okd.io/latest/cli_reference/basic_cli_operations.html#object-types[OKD documentation]. 28 | 29 | {#Service} 30 | === Services 31 | 32 | A service is an abstraction which defines a logical set of pods and a policy by which to access them. Refer to the 33 | https://docs.okd.io/latest/architecture/core_concepts/pods_and_services.html#services[OKD documentation] for more information. 34 | 35 | |============= 36 | |Service |Port |Name | Description 37 | {table} 38 | |============= 39 | {/Service} 40 | 41 | {#Route} 42 | === Routes 43 | 44 | A route is a way to expose a service by giving it an externally-reachable hostname such as `www.example.com`. A defined route and the endpoints 45 | identified by its service can be consumed by a router to provide named connectivity from external clients to your applications. Each route consists 46 | of a route name, service selector, and (optionally) security configuration. Refer to the 47 | https://docs.okd.io/latest/dev_guide/routes.html[OKD documentation] for more information. 48 | 49 | |============= 50 | | Service | Security | Hostname 51 | {table} 52 | |============= 53 | {/Route} 54 | 55 | {#BuildConfig} 56 | === Build Configurations 57 | 58 | A `buildConfig` describes a single build definition and a set of triggers for when a new build should be created. 59 | A `buildConfig` is a REST object, which can be used in a POST to the API server to create a new instance. Refer to 60 | the https://docs.okd.io/latest/dev_guide/builds/index.html[OKD documentation] 61 | for more information. 62 | 63 | |============= 64 | | S2I image | link | Build output | BuildTriggers and Settings 65 | {table} 66 | |============= 67 | {/BuildConfig} 68 | 69 | === Deployment Configurations 70 | 71 | A deployment in OpenShift is a replication controller based on a user defined template called a deployment configuration. Deployments are created manually or in response to triggered events. 72 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/how_deployments_work.html#creating-a-deployment-configuration[OKD documentation] for more information. 73 | 74 | {#triggers} 75 | ==== Triggers 76 | 77 | A trigger drives the creation of new deployments in response to events, both inside and outside OpenShift. Refer to the 78 | https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#triggers[OKD documentation] for more information. 79 | 80 | |============ 81 | |Deployment | Triggers 82 | {table} 83 | |============ 84 | {/triggers} 85 | 86 | {#replicas} 87 | ==== Replicas 88 | 89 | A replication controller ensures that a specified number of pod "replicas" are running at any one time. 90 | If there are too many, the replication controller kills some pods. If there are too few, it starts more. 91 | Refer to the https://docs.okd.io/latest/dev_guide/deployments/basic_deployment_operations.html#scaling[OKD documentation] 92 | for more information. 93 | 94 | |============ 95 | |Deployment | Replicas 96 | {table} 97 | |============ 98 | {/replicas} 99 | 100 | ==== Pod Template 101 | 102 | {#serviceAccountName} 103 | ===== Service Accounts 104 | 105 | Service accounts are API objects that exist within each project. They can be created or deleted like any other API object. Refer to the 106 | https://docs.okd.io/latest/dev_guide/service_accounts.html#dev-managing-service-accounts[OKD documentation] for more 107 | information. 108 | 109 | |============ 110 | |Deployment | Service Account 111 | {table} 112 | |============ 113 | {/serviceAccountName} 114 | 115 | {#image} 116 | ===== Image 117 | 118 | |============ 119 | |Deployment | Image 120 | {table} 121 | |============ 122 | {/image} 123 | 124 | {#readinessProbe} 125 | ===== Readiness Probe 126 | 127 | {table} 128 | {/readinessProbe} 129 | 130 | {#ports} 131 | ===== Exposed Ports 132 | 133 | |============= 134 | |Deployments | Name | Port | Protocol 135 | {table} 136 | |============= 137 | {/ports} 138 | 139 | {#env} 140 | ===== Image Environment Variables 141 | 142 | |======================================================================= 143 | |Deployment |Variable name |Description |Example value 144 | {table} 145 | |======================================================================= 146 | {/env} 147 | 148 | {#volumes} 149 | ===== Volumes 150 | 151 | |============= 152 | |Deployment |Name | mountPath | Purpose | readOnly 153 | {table} 154 | |============= 155 | {/volumes} 156 | 157 | === External Dependencies 158 | 159 | {#PersistentVolumeClaim} 160 | ==== Volume Claims 161 | 162 | A `PersistentVolume` object is a storage resource in an OpenShift cluster. Storage is provisioned by an administrator 163 | by creating `PersistentVolume` objects from sources such as GCE Persistent Disks, AWS Elastic Block Stores (EBS), and NFS mounts. 164 | Refer to the https://docs.okd.io/latest/dev_guide/persistent_volumes.html#overview[OKD documentation] for 165 | more information. 166 | 167 | |============= 168 | |Name | Access Mode 169 | {table} 170 | |============= 171 | 172 | {/PersistentVolumeClaim} 173 | 174 | {#secrets} 175 | ==== Secrets 176 | 177 | This template requires link:../secrets/{secretName}.adoc[{secretFile}] 178 | to be installed for the application to run. 179 | {/secrets} 180 | 181 | {#clustering} 182 | [[clustering]] 183 | ==== Clustering 184 | 185 | Clustering in OpenShift EAP is achieved through one of two discovery mechanisms: 186 | Kubernetes or DNS. This is done by configuring the JGroups protocol stack in 187 | standalone-openshift.xml with either the `` or `` 188 | elements. The templates are configured to use `DNS_PING`, however `KUBE_PING`is 189 | the default used by the image. 190 | 191 | The discovery mechanism used is specified by the `JGROUPS_PING_PROTOCOL` environment 192 | variable which can be set to either `openshift.DNS_PING` or `openshift.KUBE_PING`. 193 | `openshift.KUBE_PING` is the default used by the image if no value is specified 194 | for `JGROUPS_PING_PROTOCOL`. 195 | 196 | For DNS_PING to work, the following steps must be taken: 197 | 198 | . The `OPENSHIFT_DNS_PING_SERVICE_NAME` environment variable must be set to the 199 | name of the ping service for the cluster (see table above). If not set, the 200 | server will act as if it is a single-node cluster (a "cluster of one"). 201 | . The `OPENSHIFT_DNS_PING_SERVICE_PORT` environment variables should be set to 202 | the port number on which the ping service is exposed (see table above). The 203 | `DNS_PING` protocol will attempt to discern the port from the SRV records, if 204 | it can, otherwise it will default to 8888. 205 | . A ping service which exposes the ping port must be defined. This service 206 | should be "headless" (ClusterIP=None) and must have the following: 207 | .. The port must be named for port discovery to work. 208 | .. It must be annotated with `service.alpha.kubernetes.io/tolerate-unready-endpoints` 209 | set to `"true"`. Omitting this annotation will result in each node forming 210 | their own "cluster of one" during startup, then merging their cluster into 211 | the other nodes' clusters after startup (as the other nodes are not detected 212 | until after they have started). 213 | 214 | .Example ping service for use with DNS_PING 215 | [source,yaml] 216 | ---- 217 | kind: Service 218 | apiVersion: v1 219 | spec: 220 | clusterIP: None 221 | ports: 222 | - name: ping 223 | port: 8888 224 | selector: 225 | deploymentConfig: eap-app 226 | metadata: 227 | name: eap-app-ping 228 | annotations: 229 | service.alpha.kubernetes.io/tolerate-unready-endpoints: "true" 230 | description: "The JGroups ping port for clustering." 231 | ---- 232 | 233 | For `KUBE_PING` to work, the following steps must be taken: 234 | 235 | . The `OPENSHIFT_KUBE_PING_NAMESPACE` environment variable must be set (see table above). 236 | If not set, the server will act as if it is a single-node cluster (a "cluster of one"). 237 | . The `OPENSHIFT_KUBE_PING_LABELS` environment variables should be set (see table above). 238 | If not set, pods outside of your application (albeit in your namespace) will try to join. 239 | . Authorization must be granted to the service account the pod is running under to be 240 | allowed to access Kubernetes' REST api. This is done on the command line. 241 | 242 | .Policy commands 243 | ==== 244 | Using the default service account in the myproject namespace: 245 | .... 246 | oc policy add-role-to-user view system:serviceaccount:myproject:default -n myproject 247 | .... 248 | Using the eap-service-account in the myproject namespace: 249 | .... 250 | oc policy add-role-to-user view system:serviceaccount:myproject:eap-service-account -n myproject 251 | .... 252 | ==== 253 | {/clustering} 254 | {/objects} 255 | -------------------------------------------------------------------------------- /webserver/jws30-tomcat7-image-stream.json: -------------------------------------------------------------------------------- 1 | { 2 | "kind": "List", 3 | "apiVersion": "v1", 4 | "metadata": { 5 | "name": "webserver30-tomcat7-image-stream", 6 | "annotations": { 7 | "description": "ImageStream definition for Red Hat JBoss Web Server 3.0 Apache Tomcat 7.", 8 | "openshift.io/provider-display-name": "Red Hat, Inc." 9 | } 10 | }, 11 | "items": [ 12 | { 13 | "kind": "ImageStream", 14 | "apiVersion": "v1", 15 | "metadata": { 16 | "name": "jboss-webserver30-tomcat7-openshift", 17 | "annotations": { 18 | "openshift.io/display-name": "Red Hat JBoss Web Server 3.0 Apache Tomcat 7", 19 | "openshift.io/provider-display-name": "Red Hat, Inc.", 20 | "version": "1.4.17" 21 | } 22 | }, 23 | "labels": { 24 | "xpaas": "1.4.17" 25 | }, 26 | "spec": { 27 | "tags": [ 28 | { 29 | "name": "1.1", 30 | "annotations": { 31 | "description": "JBoss Web Server 3.0 Apache Tomcat 7 S2I images.", 32 | "iconClass": "icon-rh-tomcat", 33 | "tags": "builder,tomcat,tomcat7,java,jboss,hidden", 34 | "supports": "tomcat7:3.0,tomcat:7,java:8", 35 | "sampleRepo": "https://github.com/jboss-openshift/openshift-quickstarts.git", 36 | "sampleContextDir": "tomcat-websocket-chat", 37 | "version": "1.1", 38 | "openshift.io/display-name": "Red Hat JBoss Web Server 3.0 Apache Tomcat 7" 39 | }, 40 | "referencePolicy": { 41 | "type": "Local" 42 | }, 43 | "from": { 44 | "kind": "DockerImage", 45 | "name": "registry.redhat.io/jboss-webserver-3/webserver30-tomcat7-openshift:1.1" 46 | } 47 | }, 48 | { 49 | "name": "1.2", 50 | "annotations": { 51 | "description": "JBoss Web Server 3.0 Apache Tomcat 7 S2I images.", 52 | "iconClass": "icon-rh-tomcat", 53 | "tags": "builder,tomcat,tomcat7,java,jboss,hidden", 54 | "supports": "tomcat7:3.0,tomcat:7,java:8", 55 | "sampleRepo": "https://github.com/jboss-openshift/openshift-quickstarts.git", 56 | "sampleContextDir": "tomcat-websocket-chat", 57 | "version": "1.2", 58 | "openshift.io/display-name": "Red Hat JBoss Web Server 3.0 Apache Tomcat 7" 59 | }, 60 | "referencePolicy": { 61 | "type": "Local" 62 | }, 63 | "from": { 64 | "kind": "DockerImage", 65 | "name": "registry.redhat.io/jboss-webserver-3/webserver30-tomcat7-openshift:1.2" 66 | } 67 | }, 68 | { 69 | "name": "1.3", 70 | "annotations": { 71 | "description": "JBoss Web Server 3.0 Apache Tomcat 7 S2I images.", 72 | "iconClass": "icon-rh-tomcat", 73 | "tags": "builder,tomcat,tomcat7,java,jboss,hidden", 74 | "supports": "tomcat7:3.0,tomcat:7,java:8", 75 | "sampleRepo": "https://github.com/jboss-openshift/openshift-quickstarts.git", 76 | "sampleContextDir": "tomcat-websocket-chat", 77 | "version": "1.3", 78 | "openshift.io/display-name": "Red Hat JBoss Web Server 3.0 ApacheTomcat 7" 79 | }, 80 | "referencePolicy": { 81 | "type": "Local" 82 | }, 83 | "from": { 84 | "kind": "DockerImage", 85 | "name": "registry.redhat.io/jboss-webserver-3/webserver30-tomcat7-openshift:1.3" 86 | } 87 | } 88 | ] 89 | } 90 | } 91 | ] 92 | } 93 | -------------------------------------------------------------------------------- /webserver/jws30-tomcat8-image-stream.json: -------------------------------------------------------------------------------- 1 | { 2 | "kind": "List", 3 | "apiVersion": "v1", 4 | "metadata": { 5 | "name": "webserver30-tomcat8-image-stream", 6 | "annotations": { 7 | "description": "ImageStream definition for Red Hat JBoss Web Server 3.0 Apache Tomcat 8.", 8 | "openshift.io/provider-display-name": "Red Hat, Inc." 9 | } 10 | }, 11 | "items": [ 12 | { 13 | "kind": "ImageStream", 14 | "apiVersion": "v1", 15 | "metadata": { 16 | "name": "jboss-webserver30-tomcat8-openshift", 17 | "annotations": { 18 | "openshift.io/display-name": "Red Hat JBoss Web Server 3.0 Apache Tomcat 8", 19 | "openshift.io/provider-display-name": "Red Hat, Inc.", 20 | "version": "1.4.17" 21 | } 22 | }, 23 | "labels": { 24 | "xpaas": "1.4.17" 25 | }, 26 | "spec": { 27 | "tags": [ 28 | { 29 | "name": "1.1", 30 | "annotations": { 31 | "description": "JBoss Web Server 3.0 Apache Tomcat 8 S2I images.", 32 | "iconClass": "icon-rh-tomcat", 33 | "tags": "builder,tomcat,tomcat8,java,jboss,hidden", 34 | "supports": "tomcat8:3.0,tomcat:8,java:8", 35 | "sampleRepo": "https://github.com/jboss-openshift/openshift-quickstarts.git", 36 | "sampleContextDir": "tomcat-websocket-chat", 37 | "version": "1.1", 38 | "openshift.io/display-name": "Red Hat JBoss Web Server 3.0 Apache Tomcat 8" 39 | }, 40 | "referencePolicy": { 41 | "type": "Local" 42 | }, 43 | "from": { 44 | "kind": "DockerImage", 45 | "name": "registry.redhat.io/jboss-webserver-3/webserver30-tomcat8-openshift:1.1" 46 | } 47 | }, 48 | { 49 | "name": "1.2", 50 | "annotations": { 51 | "description": "JBoss Web Server 3.0 Apache Tomcat 8 S2I images.", 52 | "iconClass": "icon-rh-tomcat", 53 | "tags": "builder,tomcat,tomcat8,java,jboss,hidden", 54 | "supports": "tomcat8:3.0,tomcat:8,java:8", 55 | "sampleRepo": "https://github.com/jboss-openshift/openshift-quickstarts.git", 56 | "sampleContextDir": "tomcat-websocket-chat", 57 | "version": "1.2", 58 | "openshift.io/display-name": "Red Hat JBoss Web Server 3.0 Apache Tomcat 8" 59 | }, 60 | "referencePolicy": { 61 | "type": "Local" 62 | }, 63 | "from": { 64 | "kind": "DockerImage", 65 | "name": "registry.redhat.io/jboss-webserver-3/webserver30-tomcat8-openshift:1.2" 66 | } 67 | }, 68 | { 69 | "name": "1.3", 70 | "annotations": { 71 | "description": "JBoss Web Server 3.0 Apache Tomcat 8 S2I images.", 72 | "iconClass": "icon-rh-tomcat", 73 | "tags": "builder,tomcat,tomcat8,java,jboss,hidden", 74 | "supports": "tomcat8:3.0,tomcat:8,java:8", 75 | "sampleRepo": "https://github.com/jboss-openshift/openshift-quickstarts.git", 76 | "sampleContextDir": "tomcat-websocket-chat", 77 | "version": "1.3", 78 | "openshift.io/display-name": "Red Hat JBoss Web Server 3.0 Apache Tomcat 8" 79 | }, 80 | "referencePolicy": { 81 | "type": "Local" 82 | }, 83 | "from": { 84 | "kind": "DockerImage", 85 | "name": "registry.redhat.io/jboss-webserver-3/webserver30-tomcat8-openshift:1.3" 86 | } 87 | } 88 | ] 89 | } 90 | } 91 | ] 92 | } 93 | -------------------------------------------------------------------------------- /webserver/jws31-tomcat7-image-stream.json: -------------------------------------------------------------------------------- 1 | { 2 | "kind": "List", 3 | "apiVersion": "v1", 4 | "metadata": { 5 | "name": "webserver31-tomcat7-image-stream", 6 | "annotations": { 7 | "description": "ImageStream definition for Red Hat JBoss Web Server 3.1 Apache Tomcat 7.", 8 | "openshift.io/provider-display-name": "Red Hat, Inc." 9 | } 10 | }, 11 | "items": [ 12 | { 13 | "kind": "ImageStream", 14 | "apiVersion": "v1", 15 | "metadata": { 16 | "name": "jboss-webserver31-tomcat7-openshift", 17 | "annotations": { 18 | "openshift.io/display-name": "Red Hat JBoss Web Server 3.1 Apache Tomcat 7", 19 | "openshift.io/provider-display-name": "Red Hat, Inc.", 20 | "version": "1.4.17" 21 | } 22 | }, 23 | "labels": { 24 | "xpaas": "1.4.17" 25 | }, 26 | "spec": { 27 | "tags": [ 28 | { 29 | "name": "1.0", 30 | "annotations": { 31 | "description": "JBoss Web Server 3.1 Apache Tomcat 7 S2I images.", 32 | "iconClass": "icon-rh-tomcat", 33 | "tags": "builder,tomcat,tomcat7,java,jboss,hidden", 34 | "supports": "tomcat7:3.1,tomcat:7,java:8", 35 | "sampleRepo": "https://github.com/jboss-openshift/openshift-quickstarts.git", 36 | "sampleContextDir": "tomcat-websocket-chat", 37 | "version": "1.0", 38 | "openshift.io/display-name": "Red Hat JBoss Web Server 3.1 Apache Tomcat 7" 39 | }, 40 | "referencePolicy": { 41 | "type": "Local" 42 | }, 43 | "from": { 44 | "kind": "DockerImage", 45 | "name": "registry.redhat.io/jboss-webserver-3/webserver31-tomcat7-openshift:1.0" 46 | } 47 | }, 48 | { 49 | "name": "1.1", 50 | "annotations": { 51 | "description": "JBoss Web Server 3.1 Apache Tomcat 7 S2I images.", 52 | "iconClass": "icon-rh-tomcat", 53 | "tags": "builder,tomcat,tomcat7,java,jboss,hidden", 54 | "supports": "tomcat7:3.1,tomcat:7,java:8", 55 | "sampleRepo": "https://github.com/jboss-openshift/openshift-quickstarts.git", 56 | "sampleContextDir": "tomcat-websocket-chat", 57 | "version": "1.1", 58 | "openshift.io/display-name": "Red Hat JBoss Web Server 3.1 Apache Tomcat 7" 59 | }, 60 | "referencePolicy": { 61 | "type": "Local" 62 | }, 63 | "from": { 64 | "kind": "DockerImage", 65 | "name": "registry.redhat.io/jboss-webserver-3/webserver31-tomcat7-openshift:1.1" 66 | } 67 | }, 68 | { 69 | "name": "1.2", 70 | "annotations": { 71 | "description": "JBoss Web Server 3.1 Apache Tomcat 7 S2I images.", 72 | "iconClass": "icon-rh-tomcat", 73 | "tags": "builder,tomcat,tomcat7,java,jboss,hidden", 74 | "supports": "tomcat7:3.1,tomcat:7,java:8", 75 | "sampleRepo": "https://github.com/jboss-openshift/openshift-quickstarts.git", 76 | "sampleContextDir": "tomcat-websocket-chat", 77 | "version": "1.2", 78 | "openshift.io/display-name": "Red Hat JBoss Web Server 3.1 Apache Tomcat 7" 79 | }, 80 | "referencePolicy": { 81 | "type": "Local" 82 | }, 83 | "from": { 84 | "kind": "DockerImage", 85 | "name": "registry.redhat.io/jboss-webserver-3/webserver31-tomcat7-openshift:1.2" 86 | } 87 | }, 88 | { 89 | "name": "1.3", 90 | "annotations": { 91 | "description": "JBoss Web Server 3.1 Apache Tomcat 7 S2I images.", 92 | "iconClass": "icon-rh-tomcat", 93 | "tags": "builder,tomcat,tomcat7,java,jboss,hidden", 94 | "supports": "tomcat7:3.1,tomcat:7,java:8", 95 | "sampleRepo": "https://github.com/jboss-openshift/openshift-quickstarts.git", 96 | "sampleContextDir": "tomcat-websocket-chat", 97 | "version": "1.3", 98 | "openshift.io/display-name": "Red Hat JBoss Web Server 3.1 Apache Tomcat 7" 99 | }, 100 | "referencePolicy": { 101 | "type": "Local" 102 | }, 103 | "from": { 104 | "kind": "DockerImage", 105 | "name": "registry.redhat.io/jboss-webserver-3/webserver31-tomcat7-openshift:1.3" 106 | } 107 | } 108 | ] 109 | } 110 | } 111 | ] 112 | } 113 | -------------------------------------------------------------------------------- /webserver/jws31-tomcat8-image-stream.json: -------------------------------------------------------------------------------- 1 | { 2 | "kind": "List", 3 | "apiVersion": "v1", 4 | "metadata": { 5 | "name": "webserver31-tomcat8-image-stream", 6 | "annotations": { 7 | "description": "ImageStream definition for Red Hat JBoss Web Server 3.1 Apache Tomcat 8.", 8 | "openshift.io/provider-display-name": "Red Hat, Inc." 9 | } 10 | }, 11 | "items": [ 12 | { 13 | "kind": "ImageStream", 14 | "apiVersion": "v1", 15 | "metadata": { 16 | "name": "jboss-webserver31-tomcat8-openshift", 17 | "annotations": { 18 | "openshift.io/display-name": "JBoss Web Server 3.1 Apache Tomcat 8", 19 | "openshift.io/provider-display-name": "Red Hat, Inc.", 20 | "version": "1.4.17" 21 | } 22 | }, 23 | "labels": { 24 | "xpaas": "1.4.17" 25 | }, 26 | "spec": { 27 | "tags": [ 28 | { 29 | "name": "1.0", 30 | "annotations": { 31 | "description": "JBoss Web Server 3.1 Apache Tomcat 8 S2I images.", 32 | "iconClass": "icon-rh-tomcat", 33 | "tags": "builder,tomcat,tomcat8,java,jboss,hidden", 34 | "supports": "tomcat8:3.1,tomcat:8,java:8", 35 | "sampleRepo": "https://github.com/jboss-openshift/openshift-quickstarts.git", 36 | "sampleContextDir": "tomcat-websocket-chat", 37 | "version": "1.0", 38 | "openshift.io/display-name": "JBoss Web Server 3.1 Apache Tomcat 8" 39 | }, 40 | "referencePolicy": { 41 | "type": "Local" 42 | }, 43 | "from": { 44 | "kind": "DockerImage", 45 | "name": "registry.redhat.io/jboss-webserver-3/webserver31-tomcat8-openshift:1.0" 46 | } 47 | }, 48 | { 49 | "name": "1.1", 50 | "annotations": { 51 | "description": "JBoss Web Server 3.1 Apache Tomcat 8 S2I images.", 52 | "iconClass": "icon-rh-tomcat", 53 | "tags": "builder,tomcat,tomcat8,java,jboss,hidden", 54 | "supports": "tomcat8:3.1,tomcat:8,java:8", 55 | "sampleRepo": "https://github.com/jboss-openshift/openshift-quickstarts.git", 56 | "sampleContextDir": "tomcat-websocket-chat", 57 | "version": "1.1", 58 | "openshift.io/display-name": "Red Hat JBoss Web Server 3.1 Apache Tomcat 8" 59 | }, 60 | "referencePolicy": { 61 | "type": "Local" 62 | }, 63 | "from": { 64 | "kind": "DockerImage", 65 | "name": "registry.redhat.io/jboss-webserver-3/webserver31-tomcat8-openshift:1.1" 66 | } 67 | }, 68 | { 69 | "name": "1.2", 70 | "annotations": { 71 | "description": "JBoss Web Server 3.1 Apache Tomcat 8 S2I images.", 72 | "iconClass": "icon-rh-tomcat", 73 | "tags": "builder,tomcat,tomcat8,java,jboss,hidden", 74 | "supports": "tomcat8:3.1,tomcat:8,java:8", 75 | "sampleRepo": "https://github.com/jboss-openshift/openshift-quickstarts.git", 76 | "sampleContextDir": "tomcat-websocket-chat", 77 | "version": "1.2", 78 | "openshift.io/display-name": "Red Hat JBoss Web Server 3.1 Apache Tomcat 8" 79 | }, 80 | "referencePolicy": { 81 | "type": "Local" 82 | }, 83 | "from": { 84 | "kind": "DockerImage", 85 | "name": "registry.redhat.io/jboss-webserver-3/webserver31-tomcat8-openshift:1.2" 86 | } 87 | }, 88 | { 89 | "name": "1.3", 90 | "annotations": { 91 | "description": "JBoss Web Server 3.1 Apache Tomcat 8 S2I images.", 92 | "iconClass": "icon-rh-tomcat", 93 | "tags": "builder,tomcat,tomcat8,java,jboss,hidden", 94 | "supports": "tomcat8:3.1,tomcat:8,java:8", 95 | "sampleRepo": "https://github.com/jboss-openshift/openshift-quickstarts.git", 96 | "sampleContextDir": "tomcat-websocket-chat", 97 | "version": "1.3", 98 | "openshift.io/display-name": "Red Hat JBoss Web Server 3.1 Apache Tomcat 8" 99 | }, 100 | "referencePolicy": { 101 | "type": "Local" 102 | }, 103 | "from": { 104 | "kind": "DockerImage", 105 | "name": "registry.redhat.io/jboss-webserver-3/webserver31-tomcat8-openshift:1.3" 106 | } 107 | } 108 | ] 109 | } 110 | } 111 | ] 112 | } 113 | --------------------------------------------------------------------------------