You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+33Lines changed: 33 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -240,6 +240,39 @@ During cluster provisioning a containers apikey is created if one does not alrea
240
240
241
241
To workaround the issue simply attempt a re-apply of the terraform and it should pass on second attempt. If you still face issues, an IBM Cloud support case should be created with the `Kubernetes service` and include the `incidentID` from the error.
242
242
243
+
#### The entitlement 'cloud_pak' was not found
244
+
When provisioning this module, you might encounter the following error during the Terraform apply phase if a value has been set for ocp_entitlement.
245
+
246
+
```
247
+
2025/10/20 14:28:57 Terraform apply | with module.ocp_base.ibm_container_vpc_cluster.cluster[0],
248
+
2025/10/20 14:28:57 Terraform apply | on ../../main.tf line 140, in resource "ibm_container_vpc_cluster" "cluster":
This error typically occurs when the OpenShift cluster API key for the target region and resource group is invalid, expired, or not properly associated with the required entitlement.
268
+
269
+
To resolve this issue, Replace the API key for all clusters in the specified region and targeted resource group.
270
+
```
271
+
ibmcloud target -g <resource-group>
272
+
ibmcloud oc api-key reset --region <region>
273
+
```
274
+
275
+
243
276
#### New kube_version message
244
277
245
278
- When you run a `terraform plan` command, you might get a message about a new version of Kubernetes, as in the following example:
0 commit comments