Chapter 2. Getting Started for administrators

Procedure

1. Login to OpenShift as a user with cluster admin access:

   oc login -u <user_with_cluster_admin_role>

2. Retrieve the service signing certificate authority keys, by executing the following commands:

   • To retrieve the certificate:

     oc get secrets/signing-key -n openshift-service-ca -o "jsonpath={.data['tls\.crt']}" | base64 --decode > ca.crt

   • To retrieve the private key:

     oc get secrets/signing-key -n openshift-service-ca -o "jsonpath={.data['tls\.key']}" | base64 --decode > ca.key

3. Generate the client certificate, as documented in Kubernetes certificates administration, using either easyrsa, openssl, or cfssl.

   Here are the example commands using openssl:

   1. Generate the private key:

      openssl genrsa -out server.key 2048

   2. Write the CSR config file.

      cat <<EOT >> csr.conf
        [ req ]
        default_bits = 2048
        prompt = no
        default_md = sha256
        distinguished_name = dn
      
        [ dn ]
        CN = fuse-console.fuse.svc
      
        [ v3_ext ]
        authorityKeyIdentifier=keyid,issuer:always
        keyUsage=keyEncipherment,dataEncipherment,digitalSignature
        extendedKeyUsage=serverAuth,clientAuth
      EOT

   3. Generate the CSR:

      openssl req -new -key server.key -out server.csr -config csr.conf

   4. Issue the signed certificate:

      openssl x509 -req -in server.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out server.crt -days 10000 -extensions v3_ext -extfile csr.conf

Procedure

1. Verify that the Fuse Console image stream is installed by using the following command to retrieve a list of all templates:

   oc get template -n openshift

2. Optionally, if you want to update the already installed image stream with new release tags, use the following command to import the Fuse Console image to the openshift namespace:

   oc import-image fuse7/fuse7-console:1.5 --from=registry.redhat.io/fuse7/fuse-console:1.5 --confirm -n openshift

3. Download one of the following Fuse Console templates from https://raw.githubusercontent.com/jboss-fuse/application-templates/application-templates-2.1.fuse-750056-redhat-00006 in raw format to a local directory of your choice (for example, mytemp).

   • Cluster template: fuse-console-cluster-os4.json
   • Namespace template: fuse-console-namespace-os4.json

4. For the namespace template, skip to the next step.

   For the cluster template, in an editor of your choice, edit your local copy of the fuse-console-cluster-os4.json file to add the "grantMethod": "auto" attribute to the OAuthClient section:

   {
         "kind": "OAuthClient",
         "apiVersion": "v1",
         "metadata": {
           "name": "${APP_NAME}-oauth-client"
         },
         "grantMethod": "auto",
         "redirectURIs": [
           "https://${ROUTE_HOSTNAME}"
         ]
   }

5. Obtain the Fuse Console APP_NAME value by running the following command (where mytemp is the path to the local directory that contains the Fuse Console template):

   • For the cluster template:

     oc process --parameters -f mytemp/fuse-console-cluster-os4.json

   • For the namespace template:

     oc process --parameters -f mytemp/fuse-console-namespace-os4.json

6. From the certificate that you generated in Securing the Fuse Console on OpenShift 4.x, create the secret and mount it in the Fuse Console by using the following command (where APP_NAME is the name of the Fuse Console application.

   oc create secret tls APP_NAME-tls-proxying --cert server.crt --key server.key

7. Create a new application based on your local copy of the Fuse Console template by running the following command (where myproject is the name of your OpenShift project, mytemp is the path to the local directory that contains the Fuse Console template, and myhost is the hostname to access the Fuse Console:

   • For the cluster template:

     oc new-app -n myproject -f mytemp/fuse-console-cluster-os4.json -p ROUTE_HOSTNAME=myhost

   • For the namespace template:

     oc new-app -n myproject -f mytemp/fuse-console-namespace-os4.json

8. Obtain the status and the URL of your Fuse Console deployment by running this command:

   oc status

9. To access the Fuse Console from a browser, use the URL that is returned in Step 6 (for example, https://fuse-console.192.168.64.12.nip.io).

1. In a terminal window, use the following command to change the .spec.version field of the application custom resource definition:

   oc patch <project-name> <custom-resource-name> --type='merge' -p '{"spec":{"version":"1.7.1"}}'

   For example:

   oc patch myproject example-fuseconsole --type='merge' -p '{"spec":{"version":"1.7.1"}}'

2. Check that the application’s status has updated:

    oc get myproject

   The response shows information about the application, including the version number:

   NAME                  AGE   URL                                        IMAGE
   example-fuseconsole   1m    https://fuseconsole.192.168.64.38.nip.io   docker.io/fuseconsole/online:1.7.1

   When you change the value of the .spec.version field, OpenShift automatically redeploys the application.

3. To check the status of the redeployment that is triggered by the version change:

   oc rollout status deployment.v1.apps/example-fuseconsole

   A successful deployment shows this response:

   deployment "example-fuseconsole" successfully rolled out

Procedure

1. In the OpenShift web console, click Operators and then click Installed Operators.
2. In the Name column, click API Designer.

3. Under Provided APIs, click Create Instance.

   A default form with a minimal starting template for the API Designer instance opens.

4. Accept the default values or optionally edit the following values:

   • size: The number of pods for the API Designer instance.

     The default is three pods for three new resource types that contain logic specific to managing API Designer.

   • image: The API Designer image. If you change this image, the API Designer operator is automatically upgraded on the cluster.
5. Click Create to create a new apicurito-service. OpenShift starts up of the pods, services, and other components for the new API Designer service.

6. To verify that the API Designer service is available:

   1. Click Operators and then click Installed Operators.

   2. In the Provided APIs column, click Apicurito CRD.

      On the Operator Details page, the apicurito-service is listed.

7. To obtain the URL for the API Designer:

   1. Click Networking > Routes.
   2. Make sure that the correct project is selected.
   3. In the apicurito-service row, find the URL for the API Designer web console in the Location column.

Procedure

1. In the OpenShift console, open an existing project or create a new project.

2. Add the Fuse Console to your OpenShift project:

   1. Select Add to Project → Browse Catalog.

      The Select an item to add to the current project page opens.

   2. In the Search field, type Fuse Console.

      The Red Hat Fuse 7.x Console and Red Hat Fuse 7.x Console (cluster) items should appear as the search result.

1. Click one of the Red Hat Fuse Console items:

   • Red Hat Fuse 7.x Console - This version of the Fuse Console discovers and connects to Fuse applications deployed in the current OpenShift project.
   • Red Hat Fuse 7.x Console (cluster) - This version of the Fuse Console can discover and connect to Fuse applications deployed across multiple projects on the OpenShift cluster.

2. In the Red Hat Fuse Console wizard, click Next. The Configuration page of the wizard opens.

   Optionally, you can change the default values of the configuration parameters.

   1. Click Create.

      The Results page of the wizard indicates that the Red Hat Fuse Console has been created.

   2. Click the Continue to the project overview link to verify that the Fuse Console application is added to the project.

   3. To open the Fuse Console, click the provided URL link and then log in.

      An Authorize Access page opens in the browser listing the required permissions.

   4. Click Allow selected permissions.

      The Fuse Console opens in the browser and shows the Fuse pods running in the project.

   5. Click Connect for the application that you want to view.

      A new browser window opens showing the application in the Fuse Console.

1. From the Applications → Pods view in your OpenShift project, click on the pod name to view the details of the running Fuse pod. On the right-hand side of this page, you see a summary of the container template:

   

2. From this view, click on the Open Java Console link to open the Fuse Console.

   

   Note

   In order to configure OpenShift to display a link to Fuse Console in the pod view, the pod running a Fuse on OpenShift image must declare a TCP port within a name attribute set to jolokia:

   {
     "kind": "Pod",
     [...]
     "spec": {
       "containers": [
         {
           [...]
           "ports": [
             {
               "name": "jolokia",
               "containerPort": 8778,
               "protocol": "TCP"
             }

1. Create a new application based on a Fuse Console template by running one of the following commands (where myproject is the name of your project):

   • For the Fuse Console cluster template, where myhost is the hostname to access the Fuse Console:

     oc new-app -n myproject -f https://raw.githubusercontent.com/jboss-fuse/application-templates/application-templates-2.1.fuse-750056-redhat-00006/fis-console-cluster-template.json -p ROUTE_HOSTNAME=myhost

   • For the Fuse Console namespace template:

     oc new-app -n myproject -f https://raw.githubusercontent.com/jboss-fuse/application-templates/application-templates-2.1.fuse-750056-redhat-00006/fis-console-namespace-template.json

     Note

     You can omit the route_hostname parameter for the namespace template because OpenShift automatically generates one.

2. Obtain the status and the URL of your Fuse Console deployment by running this command:

   oc status

3. To access the Fuse Console from a browser, use the provided URL (for example, https://fuse-console.192.168.64.12.nip.io).