This repository will not be updated. The repository will be kept available in read-only mode.
The IBM Starter Kit Collection for OpenShift installs new IBM templates into the Developer Catalog for an OpenShift cluster, so developers can easily find and use them. All the templates in this collection run on OpenShift and have the ability to automatically provision and use managed services from the IBM Cloud public catalog.
This Collection is currently in Beta.
These starter kits are included in the deployment:
- Node.js Express App
- Go Gin App
- Python Flask App
- Python Django App
- Java Spring App
- Node.js + Cloudant App
- Text to Speech Node.js App
- Speech to Text Node.js App
- Visual Recognition Node.js App
- Natural Language Understanding Node.js App
- Log in to IBM Cloud and connect to your OpenShift cluster.
- Be sure your cluster has the IBM Cloud Operator installed. If it doesn't, have your cluster admin install it.
- Download and run this bash script. Be sure make the script executable
chmod +x install.sh. - When the script completes, wait a few minutes and then reload the Developer Catalog in your cluster console. Filter on publisher 'IBM' to find the newly installed starter kits.
Installation tips:
- The new template will appear in the Developer Catalog for the
defaultproject for your cluster. You can add the starters to other projects by modifying the install script to include the '-n' flag. For example,oc apply -f templates/go-gin-app.json -n test_projectwill install the starter in the project named 'test_project', andoc apply -f templates/go-gin-app.json -n openshiftwill install the starter into the cluster Service Catalog.- If you would like to uninstall a single starter, you can run the oc delete command from your terminal:
oc delete -f templates/go-gin-app.json -n test_project- If you would like to uninstall all the starters in the collection, you can download and run the uninstall script.
- Note the instructions for the IBM Cloud Operator installation script say to log in to IBM Cloud and target a resource group before running the script. The is important because all the IBM Cloud services that are provisioned by the Operator will go into the resource group from which you installed the Operator. Administrators should be certain they are targeting the intended resource group as they install the Operator.
Every time I invoke my IBM starter kit template, I see duplicate instances of the associate services provisioned on IBM Cloud. What is going on?
There are probably two IBM Cloud Operators installed on your cluster. This might occure if your admin installed using the install-operator.sh script and installed with the Red Hat Operator Life Cycle Manager (OLM). This would give you two operators, one in the current namespace (e.g. default) and one in the openshift-operators namespace. If that is the case, remove the unwanted deployment.
This sample application is licensed under the Apache License, Version 2. Separate third-party code objects invoked within this code pattern are licensed by their respective providers pursuant to their own separate licenses. Contributions are subject to the Developer Certificate of Origin, Version 1.1 and the Apache License, Version 2.