vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Why can't I connect to my Red Hat OpenShift API Satellite link endpoint? 

  What’s happening 

I can't connect to my Red Hat OpenShift API Satellite link endpoint. I was able to before, what changed?

  Why it’s happening 

By default, your Red Hat OpenShift API Satellite link endpoints are protected. To access your link endpoints, you must configure a source list for your endpoint.

  How to fix it 

To configure a source list for your endpoint, follow these steps.



1.  From the [Satellite Locations dashboard](https://cloud.ibm.com/satellite/locations), click the name of your location.
2.  From the Link endpoints tab, click the name of your endpoint.
3.  In the Source list section, click Add source.
4.  Click Configure source to enter a source name and the IP address or subnet CIDR for the client that you want to connect to the endpoint, and click Add.
5.  Use the toggle to enable the source to connect to the destination resource. After you enable a source, network traffic to the destination through the endpoint is permitted only from clients that use an IP address in the range that you specified in the source. Network traffic from other clients that is sent to the destination resource through the endpoint is blocked.
6.  Repeat these steps for any sources that you want to grant access to the destination resource through the endpoint.



You can find the Red Hat OpenShift API Satellite link endpoint by looking in the IBM Cloud Log Analysis logs for your Satellite location.
Updated image for [CVE-2021-33194](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33194). 
 Red Hat OpenShift 4.7.12 4.7.16 See the [Red Hat OpenShift release notes](https://docs.openshift.com/container-platform/4.7/release_notes/ocp-4-7-release-notes.htmlocp-4-7-16). 
 Red Hat OpenShift Control Plane Operator v4.7.0-20210512 v4.7.0-20210608 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20210608). 
 OpenVPN Operator image v1.3.2 v1.3.3 Updated ansible operator base image to version 1.8.0 to resolve CVEs. 
 Portieris admission controller v0.10.2 v0.10.3 See the [Portieris admission controller release notes](https://github.com/IBM/portieris/releases/tag/v0.10.3). 
 Red Hat OpenShift on IBM Cloud Metrics Server v4.7.0-20210512 v4.7.0-20210608 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20210608). 
 Red Hat OpenShift on IBM Cloud toolkit 4.7.0+20210512 4.7.0+20210608 See the [Red Hat OpenShift on IBM Cloud toolkit release notes](https://github.com/openshift/ibm-roks-toolkit/releases/tag/v4.7.0+20210608).
* For Red Hat OpenShift hosts, the NO_PROXY for Red Hat OpenShift hosts must include the first IP of the service subnet that is used for the Red Hat OpenShift cluster. To find this IP, run the cluster get command.

ibmcloud ks cluster get --cluster <ClusterID>

Example output

Name: hyp-20220306-1-d2
ID: <ClusterID>
...
Service Subnet: 172.21.0.0/16
...

From this output, note that the first IP is 172.21.0.1, which makes the full output for hosts associated with this specific cluster in this example NO_PROXY=172.20.0.1,172.21.0.1,$REDHAT_PACKAGE_MIRROR_LOCATION for RHEL hosts and NO_PROXY=172.20.0.1,172.21.0.1,.REGION.satellite.appdomain.cloud for RHCOS hosts. For example, NO_PROXY=172.20.0.1,172.21.0.1,.eu-gb.satellite.appdomain.cloud is correct for a London mirror location for RHCOS hosts. Note that the RHCOS value includes . before the region.

Remember that any traffic to cluster services from the worker node must be included in NO_PROXY. For example, to use the image registry service to store images, add image-registry.openshift-image-registry.svc to NO_PROXY for each worker node; this value doesn't need to be included for the control plane.



3. Navigate to /etc/systemd/system.conf.d on your host. If that file does not exist, create it with the following command. Enter the <VALUE> for NO_PROXY from step 2.

mkdir -p /etc/systemd/system.conf.d
cat >"/etc/systemd/system.conf.d/proxy.conf" <<EOF
[Manager]
DefaultEnvironment="HTTP_PROXY=xxxx" "HTTPS_PROXY=xxxx" "NO_PROXY=<VALUE>"
Another benefit is that copies of the pulled images from Container Registry are stored locally on the cluster, therefore reducing latency and external traffic, but you are subject to storage limitations.

To set up your Red Hat OpenShift on IBM Cloud clusters to use the internal registry in combination with Container Registry, see the following topics in the Red Hat OpenShift on IBM Cloud documentation:



* [Importing images from IBM Cloud Container Registry into the internal registry image stream](https://cloud.ibm.com/docs/openshift?topic=openshift-registryimagestream_registry).
* [Setting up builds in the internal registry to push images to IBM Cloud Container Registry](https://cloud.ibm.com/docs/openshift?topic=openshift-registrybuilds_registry).







 Set up Red Hat OpenShift Container Platform to use Container Registry 

To set up Red Hat OpenShift Container Platform, you must create secrets that have the credentials to access Container Registry so that you can perform the following actions.



* Pull Create image pull secrets to [pull images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_rhosregistry_rhos_os_pull) from Container Registry to your Red Hat OpenShift cluster. For example, you might deploy an app that uses an image in a private registry.
* Push Create image push secrets to [push images](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_rhosregistry_rhos_os_push) from your Red Hat OpenShift cluster to a repository in Container Registry. For example, you might set up a continuous delivery pipeline that builds an image to a private registry instead of the internal registry.
* Both Create a secret that can pull images from and push images to Container Registry. For example, you might set up a continuous delivery pipeline that builds an image to a private registry so that your team can pull the most recent image across multiple clusters.





 Set up the Red Hat OpenShift Container Platform internal registry to pull from Container Registry 

To configure Red Hat OpenShift Container Platform to pull from Container Registry, you must complete the following steps:



1.
Red Hat OpenShift on IBM Cloud partners 

To provide you with all the capabilities that you need to run production workloads in the cloud, Red Hat OpenShift on IBM Cloud partners with other third-party service providers to enhance your cluster with logging, monitoring, and storage tools.

Review the list of partners and the benefits of each solution that they provide. To find other proprietary IBM Cloud and third-party open source services that you can use in your cluster, see [Understanding IBM Cloud and 3rd party integrations](https://cloud.ibm.com/docs/openshift?topic=openshift-ibm-3rd-party-integrations).



 Portworx 

[Portworx](https://portworx.com/products/portworx-enterprise//) is a highly available software-defined storage solution that you can use to manage local persistent storage for your containerized databases and other stateful apps, or to share data between pods across multiple zones.

An software defined storage (SDS), such as Portworx, solution abstracts storage devices of various types, sizes, or from different vendors that are attached to the worker nodes in your cluster. Worker nodes with available storage on hard disks are added as a node to a storage cluster. In this cluster, the physical storage is virtualized and presented as a virtual storage pool to the user. The storage cluster is managed by the SDS software. If data must be stored on the storage cluster, the SDS software decides where to store the data for highest availability. Your virtual storage comes with a common set of capabilities and services that you can leverage without caring about the actual underlying storage architecture.



 Benefits 

Review the following table to find a list of key benefits that you can get by using Portworx.



Benefits of using Portworx

 Benefit Description 

 Cloud native storage and data management for stateful apps Portworx aggregates available local storage that is attached to your worker nodes and that can vary in size or type, and creates a unified persistent storage layer for containerized databases or other stateful apps that you want to run in the cluster. By using Kubernetes persistent volume claims (PVC), you can add local persistent storage to your apps to store your data.
* IBM® Secure Gateway for IBM Cloud® is used to create a secure tunnel to on-premises systems that host the benefits systems.
* Combination of on-premises data and Red Hat OpenShift on IBM Cloud lets them access sensitive data while they adhere to regulations.
* Chatbot conversations fed back into HR policies, allowing the benefits site to reflect which benefits were most and least popular, including targeted improvements to poorly performing initiatives.







 Step 3: Chatbot and personalization 

Watson Assistant provides tools to quickly scaffold a chatbot that can provide the correct benefits information to users.





 Step 4: Deliver continuously across the globe 



* IBM Cloud® Continuous Delivery helps Developers to quickly provision an integrated toolchain, by using customizable, shareable templates with tools from IBM, third parties, and open source. Automate builds and tests, controlling quality with analytics.
* After Developers build and test the apps in their Development and Test clusters, they use the IBM CI/CD toolchains to deploy apps into Production clusters across the globe.
* Red Hat OpenShift on IBM Cloud provides easy rollout and roll-back of apps. Tailored apps are deployed to meet regional requirements through the intelligent routing and load balancing of Istio.
* Built-in HA tools in Red Hat OpenShift on IBM Cloud balance the workload within each geographic region, including self-healing and load balancing.









 Results 



* With tools like the chatbot, the HR team proved to their workforce that innovation was part of the corporate culture, not just buzz words.
* Authenticity with personalization in the site addressed the changing expectations of the airline’s workforce today.
* Last-minute updates to the HR site, including ones that driven by the employees chatbot conversations, went live quickly because Developers were pushing changes at least 10 times daily.
* With infrastructure management taken care of by IBM, the Development team was freed up to deliver the site in only 3 weeks.
* Create clusters for public-private apps, which are driven by the APIs.
* Structure apps into a set of cooperative microservices that run within Red Hat OpenShift on IBM Cloud, which is based on functional areas of apps and their dependencies.
* Deploy the apps to containers that run in Red Hat OpenShift on IBM Cloud. Built-in HA tools in Red Hat OpenShift on IBM Cloud balance the workloads, including self-healing and load balancing.
* Provide standardized DevOps dashboards through Kubernetes, open-source tools familiar to all types of Developers.







 Step 3: Innovate with IBM Garage and cloud services 



* Adopt the agile and iterative development practices from the IBM Garage Method to enable frequent releases of features, patches, and fixes without downtime.
* Whether developers are in the public or private sector, IBM Cloud® Continuous Delivery helps them to quickly provision an integrated toolchain, by using customizable, shareable templates.
* After Developers build and test the apps in their Dev and Test clusters, they use the IBM Cloud® Continuous Delivery toolchains to deploy apps into production clusters.
* With Watson AI, machine learning, and deep learning tools available from the IBM Cloud catalog, Developers focus on domain problems. Instead of custom unique ML code, ML logic is snapped into apps with service bindings.









 Results 



* Normally slow public-private partnerships now quickly spin up apps in weeks instead of months. These development partnerships now deliver features and bug fixes up to 10 times per week.
* Development is accelerated when all participants use well-known open-source tools, such as Kubernetes. Long learning curves are no longer a blocker.
* Transparency in activities, information, and plans is provided to citizens and private sector. And, citizens are integrated into government processes, services, and support.
* Public-private partnerships conquer Herculean tasks, such as Zika virus tracking, smart electricity distribution, analysis of crime statistics, and university "new collar" education.









 Large public port secures exchange of port data and shipping manifests that connect public and private organizations 

IT Execs for a private shipping company and the government-operated port need to connect, provide visibility, and securely exchange port information.
Thus, they chose Red Hat OpenShift on IBM Cloud because IBM simplifies infrastructure management.



* Managing Kubernetes master, IaaS, and operational components, such as Ingress and storage
* Monitoring health and recovery for worker nodes
* Providing global compute, so Developers don’t have to stand up infrastructure in worldwide regions where they need workloads and data to be located



Moving compute workloads into the IBM Cloud isn't enough though. The government needs to go through a method transformation as well. By adopting the practices of the IBM Garage Method, the provider can implement an agile and iterative delivery process that supports modern DevOps practices like Continuous Integration and Delivery (CI/CD).

Much of the CI/CD process itself is automated with IBM Cloud® Continuous Delivery in the cloud. The provider can define workflow toolchains to prepare container images, check for vulnerabilities, and deploy them to the Kubernetes cluster.

Compute, storage, and API tools run in the public cloud with secure access to and from on-premises data sources.

Technical solution:



* Red Hat OpenShift on IBM Cloud
* IBM Cloud Object Storage and IBM Cloudant
* IBM® API Connect
* IBM Secure Gateway
* IBM Cloud® Continuous Delivery





 Step 1: Store data in the cloud 



* IBM Cloud Object Storage provides historical data storage, accessible to all on the public cloud.
* Use IBM Cloudant with developer-provided keys to cache data in the cloud.
* Use IBM Secure Gateway to maintain secure connections to existing on-premises databases.







 Step 2: Provide access to data with APIs 



* Use IBM® API Connect for the API economy platform. APIs allow the public and private sectors to combine data into their apps.
* Create clusters for public-private apps, which are driven by the APIs.
* Structure apps into a set of cooperative microservices that run within Red Hat OpenShift on IBM Cloud, which is based on functional areas of apps and their dependencies.
* Deploy the apps to containers that run in Red Hat OpenShift on IBM Cloud. Built-in HA tools in Red Hat OpenShift on IBM Cloud balance the workloads, including self-healing and load balancing.
: Deploy clusters with Red Hat OpenShift or community Kubernetes installed as the container platform orchestrator.
: Choose the developer experience that fits your company, or run workloads across both Red Hat OpenShift or community Kubernetes clusters.
: Built-in integrations from the IBM Cloud console to the Kubernetes dashboard or Red Hat OpenShift web console.
: Single view and management experience of all your Red Hat OpenShift or community Kubernetes clusters from IBM Cloud. For more information, see Comparison between [Red Hat OpenShift](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_ovopenshift_kubernetes) and community Kubernetes clusters.

Single-tenant Kubernetes clusters with compute, network, and storage infrastructure isolation
: Create your own customized infrastructure that meets the requirements of your organization.
: Choose between [IBM Cloud Classic or VPC infrastructure providers](https://cloud.ibm.com/docs/openshift?topic=openshift-infrastructure_providers).
: Provision a dedicated and secured Red Hat OpenShift master, worker nodes, virtual networks, and storage by using the resources provided by IBM Cloud infrastructure.
: Fully managed Kubernetes master that is continuously monitored and updated by IBM to keep your cluster available.
: Option to provision worker nodes as bare metal servers for compute-intensive workloads such as data, GPU, and AI.
: Store persistent data, share data between Kubernetes pods, and restore data when needed with the integrated and secure volume service.
: Benefit from full support for all native Kubernetes APIs.

Multizone clusters to increase high availability
: Easily manage worker nodes of the same flavor (CPU, memory, virtual or physical) with worker pools.
: Guard against zone failure by spreading nodes evenly across select multizones and by using anti-affinity pod deployments for your apps.
: Decrease your costs by using multizone clusters instead of duplicating the resources in a separate cluster.
: Benefit from automatic load balancing across apps with the multizone load balancer (MZLB) that is set up automatically for you in each zone of the cluster.

Highly available masters
Benefits and service offerings 

[IBM Cloud® Kubernetes Service](https://www.ibm.com/cloud/kubernetes-service) delivers powerful tools by combining Docker containers, the Kubernetes technology, an intuitive user experience, and built-in security and isolation to automate the deployment, operation, scaling, and monitoring of containerized apps in a cluster of compute hosts. For more information about certification, see [Compliance on the IBM Cloud](https://www.ibm.com/cloud/compliance).



 Benefits of using the service 

Clusters are deployed on compute hosts that provide native Kubernetes and IBM-specific capabilities.

Choice of container platform provider
: Deploy clusters with Red Hat OpenShift or community Kubernetes installed as the container platform orchestrator.
: Choose the developer experience that fits your company, or run workloads across both Red Hat OpenShift or community Kubernetes clusters.
: Built-in integrations from the IBM Cloud console to the Kubernetes dashboard or Red Hat OpenShift web console.
: Single view and management experience of all your Red Hat OpenShift or community Kubernetes clusters from IBM Cloud. For more information, see Comparison between [Red Hat OpenShift](https://cloud.ibm.com/docs/containers?topic=containers-cs_ovopenshift_kubernetes) and community Kubernetes clusters.

Single-tenant Kubernetes clusters with compute, network, and storage infrastructure isolation
: Create your own customized infrastructure that meets the requirements of your organization.
: Choose between [IBM Cloud Classic or VPC infrastructure providers](https://cloud.ibm.com/docs/containers?topic=containers-infrastructure_providers).
: Provision a dedicated and secured Kubernetes master, worker nodes, virtual networks, and storage by using the resources provided by IBM Cloud infrastructure.
: Fully managed Kubernetes master that is continuously monitored and updated by IBM to keep your cluster available.
: Option to provision worker nodes as bare metal servers for compute-intensive workloads such as data, GPU, and AI.
* Use IBM Secure Gateway to maintain secure connections to remaining on-premises tool systems.
* Provide standardized DevOps dashboards and practices through Kubernetes.
* After Developers build and test apps in Development and Test clusters, they use the IBM Cloud® Continuous Delivery toolchains to deploy apps into the Red Hat OpenShift on IBM Cloud clusters across the globe.
* Built-in HA tools in Red Hat OpenShift on IBM Cloud balance the workload within each geographic region, including self-healing and load balancing.







 Step 3: Analyze and prevent fraud 



* Deploy IBM Watson for Financial Services to prevent and detect fraud.
* Using the toolchains and Helm deployment tools, the apps are also deployed to the Red Hat OpenShift on IBM Cloud clusters across the globe. Then, workloads and data meet regional regulations.









 Results 



* Lifting the existing monolithic VMs into cloud-hosted containers was a first step that allowed the Development Exec to save on capital and operations costs.
* With infrastructure management taken care of by IBM, the Development team was freed up to deliver updates 10 times daily.
* In parallel, the provider implemented simple time-boxed iterations to get a handle on the existing technical debt.
* With the number of transactions they process, they can scale their operations exponentially.
* At the same time, new fraud analysis with Watson increased the speed of detection and prevention, reducing fraud 4 times more than the region’s average.
Adding services by using managed add-ons 

Managed Red Hat OpenShift on IBM Cloud add-ons are an easy way to enhance your cluster with extra capabilities and open-source capabilities, such as the Diagnostics and Debug Tool, Block Storage for VPC, or the Cluster Autoscaler. The version of the driver, plug-in, or open-source tool that you add to your cluster is tested by IBM and approved to be used in Red Hat OpenShift on IBM Cloud.

The managed add-ons that you can install in your cluster depend on the type of cluster, the container platform, and the infrastructure provider that you choose.

Support
: Managed add-ons are fully integrated into the IBM Cloud support organization. If you have a question or an issue with using the managed add-ons, you can use one of the Red Hat OpenShift on IBM Cloud support channels. For more information, see [Getting help and support](https://cloud.ibm.com/docs/openshift?topic=openshift-get-help).

Billing
: If the tool that you add to your cluster incurs costs, these costs are automatically integrated and listed as part of your Red Hat OpenShift on IBM Cloud billing. The billing cycle is determined by IBM Cloud depending on when you enabled the add-on in your cluster.
: In general, no additional setup, such as opening ports or IP addresses is required. However, refer to the documentation of each managed add-on to find the prerequisites that your cluster must meet before you install the managed add-on.



 Adding managed add-ons 

To enable a managed add-on in your cluster from the CLI, use the [ibmcloud oc cluster addon enable command](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_addon_enable). To enable a managed add-on in your cluster in the [Red Hat OpenShift clusters console](https://cloud.ibm.com/kubernetes/clusters?platformType=openshift), use the Add-ons pane of the cluster details page.