vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Accessing and working with your Satellite clusters 

After you created your Red Hat OpenShift cluster, you can use the capabilities in Red Hat OpenShift on IBM Cloud to work with your cluster.

Review common tasks that you might be interested in:



* [Accessing Red Hat OpenShift clusters on Satellite](https://cloud.ibm.com/docs/openshift?topic=openshift-access_clusteraccess_cluster_sat)
* [Assigning cluster access](https://cloud.ibm.com/docs/openshift?topic=openshift-users)







 Setting up the internal container image registry 

By default, the internal registry does not run in your Satellite cluster because no backing storage is set up for the internal registry. Review the following options to set up the internal registry.



* Non-persistent data on the worker node: See [Storing images in the worker node empty directory](https://cloud.ibm.com/docs/openshift?topic=openshift-registryemptydir_internal_registry).
* Persistent data in IBM Cloud Object Storage: See [Setting up the internal container image registry with IBM Cloud Object Storage](https://cloud.ibm.com/docs/openshift?topic=openshift-satellite-clusterssatcluster-internal-registry-cos)



By default, the [image registry operator management state](https://docs.openshift.com/container-platform/4.11/registry/configuring-registry-operator.htmlregistry-operator-configuration-resource-overview_configuring-registry-operator) is set to Unmanaged. After you change the storage section in the ConfigMap to use a different solution such as the emptyDir, you must update the management state to Managed. Then, the operator creates the internal registry pod. Use the following command: oc patch configs.imageregistry.operator.openshift.io/cluster --type merge -p '{"spec":{"managementState":"Managed"}}'



 Setting up the internal container image registry with IBM Cloud Object Storage
Setting up Container Registry as a private registry on Red Hat OpenShift 

You can add value to your Red Hat® OpenShift® Container Platform clusters by using IBM Cloud® Container Registry even where an internal registry is already provided.

For example, if you have multiple clusters, Container Registry integrates conveniently with Red Hat OpenShift Container Platform clusters so that you can build, share, synchronize, and scan image assets across clusters. For more information, see [Choosing an image registry solution](https://cloud.ibm.com/docs/openshift?topic=openshift-registryopenshift_registry_options).

You can set up Container Registry to work with the internal registry of [Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_rhosregistry_rhos_rhoks) or [other Red Hat OpenShift Container Platform providers](https://cloud.ibm.com/docs/Registry?topic=Registry-registry_rhosregistry_rhos_os).



 Set up Red Hat OpenShift on IBM Cloud to use Container Registry 

By default, your Red Hat OpenShift on IBM Cloud clusters are set up with an internal registry that stores images locally in your cluster. The clusters are also set up with image pull secrets in the default project to pull images that you store in your private Container Registry repositories.

You can use either registry separately or in combination. When you set up the Red Hat OpenShift on IBM Cloud internal registry to import images from Container Registry, you get the advantage of a private registry that is common to multiple clusters. 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).
5. The user securely(HTTPS) accesses the application via browser.
6. The admin monitors the health and performance of the microservices using the metrics, traces, logs.







 Before you begin 

This tutorial requires:



* IBM Cloud CLI,



* IBM Cloud Kubernetes Service plugin (kubernetes-service),



* oc to interact with OpenShift.



You will find instructions to download and install these tools for your operating environment in the [Getting started with tutorials](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-tutorials) guide.

To avoid the installation of these tools, you can use the [Cloud Shell](https://cloud.ibm.com/shell) from the IBM Cloud console. Use oc version to ensure the version of the Red Hat OpenShift on IBM Cloud CLI matches your cluster version (4.12.x). If they do not match, install the matching version by following [these instructions](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-tutorialsgetting-started-cloud-shell).





 Step 1: Create a Red Hat OpenShift on IBM Cloud cluster 

With Red Hat OpenShift on IBM Cloud, you have a fast and secure way to containerize and deploy enterprise workloads in clusters. Red Hat OpenShift on IBM Cloud clusters build on Kubernetes container orchestration that offers consistency and flexibility for your development lifecycle operations.

In this section, you will provision a Red Hat OpenShift on IBM Cloud cluster in one (1) zone with two (2) worker nodes:



1. Log into your IBM Cloud account and create a Red Hat OpenShift on IBM Cloud cluster from the [Red Hat OpenShift on IBM Cloud cluster create page](https://cloud.ibm.com/kubernetes/catalog/create?platformType=openshift).
2. Set the Orchestration service to 4.12.x version of Red Hat OpenShift on IBM Cloud.
3. Select your OCP entitlement.
4.
* Red Hat OpenShift for VMware v4.4.23



You can now install the Red Hat OpenShift for VMware service on vCenter Server with NSX-T instances. For NSX-T, you must have a new vCenter Server instance with NSX-T that is provisioned with NSX-T 3.0.1.1 or you must upgrade from NSX-T 2.5.1 to NSX-T 3.0.2.

HyTrust CloudControl for vCenter Server with NSX-V - deprecated
: New installations of HyTrust CloudControl are no longer supported for new or existing deployments of vCenter Server with NSX-V instances. You can still view or delete existing HyTrust CloudControl installations on your existing instances.

User interface updates and enhancements
: A new Uplink speed option is available in the Network interface section when you order vCenter Server instances, order new vSphere clusters, and add clusters for vCenter Server instances.





 24 August 2020 

VMware Solutions Shared
: (Updated on 25 August 2020) VMware Solutions provides an upgrade for the VMware Shared infrastructure to VMware Cloud Director (vCD) v10.1.1. The v10.1.1 update is available to Dallas and Frankfurt IBM Cloud® data centers.

The Flash portal is no longer available with the v10.1.1 update.

VMware Solutions Shared - storage policy updates
: For the existing storage policies in your virtual data center, the default storage policy is now the new standard storage policy. Previously, the default storage policy was 4 IOPS/GB. This default storage policy is automatic for new VMware Solutions Shared instances.

The 3.8 release introduces Standard storage policies and Encrypted storage policies. These new storage policies are available for new VMware Solutions Shared instances and added to existing VMware Solutions Shared instances with the VMware Cloud Director (vCD) v10.1.1 upgrade.



* A standard storage policy is now available for both decrypted and encrypted policies.
[Deploy microservices with Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-openshift-microservices)Deploy microservices with Red Hat OpenShift on IBM Cloud

This tutorial demonstrates how to deploy applications to Red Hat OpenShift on IBM Cloud. Red Hat OpenShift on IBM Cloud provides a great experience for developers to deploy software applications and for System Administrators to scale and observe the applications in production.

Red Hat OpenShift on IBM Cloud Log Analysis

+3

Monitoring,Kubernetes service,Cloudant



* 3 hours
* 2023-05-18



[Plan, create and update deployment environments](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-plan-create-update-deployments)Plan, create and update deployment environments

Multiple deployment environments are common when building a solution. They reflect the lifecycle of a project from development to production. This tutorial introduces tools like the IBM Cloud CLI and Terraform to automate the creation and maintenance of these deployment environments.

Kubernetes service Virtual Servers for Classic

+5

Object Storage,Cloudant,,Activity Tracker hosted event search,Monitoring



* 2 hours
* 2023-05-05



[Serverless web application and API with Code Engine](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-serverless-webapp)Serverless web application and API with Code Engine

In this tutorial, you will create a serverless web application using a bucket in Object Storage and implementing the application backend using IBM Cloud Code Engine and IBM Cloudant as JSON document database.

Code Engine Cloudant

+1

Object Storage



* 1 hour
* 2023-06-16



[Best practices for organizing users, teams, applications](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-users-teams-applications)Best practices for organizing users, teams, applications
This tutorial walks you through how to deploy an application to a Red Hat OpenShift on IBM Cloud cluster from a remote Git repository, expose the app on an Red Hat OpenShift on IBM Cloud route, monitor the health of the environment, and scale the application. Additionally, you will learn how to use a private container registry, deploy an application from a private Git repository and bind a custom domain to your application.

Red Hat OpenShift on IBM Cloud Kubernetes service

+1

Container Registry



* 2 hours
* 2023-06-14



[Use trusted profiles as foundation for secure cloud environments](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-trusted-profile-for-enterprise-security)Use trusted profiles as foundation for secure cloud environments

This tutorial may incur costs. Use the Cost Estimator to generate a cost estimate based on your projected usage.

Running secure enterprise workloads Kubernetes service

+2

Activity Tracker hosted event search,Container Registry



* 2 hours
* 2023-07-14



[Deploy an app on Kubernetes](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-tutorial-cd-kubernetes)Deploy an app on Kubernetes

In this tutorial, you learn how to create an open toolchain by using different deployment strategies. You also learn how toolchains are implemented in the IBM Cloud® Continuous Delivery service and how to develop and deploy a simple web application (app) by using toolchains.

Creating apps Red Hat OpenShift on IBM Cloud

+2

Kubernetes service,Continuous Delivery



* 30 minutes
* 2022-10-27



[Deploy Kubernetes resources to multiple clusters by using IBM Cloud Satellite Config](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-tutorial-cd-only-satellite)Deploy Kubernetes resources to multiple clusters by using IBM Cloud Satellite Config
* Red Hat OpenShift on IBM Cloud provides scalable compute, so that the inventory and cross-sales API workloads can grow during high-volume periods of the year, such as the fall holidays.









 Traditional grocer increases customer traffic and sales with digital insights 

A Chief Marketing Officer (CMO) needs to increase customer traffic by 20% in stores by making the stores a differentiating asset. Large retail competitors and online retailers are stealing sales. At the same time, the CMO needs to reduce inventory without markdowns because holding inventory too long locks up millions in capital.

Red Hat OpenShift on IBM Cloud provides easy spin-up of more compute, where Developers quickly add Cloud Analytics services for sales behavior insights and digital market adaptability.

Key technologies:



* [Horizontal scaling to accelerate development](https://cloud.ibm.com/docs/openshift?topic=openshift-plan_deployhighly_available_apps)
* [Clusters that fit varied CPU, RAM, storage needs](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesplanning_worker_nodes)
* [Insights to market trends with Watson Discovery](https://www.ibm.com/products/watson-discovery)
* [DevOps native tools, including open toolchains in IBM Cloud® Continuous Delivery](https://www.ibm.com/cloud/architecture/toolchains/)
* [Inventory management with IBM® Event Streams for IBM Cloud®](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-aboutabout)





 Context 

Traditional grocer increases customer traffic and sales with digital insights.



* Competitive pressures from online retailers and large retail stores disrupted traditional grocery retail models. Sales are declining, evidenced by low foot traffic in physical stores.
* Their loyalty program needs a boost in the arm with a modern take on the printed coupons at check out. So Developers must constantly evolve the related apps, but traditional tools slow their ability to deploy updates and features frequently.
For more information, see [PowerNSX](https://github.com/vmware/powernsx).







 Build process overview 

This documentation describes the process to install Red Hat OpenShift v4.7 on to an existing vCenter Server instance. The process installs and configures:



* One bastion node.
* One bootstrap node.
* Three control plane nodes.
* Three worker nodes.



The deployment approach is described in the following phases:



* Phase 1 - vCenter Server instance preparation.



* Using the IBM Cloud® for VMware Solutions console, [order a vCenter Server instance](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-procedure), which can include NFS or vSAN storage. You can use an existing instance if the instance has enough capacity.
* Using the IBM Cloud console, [order more private and public subnets](https://cloud.ibm.com/docs/subnets?topic=subnets-getting-started) to be used by the Red Hat OpenShift cluster.
* Download RHEL 8.0 ISO for the OS of the bastion or deployment node and the Red Hat Enterprise Linux CoreOS (RHCOS) OVA image. This step is described in [Prerequisites for installation](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-openshift-runbook-runbook-prereq-intro).
* Using govc, the OVA and ISO are uploaded to a datastore on the vCenter Server instance. This step is described in [Prerequisites for installation](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-openshift-runbook-runbook-prereq-intro).
* Add logical switches - Two logical switches are created; OpenShift-LS the network the OpenShift VMs are deployed onto and OpenShift-DLR-Transit, the uplink between the DLR and the Edge.
For more information, see [Promotions for VMware Solutions services](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservicesvc_addingservices-service-promotions).

The cluster consists of the following components:



* Three primary nodes
* Three worker nodes, all running Red Hat® CoreOS
* Two VMware NSX® VMs
* A Red Hat CoreOS template
* A bastion VM running CoreOS



For more information about the architecture, see [Red Hat OpenShift architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcs-openshift-redhat-arch).



 Technical specifications for Red Hat OpenShift for VMware 

The following capacity requirements apply only if your vCenter Server instance is using vSAN™ storage. If you are using NFS, a new 2-TB NFS datastore, which is dedicated to Red Hat OpenShift, is ordered.

The solution topology has the following requirements:



* 9 CPUs
* 120 GB RAM
* 1,170 GB storage



For more information about resource requirements and capacity checking, see [Resource requirements for services](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservicesvc_addingservices-resource-requirements).

To successfully deploy Red Hat OpenShift for VMware on vCenter Server, you must have a Red Hat account and the pull secret key from your account. All Red Hat accounts have an associated pull secret, which you can retrieve by [logging in to your Red Hat account](https://cloud.redhat.com/openshift/install/vsphere/user-provisioned). You must purchase Red Hat support entitlements through Red Hat and, if needed, send information for all Red Hat OpenShift support issues to Red Hat.



 Selection of the target cluster for installation 

During deployment and Day 2 operations, you are prompted for the cluster.
Container-native virtualization You can set up [container-native virtualization add-on](https://docs.openshift.com/container-platform/4.11/virt/about-virt.html) on bare metal machines, but not on virtual machines. Container-native virtualization is not supported by IBM. If you experience issues, you are responsible for resolving the issues and any impact to your workloads. 
 Serverless workloads You can set up [Red Hat OpenShift Serverless](https://www.redhat.com/en/topics/microservices/why-choose-openshift-serverless). You can also set up Red Hat OpenShift Serverless. 
 Service mesh You can set up the [Red Hat OpenShift Service Mesh](https://docs.openshift.com/container-platform/4.11/service_mesh/v1x/installing-ossm.html). You can also set up the Red Hat OpenShift Service Mesh, but you must [apply a network policy](https://gist.githubusercontent.com/kitch/39c504a2ed9e381c2aadea436d5b52e4/raw/d8efa69f41d41425b16bb363a881a98d40d3708c/mesh-policy.yaml) for the service mesh ingress to work. 
 API and CLI tools OpenShift Container Platform clusters are set up with access to Kubernetes and Red Hat OpenShift API resources. You can also install command line tools such as oc and odo. Red Hat OpenShift on IBM Cloud clusters come with the same capabilities to use the Kubernetes and Red Hat OpenShift API and CLI tools.
Setting up virtualization on a Satellite location 

You can set up your Bare Metal Servers to use Red Hat OpenShift virtualization in your Satellite location. By using virtualization, you can provision Windows or other virtual machines on your Bare Metal Servers in a managed Red Hat OpenShift space.

Supported host operating systems
: Red Hat CoreOS (RHCOS)



 Prerequisites 



* Create a RHCOS-enabled location. To check whether your location is RHCOS-enabled, see [Is my location enabled for Red Hat CoreOS?](https://cloud.ibm.com/docs/satellite?topic=satellite-locationsverify-coreos-location). If your location is not enabled, [create a new one with RHCOS](https://cloud.ibm.com/docs/satellite?topic=satellite-locations).
* Attach hosts to your location and set up your [location control plane](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-control-plane).
* Find and record your bare metal host name.
* Find your bare metal server network information. Record the CIDR and gateway information for the public and private interfaces for your system.
* If you want to use IBM Cloud Object Storage to store your ignition file, create or identify a bucket.
* Create or identify a cluster within the Satellite location that runs a supported operating system; for example, this tutorial uses a Red Hat OpenShift cluster that is running 4.11.
* If you want to use OpenShift Data Foundation as your storage solution, add 2 storage disks to each of your Bare Metal Servers when you provision them.







 Bare Metal Server requirements for Satellite 

To set up virtualization, your Bare Metal Server must meet the following requirements.



* Must support virtualization technology.



* For Intel CPUs, support for virtualization is referred to as Intel VT or VT-x.
* For AMD CPUs, support for virtualization is referred to as AMD Virtualization or AMD-V.



* Must have a minimum of minimum of 8 cores and 32 GB RAM, plus any additional cores that you need for your vCPU overhead.
* [VMware vCenter Server and Red Hat OpenShift architecture overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcs-openshift-intro)
* [System context for vCenter Server and Red Hat OpenShift architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcs-openshift-syscontext)
* [Red Hat OpenShift architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcs-openshift-redhat-arch)
* [Storage options on IBM Cloud and Red Hat OpenShift](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcs-openshift-storage)
IBM Cloud networking and infrastructure 



 Physical structure 

The physical infrastructure required to deploy a Red Hat® OpenShift® production instance onto a VMware® vCenter Server® cluster requires the following minimum specification.



Table 1. vCenter Server specification for Red Hat OpenShift

 Item NFS deployment vSAN deployment 

 Number of servers 3 4 
 CPU 28 Cores 2.2 GHz 28 Cores 2.2 GHz 
 Memory (GB) 384 384 
 Storage 2,000 GB 2 IOPS/GB Management <br>2,000 GB 4 IOPS/GB Workload <br>4,000 GB 4 IOPS/GB Min 960-GB SSD x2 



In addition to the Red Hat OpenShift hardware requirements, you must create persistent volumes in the Red Hat OpenShift environment to store images from the container register or customer workloads.





 Virtual structure 

Zoom

![Physical structure](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/openshift-networking41.svg)

Figure 1. Physical structure

Within the vCenter Server instance, the Red Hat OpenShift instance is deployed with a dedicated NSX® Edge Services Gateway (ESG) and Distributed Logical Router (DLR). The Red Hat OpenShift installation is loaded into the VXLAN subnet that is defined in the previous components.

The ESG is configured with a source NAT rule (SNAT) to allow outbound traffic, which enables internet connectivity to download the Red Hat OpenShift prerequisites and to connect to GitHub and Red Hat®. Alternatively, you can use a web-proxy for internet connectivity. The ESG is also configured to provide access to DNS and NTP services within the IBM Cloud® environment.

The ESG is also configured to use the load balancer capability, thus reducing the need for HAProxy nodes. The load balancers are configured for the apps wildcard DNS URL and the API / API-INT DNS Records.