This tutorial shows you how to install the Cloud-Native Toolkit so you can use it to build images. The toolkit only needs to be installed once by the person who manages your development environment or Red Hat OpenShift cluster, and then your whole group can use it.
After installation, you can learn how to build images with the toolkit by following these tutorials:
The Fast-Start Install option is a good option if the main task you want to accomplish with the toolkit is to create images and you already have an OpenShift cluster. This tutorial shows you how to install the Cloud-Native Toolkit into an OpenShift cluster using the Fast Install option. The installed toolkit is contained completely within the OpenShift cluster and uses OpenShift services, including its built-in container image registry.
If you think the Fast-Start Install might not be the best approach for you, explore one of our other install options:
Private Catalog Tiles: For environments within IBM Cloud, you can install the toolkit using tiles in a private catalog similar to installing other software within your account.
Iteration Zero: This is a highly customizable installation that also enables you to install in an environment other than IBM Cloud using Terraform scripts.
Prerequisites for the Fast Install
To use the Fast-Start Install option, you should have access to your OpenShift cluster and be able to log in using the oc login command in a terminal.
Watch and wait while Terraform sets everything up. When it's finished, you will see a message indicating installation is complete:
Expose the registry.
After a pipeline runs successfully, a tagged image is copied to the registry. With Fast-Start Install, the toolkit is contained completely within the OpenShift cluster and uses OpenShift services, including its built-in container image registry. You will want to expose the registry to make it more usable for developers. See Exposing the registry for how to expose the registry with a route.
Note: With an IBM Cloud Private Catalog, Iteration-Zero, or custom install, you can use an external registry such as IBM Cloud Container Registry (ICCR). When you use ICCR, the registry is already exposed outside of the cluster, and the images created by pipelines will be pushed there.
A quick tour of what was installed
The following sections provide an brief overview of what was installed.
The tools project
Use the developer topology view to see what was installed in your tools project. In your OpenShift Web Console:
Use the drop-down to select the Developer perspective in the sidebar.
Click on Topology in the sidebar.
Select the tools project.
Application launcher links
The tools are added to the application launcher drop-down menu in the top navigation bar (shown above). This dropdown is available in all projects.
Developer dashboard
Launch the Developer Dashboard for a dashboard that contains tiles for the applications that you saw in the application launcher and more.
From the dashboard, you have access to:
Tools
Starter Kit repos
Learning resources
Check out the pipelines
You should see that Tekton pipelines have been installed in your tools project:
Next steps
The Cloud-Native Toolkit is now ready for use. Refer to the following tutorials to use the Cloud-Native Toolkit to create a universal application image from a starter kit or an existing application:
About cookies on this siteOur websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising.For more information, please review your cookie preferences options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.