Upgrade
Update an existing IBM Bob on-premises deployment to a newer release while preserving the current configuration.
Before you begin
Complete the following tasks before starting the upgrade:
Ensure that the existing config.yaml file is available.
If the target version includes new container images and you are using a private registry, mirror the required images before starting the upgrade.
Regenerate the cluster-scoped resources for the target release:
./bobctl generate-cluster-resourcesReview the generated work/cluster-resources.yaml file before applying it to confirm the changes are expected for your environment.
Apply the resources:
oc apply -f work/cluster-resources.yaml --server-side --force-conflictsUpgrade the deployment
Replace the existing release bundle with the new version, then run:
./bobctl upgradeThe upgrade process uses the existing config.yaml file and performs the following actions:
- Validates cluster connectivity and namespace availability.
- Verifies image pull secret configuration.
- Applies Helm chart updates.
- Preserves existing configuration values.
| Option | Description |
|---|---|
--dry-run | Displays the changes that would be applied without performing the upgrade. |
Verify the upgrade
After the upgrade completes, verify the deployment status.
Check the operator pods:
oc get pods -n <operator-namespace>Check the Bob instance status and version:
oc get bob -n <instance-namespace>View the operator logs:
oc logs -n <operator-namespace> deployment/ibm-bob-operator -fEnsure that all pods are running successfully and that the Bob custom resource reports the expected version.
TLS certificates
Configure external TLS certificates for IBM Bob on-premises so that bob-ide and bob-shell clients can connect securely.
Model Gateway overview
Learn how Bob on-premises uses the model-gateway.yaml and config.yaml files to securely configure model endpoints, credentials, and TLS certificates for Model Gateway access.