subcollection | copyright | lastupdated | lasttested | ||
---|---|---|---|---|---|
solution-tutorials |
|
2023-10-10 |
2023-10-10 |
{{site.data.keyword.attribute-definition-list}}
{: #tutorials}
Solution tutorials provide step-by-step instructions on how to use IBM Cloud to implement common patterns based on best practices and proven technologies.
Before going through the tutorials collection, this guide will help you set up your development environment to successfully follow the instructions of the guides found in this collection. {: shortdesc}
{: #getting-started-objectives}
Install must-have tools to be productive with {{site.data.keyword.cloud_notm}}:
- {{site.data.keyword.cloud_notm}} CLI - the command line interface to interact with {{site.data.keyword.cloud_notm}} API.
- Docker - to deliver and run software in packages called containers.
- kubectl - a command line interface for running commands against Kubernetes clusters.
- oc - manages OpenShift applications, and provides tools to interact with each component of your system.
- Helm 3 - helps you manage Kubernetes applications — Helm Charts help you define, install, and upgrade even the most complex Kubernetes application.
- Terraform - automates your resource provisioning.
- jq - a lightweight and flexible command-line JSON processor.
- Git - a free and open source distributed version control system.
To avoid the installation of these tools, you can also use the {{site.data.keyword.cloud-shell_short}} from the {{site.data.keyword.cloud_notm}} console. {: tip}
{: #getting-started-windows}
The following sections assume you are running Microsoft Windows 10 64-bit under a user with Administrator privileges. Once you're done with the specific sections, proceed to the configuration common to all operating systems.
{: #getting-started-windows_cli}
-
Download and install the {{site.data.keyword.cloud_notm}} CLI from https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases/latest.
-
Verify the installation with:
ibmcloud version
{: pre}
You may need to restart your machine after the installation. {: tip}
{: #getting-started-windows_docker}
-
Docker Desktop on Windows is one option to run container images on Windows. Make sure to review the terms of the license agreement{: external} before proceeding with the installation.
-
If you don't have one, sign up for a free account at https://hub.docker.com/signup.
-
Download and install Docker Desktop on Windows from https://docs.docker.com/docker-for-windows/install/.
-
Verify the installation with:
docker --version docker run hello-world
{: pre}
You may need to log out and wait for the Docker daemon to be started. {: tip}
{: #getting-started-windows_kubectl}
- Download
kubectl
from https://kubernetes.io/docs/tasks/tools/#install-kubectl-on-windows. - Move
kubectl.exe
binary to your PATH. - Verify the installation with:
{: pre}
kubectl version --client=true
{: #getting-started-windows_oc}
- Download the latest 4.x OpenShift CLI (
oc
) from https://mirror.openshift.com/pub/openshift-v4/clients/ocp/stable/. - Move
oc.exe
binary to your PATH. - Verify the installation with:
{: pre}
oc version
{: #getting-started-windows_helm}
- Download
helm
from https://github.com/helm/helm/releases/latest. - Uncompress the downloaded archive.
- Move
helm.exe
binary to your PATH. - Verify the installation with:
{: pre}
helm version
{: #getting-started-windows_terraform}
- Download
terraform
from https://developer.hashicorp.com/terraform/downloads. - Uncompress the downloaded archive.
- Move the
terraform.exe
binary to your PATH. - Verify the installation with:
{: pre}
terraform version
To manage {{site.data.keyword.cloud_notm}} resources with Terraform, you also need to install the {{site.data.keyword.cloud_notm}} Provider. Starting with Terraform 0.13, the provider can be automatically downloaded from Terraform plugin registry. Follow the instructions in the provider documentation to configure the required_providers
property in your Terraform templates.
{: #getting-started-windows_jq}
- Download jq from https://jqlang.github.io/jq/.
- Rename
jq-win64.exe
tojq.exe
. - Move
jq.exe
binary to your PATH. - Verify the installation with:
{: pre}
jq --version
{: #getting-started-windows_git}
- Download and install
git
from https://github.com/git-for-windows/git/releases/latest. - Verify the installation with:
{: pre}
git --version
Proceed to the configuration common to all operating systems.
{: #getting-started-macos}
The following sections assume you are running macOS High Sierra or later under a user with Administrator privileges. Once you're done with the specific sections, proceed to the configuration common to all operating systems.
{: #getting-started-macos_cli}
- Download and install the {{site.data.keyword.cloud_notm}} CLI from https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases/latest.
- Verify the installation with:
{: pre}
ibmcloud version
{: #getting-started-macos_docker}
- Docker Desktop on Mac is one option to run container images on macOS. Make sure to review the terms of the license agreement{: external} before proceeding with the installation. Other options include Podman{: external}.
- If you don't have one, sign up for a free account at https://hub.docker.com/signup.
- Download and install Docker Desktop on Mac from https://docs.docker.com/docker-for-mac/install/.
- Verify the installation with:
{: pre}
docker --version docker run hello-world
{: #getting-started-macos_kubectl}
-
Download
kubectl
from https://kubernetes.io/docs/tasks/tools/#install-kubectl-on-macos. -
Make the
kubectl
binary executable.chmod +x ./kubectl
{: pre}
-
Move the binary to your PATH.
sudo mv ./kubectl /usr/local/bin/kubectl
{: pre}
-
Verify the installation with:
kubectl version --client=true
{: pre}
{: #getting-started-macos_oc}
-
Download the latest 4.x OpenShift CLI (
oc
) from https://mirror.openshift.com/pub/openshift-v4/clients/ocp/stable/. -
Extract
openshift-client-mac.tar.gz
(Intel) oropenshift-install-mac-arm64.tar.gz
(Apple Silicon):tar zxvf openshift-client-mac*.tar.gz oc
{: pre}
-
Move the
oc
binary to your PATH.sudo mv ./oc /usr/local/bin/oc
{: pre}
-
Verify the installation with:
oc version
{: pre}
macOS Catalina and later may prompt you with a message saying the developer cannot be verified. To allow
oc
to be executed anyway, runsudo xattr -r -d com.apple.quarantine /usr/local/bin/oc
. {: tip}
{: #getting-started-macos_helm}
-
Download
helm
from https://github.com/helm/helm/releases/latest. -
Uncompress the downloaded archive.
-
Move the
helm
binary to your PATH.sudo mv ./darwin-amd64/helm /usr/local/bin/helm
{: pre}
-
Verify the installation with:
helm version
{: pre}
macOS Catalina and later may prompt you with a message saying the developer cannot be verified. To allow
helm
to be executed anyway, runsudo xattr -r -d com.apple.quarantine /usr/local/bin/helm
. {: tip}
{: #getting-started-macos_terraform}
-
Download
terraform
from https://developer.hashicorp.com/terraform/downloads. -
Uncompress the downloaded archive.
-
Move the
terraform
binary to your PATH.sudo mv ./terraform /usr/local/bin/terraform
{: pre}
-
Verify the installation with:
terraform version
{: pre}
To manage {{site.data.keyword.cloud_notm}} resources with Terraform, you also need to install the {{site.data.keyword.cloud_notm}} Provider. Starting with Terraform 0.13, the provider can be automatically downloaded from Terraform plugin registry. Follow the instructions in the provider documentation to configure the required_providers
property in your Terraform templates.
{: #getting-started-macos_jq}
-
Download
jq
from https://jqlang.github.io/jq/. -
Rename the downloaded file to
jq
. -
Make the
jq
binary executable.chmod +x ./jq
{: pre}
-
Move the
jq
binary to your PATH.sudo mv ./jq /usr/local/bin/jq
{: pre}
-
Verify the installation with:
jq --version
{: pre}
macOS Catalina and later may prompt you with a message saying the developer cannot be verified. To allow
jq
to be executed anyway, runsudo xattr -r -d com.apple.quarantine /usr/local/bin/jq
. {: tip}
{: #getting-started-macos_git}
-
Check that
git
is installed:git --version
{: pre}
macOS may prompt you to install the developer tools. These tools include the
git
command line. {: tip}
Proceed to the configuration common to all operating systems.
{: #getting-started-ubuntu}
The following sections assume you are running Ubuntu Linux as non-root user with access to root privileges. Once you're done with the specific sections, proceed to the configuration common to all operating systems. If you are using the Linux-based Cloud Shell, proceed to the section on Cloud Shell.
{: #getting-started-ubuntu_cli}
- Download and install the {{site.data.keyword.cloud_notm}} CLI from https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases/latest.
- Verify the installation with:
{: pre}
ibmcloud version
{: #getting-started-ubuntu_docker}
-
If you don't have one, sign up for a free account at https://hub.docker.com/signup.
-
Install Docker Engine on Ubuntu following the instructions from https://docs.docker.com/engine/install/ubuntu/.
-
Verify the installation with:
docker --version sudo docker run hello-world
{: pre}
To run Docker under your own user instead of root, perfom the post install{: external} steps. {: tip}
{: #getting-started-ubuntu_kubectl}
-
Download
kubectl
from https://kubernetes.io/docs/tasks/tools/#install-kubectl-on-linux. -
Make the
kubectl
binary executable.chmod +x ./kubectl
{: pre}
-
Move the binary to your PATH.
sudo mv ./kubectl /usr/local/bin/kubectl
{: pre}
-
Verify the installation with:
kubectl version --client=true
{: pre}
{: #getting-started-ubuntu_oc}
-
Download the latest 4.x OpenShift CLI (
oc
) from https://mirror.openshift.com/pub/openshift-v4/clients/ocp/stable/. -
Extract
openshift-client-linux.tar.gz
:tar zxvf openshift-client-linux.tar.gz oc
{: pre}
-
Move the
oc
binary to your PATH.sudo mv ./oc /usr/local/bin/oc
{: pre}
-
Verify the installation with:
oc version
{: pre}
{: #getting-started-ubuntu_helm}
-
Download
helm
from https://github.com/helm/helm/releases/latest. -
Uncompress the downloaded archive.
-
Move the
helm
binary to your PATH.sudo mv ./linux-amd64/helm /usr/local/bin/helm
{: pre}
-
Verify the installation with:
helm version
{: pre}
{: #getting-started-ubuntu_terraform}
-
Download
terraform
from https://developer.hashicorp.com/terraform/downloads. -
Uncompress the downloaded archive.
-
Move the
terraform
binary to your PATH.sudo mv ./terraform /usr/local/bin/terraform
{: pre}
-
Verify the installation with:
terraform version
{: pre}
To manage {{site.data.keyword.cloud_notm}} resources with Terraform, you also need to install the {{site.data.keyword.cloud_notm}} Provider. Starting with Terraform 0.13, the provider can be automatically downloaded from Terraform plugin registry. Follow the instructions in the provider documentation to configure the required_providers
property in your Terraform templates.
{: #getting-started-ubuntu_jq}
-
Install
jq
with:sudo apt install jq
{: pre}
-
Verify the installation with:
jq --version
{: pre}
{: #getting-started-ubuntu_git}
-
Install
git
with:sudo apt install git
{: pre}
-
Verify the installation with:
git --version
{: pre}
Proceed to the configuration common to all operating systems.
{: #getting-started-common}
The next sections are common to all operating systems.
{: #getting-started-29}
Plugins extend the capabilities of the {{site.data.keyword.cloud_notm}} CLI with commands specific to a service.
-
Install the following plugins:
ibmcloud plugin install container-registry ibmcloud plugin install cloud-object-storage ibmcloud plugin install kubernetes-service ibmcloud plugin install vpc-infrastructure ibmcloud plugin install code-engine
{: pre}
To see all the available plugins, run
ibmcloud plugin repo-plugins
and to install a pluginibmcloud plugin install <PLUGIN_NAME>
{: tip}
{: #getting-started-common_github}
- Sign up for a free account at https://github.com/.
- Create a new public repository at https://github.com/new to get familiar with GitHub.
{: #getting-started-common_gitlab}
{{site.data.keyword.cloud_notm}} provides you with hosted Git repositories built on GitLab Community Edition and accessible with the same credentials used to log in {{site.data.keyword.cloud_notm}}. It is recommended to configure your SSH public key to simplify the command line interactions with the Git repositories.
- Use these instructions{: external} to generate a new SSH key pair if you don't have one.
- Add your SSH public key{: external} to your Git settings in the region where you plan to host your Git repositories, such as Dallas (us-south.git.cloud.ibm.com){: external}, London (eu-gb.git.cloud.ibm.com){: external} or Frankfurt (eu-de.git.cloud.ibm.com){: external}.
To verify the configuration:
- Create a new private project in GitLab, select the option to initialize the repository with a README.
- Checkout the project from the command line by cloning with the SSH link.
- Update the README file.
- Commit and push the changes.
{: #getting-started-cloud-shell}
{: #getting-started-cloud-shell_oc}
Follow these steps if you need to use another version of the OpenShift CLI than the one pre-installed:
-
Download the latest stable 4.x OpenShift CLI (
oc
)curl https://mirror.openshift.com/pub/openshift-v4/clients/ocp/stable/openshift-client-linux.tar.gz --output oc.tar.gz
{: pre}
-
Extract
oc.tar.gz
:tar zxvf oc.tar.gz oc
{: pre}
-
Add your current directory to
PATH
export PATH=$PWD:$PATH
{: pre}
-
Verify the installation with:
oc version
{: pre}