vania-janet/multiturn-rag-retrieval-data huggingface dataset:
10.176.48.107 Ready <none> 196d v1.26+IKS dal10
10.184.58.23 Ready <none> 2y38d v1.26+IKS dal12
10.184.58.42 Ready <none> 529d v1.26+IKS dal12



 How to fix it 

To resolve this issue, you can either move the istio-ingressgateway pod to the zone that the ibm-cloud-provider-ip pod exists in, or vice versa.



* [Moving the istio-ingressgateway pod](https://cloud.ibm.com/docs/containers?topic=containers-istio_gateway_affinitymove-gateway-pod): The gateway's load balancer retains the same external IP address after it moves. However, in version 1.9 and earlier of the add-on, the changes that you make might be overwritten when the zone labels for gateways are automatically populated during Istio patch updates.
* [Moving the ibm-cloud-provider-ip pod](https://cloud.ibm.com/docs/containers?topic=containers-istio_gateway_affinitymove-ip-pod): The gateway does not retain the same external IP address after it moves, and is assigned a new IP address. However, no changes are overwritten during add-on updates.





 Moving the istio-ingressgateway pod 

Move the istio-ingressgateway pod to the same zone as the ibm-cloud-provider-ip pod.



1. Edit the managed-istio-custom ConfigMap resource.

kubectl edit cm managed-istio-custom -n ibm-operators
2. For the gateway that you want to move, change the istio-ingressgateway-zone-1|2|3 setting to the zone where the ibm-cloud-provider-ip pod exists.
3. Save and close the configuration file. The istio-ingressgateway pod is moved to a worker node in the same zone as the ibm-cloud-provider-ip pod, and the ibm-cloud-provider-ip pod properly deploys.
4.
Why does binding a service to a cluster result in a same name error? 

Virtual Private Cloud

Classic infrastructure

  What’s happening 

When you run ibmcloud ks cluster service bind --cluster <cluster_name> --namespace <namespace> --service <service_instance_name>, you see the following message.

Multiple services with the same name were found.
Run 'ibmcloud service list' to view available Bluemix service instances...

  Why it’s happening 

Multiple service instances might have the same name in different regions.

  How to fix it 

Use the service GUID instead of the service instance name in the ibmcloud ks cluster service bind command.



1.  [Log in to the IBM Cloud region that includes the service instance to bind.](https://cloud.ibm.com/docs/containers?topic=containers-regions-and-zonesbluemix_regions)
2.  Get the GUID for the service instance.

ibmcloud service show <service_instance_name> --guid

Example output

Invoking 'cf service <service_instance_name> --guid'...
<service_instance_GUID>
3.  Bind the service to the cluster again.

ibmcloud ks cluster service bind --cluster <cluster_name> --namespace <namespace> --service <service_instance_GUID>
The MotionPro Plus clients, located in the [Apple Store](https://apps.apple.com/us/app/motionpro-plus/id1218085720?mt=12), are not supported.



1. Open the Mac MotionPro or MotionPro Plus application.
2. Click Profile, then Create. The Create Profile window shows.
3. Enter the following information:



* Profile Name
* Virtual Site Host
* Virtual Site Port
* User Name
* Password



4. Select the newly created profile, then click Connect. Status shows Connecting.



If the tunnel isn't directing traffic correctly, you might need to [add routes manually](https://discussions.apple.com/thread/2735376).
Reset the IAM API key for that region or resource group: ibmcloud ks api-key reset --region <region>.
5. Review that the API key was set: ibmcloud ks api-key info --cluster <roks_cluster_in_location>.
6. [Open a support case](https://cloud.ibm.com/docs/satellite?topic=satellite-get-help) and ask that the location that contains the cluster to be refreshed. Include your location ID, which you can find by running the ibmcloud sat location ls command.



: If your location does not have any clusters, then you cannot reset the API key yourself. Instead, [open a support case](https://cloud.ibm.com/docs/satellite?topic=satellite-get-help) and ask for your location to be refreshed. Include your location ID, which you can find by running the ibmcloud sat location ls command.





 R0050, R0051: Satellite Link connector issues 

Location message
: The Link connector is experiencing token authentication issues. Contact IBM Cloud Support and include your Satellite location ID.
: The Link connector cannot retrieve the location ID. Contact IBM Cloud Support and include your Satellite location ID.

Steps to resolve
: [Open a support case](https://cloud.ibm.com/docs/satellite?topic=satellite-get-help) and include your Satellite location ID.





 R0052: Ingress certificate generation issues 

Location message
: Ingress certificates have not been generated for the location endpoints.

Steps to resolve
: IBM Cloud Support is notified and is working to resolve the issue. Try again later.





 R0056: Pod status stuck in terminating 

Location message
: Pods have been stuck in a terminating state on the location control plane node for over an hour.

Steps to resolve
: Pods that remain in a terminating state for an hour or more indicate that the location control plane is not healthy. Follow the steps to replace the location control plane hosts.

When you update or replace control plane hosts, do not assign or remove multiple hosts at the same time as doing so may break the control plane.
If the state of the PVC shows Pending, retrieve the error for why the PVC remains pending.

oc describe pvc <pvc_name>
3. Review common errors that can occur during the PVC creation.



* [File storage and classic block storage: PVC remains in a pending state](https://cloud.ibm.com/docs/openshift?topic=openshift-file_pvc_pending)
* [Object storage: PVC remains in a pending state](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_pvc_pending)



4. Review common errors that can occur when you mount a PVC to your app.



* [File storage: App can't access or write to PVC](https://cloud.ibm.com/docs/openshift?topic=openshift-file_app_failures)
* [Classic Block storage: App can't access or write to PVC](https://cloud.ibm.com/docs/openshift?topic=openshift-block_app_failures)
* [Object storage: Accessing files with a non-root user fails](https://cloud.ibm.com/docs/openshift?topic=openshift-cos_nonroot_access)



5. Verify that the kubectl CLI version that you run on your local machine matches the Kubernetes version that is installed in your cluster. If you use a kubectl CLI version that does not match at least the major.minor version of your cluster, you might experience unexpected results. For example, [Kubernetes does not support kubectl client versions that are 2 or more versions apart from the server version (n +/- 2).



1. Show the kubectl CLI version that is installed in your cluster and your local machine.

oc version

Example output
* [Step 3: Review the cluster autoscaler status](https://cloud.ibm.com/docs/containers?topic=containers-debug_cluster_autoscalerca-debug-status)
* [Step 4: Check the cluster autoscaler pod](https://cloud.ibm.com/docs/containers?topic=containers-debug_cluster_autoscalerca-debug-pod)
* [Step 5: Search the pod logs](https://cloud.ibm.com/docs/containers?topic=containers-debug_cluster_autoscalerca-debug-pod-logs)
* [Step 5: Restart the pod](https://cloud.ibm.com/docs/containers?topic=containers-debug_cluster_autoscalerca-debug-pod-restart)
* [Step 6: Disable and reenable](https://cloud.ibm.com/docs/containers?topic=containers-debug_cluster_autoscalerca-debug-disable)
* [Step 8: Check if the issue is resolved](https://cloud.ibm.com/docs/containers?topic=containers-debug_cluster_autoscalerca-debug-more)



[Autoscaling fails after API key reset](https://cloud.ibm.com/docs/containers?topic=containers-ts-storage-ca-apikey-resetts-storage-ca-apikey-reset)

[Why can't I resize or rebalance my worker pool?](https://cloud.ibm.com/docs/containers?topic=containers-ts-ca-resizets-ca-resize)

[Why are my autoscaled worker pools unbalanced?](https://cloud.ibm.com/docs/containers?topic=containers-ts-ca-unbalancedts-ca-unbalanced)





 Cluster network 

[Why does DNS resolution fail when CoreDNS pods are restarted?]
If the state of the PVC shows Pending, retrieve the error for why the PVC remains pending.

kubectl describe pvc <pvc_name>
3. Review common errors that can occur during the PVC creation.



* [File storage and classic block storage: PVC remains in a pending state](https://cloud.ibm.com/docs/containers?topic=containers-file_pvc_pending)
* [Object storage: PVC remains in a pending state](https://cloud.ibm.com/docs/containers?topic=containers-cos_pvc_pending)



4. Review common errors that can occur when you mount a PVC to your app.



* [File storage: App can't access or write to PVC](https://cloud.ibm.com/docs/containers?topic=containers-file_app_failures)
* [Classic Block storage: App can't access or write to PVC](https://cloud.ibm.com/docs/containers?topic=containers-block_app_failures)
* [Object storage: Accessing files with a non-root user fails](https://cloud.ibm.com/docs/containers?topic=containers-cos_nonroot_access)



5. Verify that the kubectl CLI version that you run on your local machine matches the Kubernetes version that is installed in your cluster. If you use a kubectl CLI version that does not match at least the major.minor version of your cluster, you might experience unexpected results. For example, [Kubernetes does not support kubectl client versions that are 2 or more versions apart from the server version (n +/- 2).



1. Show the kubectl CLI version that is installed in your cluster and your local machine.

kubectl version

Example output
[Update your add-on to the latest version](https://cloud.ibm.com/docs/containers?topic=containers-managed-addonsupdating-managed-add-ons). 
 H1510 Cluster resources low, not enough workers in Ready state. The add-on is not ready to be used for one of the following reasons:<br><br><br><br> * The cluster does not meet the size criteria for the add-on.<br> * Worker nodes in your cluster are not in a Normal state. [Review the worker nodes' state and status](https://cloud.ibm.com/docs/containers?topic=containers-debug_worker_nodes).<br><br><br> 
 <br><br> * <br><br><br> Enabling The add-on is currently deploying to the cluster. Note that the add-on might take up to 15 minutes to install. 
 H1512 Addon daemonset may not be available on all Ready nodes. For the static route add-on: The static route operator DaemonSet is not available on any worker nodes, which prevents you from applying static route resources. Your worker nodes can't run the static route operator DaemonSet for the following reasons:<br><br><br><br> * One or more worker nodes reached their [resource limits](https://cloud.ibm.com/docs/containers?topic=containers-debug_worker_nodes).<br> * One or more worker nodes are running the [maximum number of pods per worker node](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_limitationsclassic_limits).<br><br><br>
[CSR created](https://cloud.ibm.com/docs-content/v1/content/4c9a07fe500838e5e55e71e73131ef20b44a6c66/event-notifications/images/en-apns-p12-csr-created.png)

Figure 17. CSR created
* Go back to the Apple developer portal, for the Upload CSR file option, click Choose File, and select file CertificateSigningRequest.certSigningRequest. Click Continue.

Zoom

![Upload CSR file](https://cloud.ibm.com/docs-content/v1/content/4c9a07fe500838e5e55e71e73131ef20b44a6c66/event-notifications/images/en-apns-p12-upload-csr.png)

Figure 18. Upload CSR file
* Click Download. The aps_development.cer file is downloaded.

Zoom

![Download certificate](https://cloud.ibm.com/docs-content/v1/content/4c9a07fe500838e5e55e71e73131ef20b44a6c66/event-notifications/images/en-apns-p12-download-cer.png)

Figure 19. Download certificate
* Locate your newly installed certificate. Double-click the certificate to install it into the Keychain Access.
* On your Mac, go to Keychain Access > My Certificates.
* Select the certificate and private key, and then select Export to convert the certificate into the personal information exchange format (.p12 format).

Zoom

!
Service configuration properties are incorrect 

  What’s happening 

Your properties are not being set correctly. For example, the incorrect namespace is targeted.

  Why it’s happening 

When a property is set, it is retained on your workstation at <home_dir>/.bluemix/plugins/cloud-functions/config.json.

  How to fix it 

You might review your properties by using the ibmcloud fn property get --all command. You might need to run ibmcloud fn property unset --<property> to unset a specific property, then reset it. Or you might unset all properties by deleting the config.json file. This config file is re-created when you work with the service, for example, when you run ibmcloud fn property get --all.
List the deployments in the kube-system namespace.

kubectl get deployments -n kube-system
4. Disable ALBs that don't have a deployment by using the ibmcloud ks ingress alb disable[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_alb_disable).
5. Wait 10 minutes.
6. Re-enable ALBs by using the ibmcloud ks ingress alb enable[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_alb_configure).
7. Wait 15-20 minutes, then check if the deployments are created.

kubectl get deployments -n kube-system
8. If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar). In the case details, be sure to include any relevant log files, error messages, or command outputs.
If the command returns ibm.io/object-store-endpoint: NA, your cluster is deployed in a location that is supported in Red Hat OpenShift on IBM Cloud but is not yet supported by the IBM Cloud Object Storage plug-in. To add the location to the Red Hat OpenShift on IBM Cloud, post a question in our public Slack or open an IBM Cloud support case. For more information, see [Getting help and support](https://cloud.ibm.com/docs/openshift?topic=openshift-getting_help_storage).
2. If you manually added the s3fs API endpoint with the ibm.io/endpoint annotation or the IAM API endpoint with the ibm.io/iam-endpoint annotation in your PVC, make sure that you added the endpoints in the format https://<s3fs_api_endpoint> and https://<iam_api_endpoint>. The annotation overwrites the API endpoints that are automatically set by the ibmc plug-in in the IBM Cloud Object Storage storage classes.

oc describe pvc <pvc_name>
[Update your add-on to the latest version](https://cloud.ibm.com/docs/containers?topic=containers-managed-addonsupdating-managed-add-ons), or see specific update steps for [Istio](https://cloud.ibm.com/docs/containers?topic=containers-istioistio_update). 
 H1510 Cluster resources low, not enough workers in Ready state. The add-on is not ready to be used for one of the following reasons:<br><br><br><br> * The cluster does not meet the size criteria for the add-on. For example, check the size requirements for [Istio](https://cloud.ibm.com/docs/containers?topic=containers-istioistio_install).<br> * Worker nodes in your cluster are not in a Normal state. [Review the worker nodes' state and status](https://cloud.ibm.com/docs/containers?topic=containers-debug_worker_nodes).<br><br><br> 
 <br><br> * <br><br><br> Enabling The add-on is currently deploying to the cluster. Note that the add-on might take up to 15 minutes to install. 
 H1512 Addon daemonset may not be available on all Ready nodes. For the static route add-on: The static route operator DaemonSet is not available on any worker nodes, which prevents you from applying static route resources. Your worker nodes can't run the static route operator DaemonSet for the following reasons:<br><br><br><br> * One or more worker nodes reached their [resource limits](https://cloud.ibm.com/docs/containers?topic=containers-debug_worker_nodes).<br> * One or more worker nodes are running the [maximum number of pods per worker node](https://cloud.ibm.com/docs/containers?topic=containers-limitationsclassic_limits).<br><br><br>
Please login to cloud console to find more information","ibmenfcmbody": "{"notification":{"title":"Hello, Tag","time_to_live":100}}",
"ibmenapnsbody": "{"en_data":{"alert":"alert"},"aps":{"alert":{"loc-args":"Shelly","Rick"],"action-loc-key":"key","launch-image":"image.png","loc-key":"GAME_PLAY_REQUEST_FORMAT","subtitle":"Tes Sub apns 9","summary-arg":"apnsGroupSummaryArg","body":"Pradeep Notification 10","title-loc-key":"titleLocKey","title":"Test apns 9","summary-arg-count":1,"title-loc-args":null},"badge":9,"sound":"bingbong.aiff","category":"interactiveCategory","thread-id":"12","mutable-content":1},"url":"https","apns-collapse-id":"10","attachment-url":"some url"}",
If you created service bindings for an app or job in a Code Engine project that was created before the release of [project-wide settings in the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-codeengine-relnotescodeengine-apr2623), ignore the warning message. Service binding operations will continue to work because service bindings were previously created. Do not remove and reconfigure service binding operations configurations from the Integrations page in the console because this action does not delete the original service ID and can cause a security risk.



For more information about working with service bindings, see [Working with service bindings to integrate IBM Cloud services with Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-service-binding) and [Configuring project-wide service binding operations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-project-integrationsprojectintegration-sb).
: Ensure you move to [The IBM Cloud provider v1.33.0](https://github.com/IBM-Cloud/terraform-provider-ibm/releases/tag/v1.34.0) that replaces the [dependency](https://github.com/dgrijalva/jwt-go) of JSON web tokens with the [latest version](https://github.com/golang-jwt/jwt) to remediate[CVE-2020-26160](https://github.com/IBM-Cloud/terraform-provider-ibm/pull/3191) vulnerability.

Increasing FAQs
: [Terraform supports more FAQs](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-faqs).
If a pod requires access to the dashboard metrics scraper, deploy the pod in a namespace that has the dashboard-metrics-scraper-policy: allow label. For more information, see [Controlling traffic with network policies](https://cloud.ibm.com/docs/containers?topic=containers-network_policies). 
 Resolve non-deterministic behavior of owner references Kubernetes garbage collector is updated to resolve non-deterministic behavior of owner references. Before you update your cluster, review the [Kubernetes community recommendation](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.20.mdurgent-upgrade-notes) that you run the [kubectl-check-ownerreferences](https://github.com/kubernetes-sigs/kubectl-check-ownerreferences) tool to locate existing objects with invalid owner references. 
 Unsupported: Service service.alpha.kubernetes.io/tolerate-unready-endpoints annotation Services no longer support the service.alpha.kubernetes.io/tolerate-unready-endpoints annotation. The annotation has been deprecated since Kubernetes version 1.11 and has been replaced by the spec.publishNotReadyAddresses field. If your services rely on this annotation, update them to use the spec.publishNotReadyAddresses field instead. For more information on this field, see [DNS for Services and Pods](https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/). 
 VPC clusters: App URL character length DNS resolution is managed by the cluster's [virtual private endpoint (VPE)](https://cloud.ibm.com/docs/containers?topic=containers-vpc-subnetsvpc_basics_vpe), which can resolve URLs up to 130 characters. If you expose apps in your cluster with URLs, such as the Ingress subdomain, ensure that the URLs are 130 characters or fewer. 







 Update after master
For this case, service binding operations are configured such that you can create and manage service bindings; however, the system cannot display details of service binding operations from the project-wide Integrations page and you continue to see the warning message.



1. Review the list of service IDs in IBM Cloud® Identity and Access Management (IAM) to help you determine the custom service ID that was used with the project update command. From the IBM Cloud console, go to Manage > Access (IAM), and select Service IDs.
2. After you identify the service ID that was used with the project update command, use the Code Engine console to assign the same custom service ID to the operator secret.
3. Go to the Integrations page in the console. After you select your project from the [Projects page in the Code Engine console](https://cloud.ibm.com/codeengine/projects), click Project settings > Integrations. The configuration status is Configured.
4. Click Remove configuration. This action removes the existing operator secret, and the configuration status is Not Configured.
5. Click Configure to configure service binding operations and select the option to use a custom service ID.
6. Select your custom service ID from the table. Use the custom service ID that you identified in the first step.
7. Click Configure to save this configuration.





After service binding operations are configured with your custom service ID, you can view details of the configuration.



2. If you created service bindings for an app or job in a Code Engine project that was created before the release of [project-wide settings in the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-codeengine-relnotescodeengine-apr2623), ignore the warning message. Service binding operations will continue to work because service bindings were previously created. Do not remove and reconfigure service binding operations configurations from the Integrations page in the console because this action does not delete the original service ID and can cause a security risk.
DISCLAIMER THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM OTHER DEALINGS IN THE FONT SOFTWARE.



* FONTAWESOME [smartystreets/goconvey] (Copyright (c) 2016 SmartyStreets, LLC)([https://github.com/smartystreets/goconvey/tree/v1.6.4](https://github.com/smartystreets/goconvey/tree/v1.6.4))
* OFL.TXT [smartystreets/goconvey] (Copyright (c) 2016 SmartyStreets, LLC)([https://github.com/smartystreets/goconvey/tree/v1.6.4](https://github.com/smartystreets/goconvey/tree/v1.6.4))











 Trademarks 

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at [Copyright and trademark information](https://www.ibm.com/legal/copytrade).

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

The Android robot is reproduced or modified from work created and shared by Google and used according to terms described in the [Creative Commons 3.0 Attribution License](https://creativecommons.org/licenses/by/3.0/).