Chapter 6. Enabling level-2 seamless integration for new images

Procedure

1. In your project namespace, create an image stream by using the oc import-image command to import the tag and other information for an image.

   For example:

   oc import-image <my-image>-imagestream:latest \
   --from=quay.io/$user/<my-image>:latest \
   --confirm

   In the preceding example, replace each occurrence of <my-image> with the name of the image that you want to import.

   The preceding command creates an image stream named <my-image>-imagestream by importing information for the quay.io/$user/<my-image> image. For more information about the format and management of image streams, see Managing image streams.

2. Create a custom resource of the WebServer kind for the web application that you want the JWS Operator to deploy whenever the image stream is updated. You can define the custom resource in YAML file format.

   For example:

   apiVersion: web.servers.org/v1alpha1
   kind: WebServer
   metadata:
     name: <my-image>
   spec:
     # Add fields here
     applicationName: my-app
     useSessionClustering: true
     replicas: 2
     webImageStream:
       imageStreamNamespace: <project-name>
       imageStreamName: <my-image>-imagestream

3. Trigger an update to the image stream by using the oc tag command.

   For example:

   oc tag quay.io/$user/<my-image> <my-image>-imagestream:latest --scheduled

   The preceding command causes OpenShift Container Platform to update the specified image stream tag periodically. This period is a cluster-wide setting that is set to 15 minutes by default.