Does the IBM Cloud Kubernetes Service Ingress annotation for public IP type work identically in local kind and production clusters?

Goal: Deploy a simple web service in an IBM Cloud Kubernetes Service cluster and expose it using an IBM Cloud Load Balancer (ALB) by setting the service annotation service.kubernetes.io/ibm-load-balancer-cloud-provider-ip-type: public. The same manifest works without error in a local kind cluster, where the service receives a routable IP and the application is reachable.

In the production IBM Cloud Kubernetes Service cluster, the service remains in a pending state or receives no external IP, and the application is not accessible despite the annotation being present. The cluster is configured with a standard VPC, worker nodes have public gateway enabled, and the IAM policy for the service account includes the Container Service Operator role.

What additional configuration or permissions are required for the annotation to take effect in IBM Cloud Kubernetes Service? Does the annotation behave differently based on the cluster's VPC or resource group? Are there known limitations or version‑specific behaviors for this annotation in IBM Cloud Kubernetes Service?