IBM CloudPak for Data: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
== Installing the CLI == | |||
Before using CPD, set up the required CLI tools on a Linux VM, jump server, or bastion host. This approach is often more reliable than running the tools locally on a Mac with Docker or Podman. | |||
Download the required binaries: | |||
<source lang="bash"> | |||
wget https://github.com/IBM/cpd-cli/releases/download/v12.0.5/cpd-cli-linux-EE-12.0.5.tgz | |||
wget https://mirror.openshift.com/pub/openshift-v4/clients/oc/4.6/linux/oc.tar.gz | |||
</source> | |||
== Getting an OpenShift Login Token == | == Getting an OpenShift Login Token == | ||
| Line 24: | Line 36: | ||
./cpd-cli manage login-to-ocp --token=sha256~xxxxxxxxxxxxxxxxxxxxxxxx --server=https://api.cluster.example.com:6443 | ./cpd-cli manage login-to-ocp --token=sha256~xxxxxxxxxxxxxxxxxxxxxxxx --server=https://api.cluster.example.com:6443 | ||
</syntaxhighlight> | </syntaxhighlight> | ||
== Create the Global Pull Secret == | |||
The global pull secret is required to allow OpenShift to pull images from the IBM container registry using your entitlement key. | |||
Run the following command: | |||
<source lang="bash"> | |||
export IBM_ENTITLEMENT_KEY=..... | |||
./cpd-cli manage add-icr-cred-to-global-pull-secret ${IBM_ENTITLEMENT_KEY} | |||
</source> | |||
On ROKS, worker nodes may need to be reloaded before the updated pull secret takes effect. To speed up the process, you can temporarily reduce the worker pool to a single node before applying the change. | |||
= Veja também= | = Veja também= | ||
Revision as of 21:14, 29 July 2026
Installing the CLI
Before using CPD, set up the required CLI tools on a Linux VM, jump server, or bastion host. This approach is often more reliable than running the tools locally on a Mac with Docker or Podman.
Download the required binaries:
wget https://github.com/IBM/cpd-cli/releases/download/v12.0.5/cpd-cli-linux-EE-12.0.5.tgz
wget https://mirror.openshift.com/pub/openshift-v4/clients/oc/4.6/linux/oc.tar.gz
Getting an OpenShift Login Token
You can obtain your OpenShift API token from the OpenShift web console:
- Log in to the OpenShift console.
- Click your username in the upper-right corner.
- Select Copy login command.
- Authenticate again if prompted.
- Copy the token from the displayed oc login command.
Example:
oc login --token=sha256~xxxxxxxxxxxxxxxxxxxxxxxx --server=https://api.cluster.example.com:6443
Logging in to OpenShift with cpd-cli
After starting the container, log in to OpenShift using cpd-cli.
Provide the following command:
./cpd-cli manage login-to-ocp --token=sha256~xxxxxxxxxxxxxxxxxxxxxxxx --server=https://api.cluster.example.com:6443
Create the Global Pull Secret
The global pull secret is required to allow OpenShift to pull images from the IBM container registry using your entitlement key.
Run the following command:
export IBM_ENTITLEMENT_KEY=.....
./cpd-cli manage add-icr-cred-to-global-pull-secret ${IBM_ENTITLEMENT_KEY}
On ROKS, worker nodes may need to be reloaded before the updated pull secret takes effect. To speed up the process, you can temporarily reduce the worker pool to a single node before applying the change.