@@ -18,7 +18,7 @@ First, the OpenShift administrators have to create the MkDocs Image Stream in th
In order to be able to actually edit the MkDocs Image Stream we need a token that grants us permission via a special account. The OpenShift administrators can generate this token. To use this token we can login as such `oc login https://openshift.cern.ch --token={TOKEN}`.
With the right permissions we now have to connect the MkDocs Image Stream to the S2I MkDocs Container. This is achieved by tagging the image into the image stream: `oc tag --source=docker gitlab-registry.cern.ch/authoring/documentation/s2i-mkdocs-container:latest openshift/mkdocs:1.0 --reference-policy=local`. This will create the tag name (`1.0` in this case) if it doesn't already exist. Once the this is tagged we can check it out by running `oc describe istag/mkdocs:1.0 -n openshift`.
With the right permissions and the right Openshift CLI version (v3.10.0) we now have to connect the MkDocs Image Stream to the S2I MkDocs Container. This is achieved by tagging the image into the image stream: `oc tag --source=docker gitlab-registry.cern.ch/authoring/documentation/s2i-mkdocs-container:latest openshift/mkdocs:1.0 --reference-policy=local`. This will create the tag name (`1.0` in this case) if it doesn't already exist. Once the this is tagged we can check it out by running `oc describe istag/mkdocs:1.0 -n openshift`.
In order to have the S2I MkDocs Container appear in the web console application catalog we need to add the `builder` annotation to the image stream so that OpenShift knows it is an S2I builder. To edit to image stream and add annotations we need to run `oc edit is/mkdocs -n openshift`. The annotations should look something like this:
```yaml=
...
...
@@ -34,7 +34,7 @@ spec:
## Resources
* To run the recommended version of the OpenShift client tools we can simply run `docker run -i -t gitlab-registry.cern.ch/paas-tools/openshift-client /bin/bash` and then execute our `oc` commands.
* To run the recommended version of the OpenShift client tools we can simply run `docker run -it gitlab-registry.cern.ch/paas-tools/openshift-client:v3.10.0 /bin/bash` and then execute our `oc` commands.
*[How to Create an S2I Builder Image](https://blog.openshift.com/create-s2i-builder-image/) blog post.
*[Jupyter on OpenShift Part 7: Adding the Image to the Catalog](https://blog.openshift.com/jupyter-on-openshift-part-7-adding-the-image-to-the-catalog/) blog post.
* OpenShift template annotations: `iconClass`: *An icon to be displayed with your template in the web console. Choose from our existing logo icons when possible. You can also use icons from FontAwesome and PatternFly. Alternatively, provide icons through CSS customizations that can be added to an OpenShift Container Platform cluster that uses your template. You must specify an icon class that exists, or it will prevent falling back to the generic icon.*. When using icons from FontAwesome, make sure to select icons from the [appropriate version](https://fontawesome.com/v4.7.0/icons/).