vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Kubernetes Service delivers powerful tools by combining Docker and Kubernetes technologies, 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.

A minimal cluster with one (1) zone, one (1) worker node and the smallest available size (Flavor) is sufficient for this tutorial.

Open the [Kubernetes clusters](https://cloud.ibm.com/kubernetes/clusters) and click Create cluster. See the documentation referenced below for more details based on the cluster type. Summary:



* Click Standard tier cluster
* For Kubernetes on VPC infrastructure see reference documentation[Creating VPC clusters](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-vpc-gen2&interface=ui).



* Click Create VPC:



* Enter a name for the VPC.
* Chose the same resource group as the cluster.
* Click Create.



* Attach a Public Gateway to each of the subnets that you create:



* Navigate to the [Virtual private clouds](https://cloud.ibm.com/vpc-ext/network/vpcs).
* Click the previously created VPC used for the cluster.
* Scroll down to subnets section and click a subnet.
* In the Public Gateway section, click Detached to change the state to Attached.
* Click the browser back button to return to the VPC details page.
* Repeat the previous three steps to attach a public gateway to each subnet.





* For Kubernetes on Classic infrastructure see reference documentation [Creating classic cluster](https://cloud.ibm.com/docs/containers?topic=containers-cluster-create-classic&interface=ui).
* Choose a resource group.
* Uncheck all zones except one.
* Scale down to 1 Worker nodes per zone.
* Choose the smallest Worker Pool flavor.
* Enter a Cluster name.
* Click Create.







 Step 2: Clone a sample application
* [Key Kubernetes objects](https://cloud.ibm.com/docs/blockchain?topic=blockchain-k8s-overviewk8s-overview-key-obj)
* [IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/blockchain?topic=blockchain-k8s-overviewk8s-overview-iks)







 IBM Developer 

[IBM Developer](https://developer.ibm.com/technologies/blockchain/)





 IBM Blockchain Platform locations 

[IBM Blockchain Platform locations](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-regions-locationsibp-regions-locations)



* [IBM Blockchain Platform for IBM Cloud](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-regions-locationsibp-regions-locations-ibp)







 IBM Cloud storage 

[IBM Cloud storage](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-deploy-iksibp-console-storage)





 Glossary 

[Glossary](https://cloud.ibm.com/docs/blockchain?topic=blockchain-glossaryglossary)



* [Approve](https://cloud.ibm.com/docs/blockchain?topic=blockchain-glossaryglossary-propose)
* [Asset](https://cloud.ibm.com/docs/blockchain?topic=blockchain-glossaryglossary-asset)
* [Block](https://cloud.ibm.com/docs/blockchain?topic=blockchain-glossaryglossary-block)
* [CA](https://cloud.ibm.com/docs/blockchain?topic=blockchain-glossaryglossary-CA)
containers-kubernetes.cluster-service.unbind An IBM Cloud service is removed from the cluster. 
 containers-kubernetes.cluster-subnet.add A public or private portable subnet is added to a cluster. 
 containers-kubernetes.cluster-subnet.create A public or private subnet is created for the cluster. 
 containers-kubernetes.cluster-subnet.detach A public or private portable subnet is detached from a cluster. 
 containers-kubernetes.cluster-subnet.list The classic or VPC subnets for a cluster are listed. 
 containers-kubernetes.cluster-user-subnet.add A user-managed subnet is added to the cluster. Note: User-added subnets are deprecated. 
 containers-kubernetes.cluster.user-subnet.detach A user-managed subnet is detached from the cluster. Note: User-added subnets are deprecated. 
 containers-kubernetes.cluster-user-subnet.list User-added subnets for a cluster are listed. Note: User-added subnets are deprecated. 
 containers-kubernetes.cluster-webhook.create A cluster webhook, such as for Slack, is created. 
 containers-kubernetes.cluster-webhook.list Webhooks for a cluster are listed. 
 containers-kubernetes.version.update A master patch update is initiated for the cluster. Master patch updates are typically applied automatically by IBM to your cluster. 







 Cluster account events 

The following list of account events that are related to managing your clusters are sent to IBM Cloud Activity Tracker.



Cluster account events

 Action Description 

 containers-kubernetes.account-api-key.reset The API key that is used for all clusters in the region and resource group is set to the requesting user's API key credentials. 
 containers-kubernetes.account-customer-root-key.list Root keys from key management service instances for the IBM Cloud account are listed. 
 containers-kubernetes.account-datacenter-vlan.list VLANs in an IBM Cloud account for a particular data center are listed.
* [ibmcloud sat location rm](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencelocation-rm).







 ibmcloud sat resource 

[Search and view Kubernetes resources that are managed by Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencesat-resource-commands).



* [ibmcloud sat resource get](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-resource-get).
* ibmcloud sat resource history: Get the history of a Kubernetes resource.



* [ibmcloud sat resource history get](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-resource-history-get).



* [ibmcloud sat resource ls](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-resource-ls).







 ibmcloud sat service 

[View Satellite service clusters](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencesat-service-commands).



* [ibmcloud sat service ls](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-service-ls).







 ibmcloud sat storage 

[View and manage Satellite storage resources](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencesat-storage-commands).



* ibmcloud sat storage assignment: View and manage Satellite storage assignments.



* [ibmcloud sat storage assignment create](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-storage-assign-create).
enableRegistrationUrl [cluster register](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-cluster-register) ![Feature available.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite/images/icon-checkmark-filled.svg) 
 Remove a cluster from Satellite Config. deleteCluster [cluster unregister](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-cluster-unregister) ![Feature available.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite/images/icon-checkmark-filled.svg) 
 View clusters that are attached to Satellite Config. clusters calls [cluster ls](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-cluster-ls) <br>[cluster get](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-referencecli-cluster-get) ![Feature available.](https://cloud.ibm.com/docs-content/v1/content/c8335d66af691d19e837116fd633481c477061eb/satellite/images/icon-checkmark-filled.svg) 







 Cluster group platform access roles 



Actions that you can take with platform access roles.

 Action API CLI None Viewer Editor Operator Administrator 

 Add clusters to a cluster group.
Select the Satellite zones that Satellite uses to evenly assign hosts across zones that represent zones in your underlying infrastructure provider. Generally, create your worker pool across 3 zones for high availability.
2. Request the vCPU, Memory (GB), and number of Worker nodes per zone that you want to create the worker pool with. Satellite can automatically assign available hosts to the worker pool to fulfill your request. Generally, select at least 1 worker node per zone for a total of 3 worker nodes in your cluster.



8. In the Satellite Config section, decide whether to enable cluster admin access for Satellite Config. If you don't grant Satellite Config access, you can't later use the Satellite Config functionality to view or deploy Kubernetes resources for your clusters. If you want to enable access later, you can [create custom RBAC roles for Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfigcustom-access-cluster-wide).
9. For the Resource details, enter a Cluster name and any [IBM Cloud tags](https://cloud.ibm.com/docs/account?topic=account-tag) that you want to associate with your cloud resource. The cluster name must start with a letter, can contain letters, numbers, and hyphen (-), and must be 35 characters or fewer.
10. Click Create. When you create the cluster, the cluster master is automatically created in your Satellite location control plane, and your worker pool is automatically assigned available hosts that match your worker node request.
11. Wait for the cluster to reach a Normal state.

If you don't have any available and matching hosts in your Satellite location, the cluster is still created but enters a Warning state. [Attach hosts](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts) to your Satellite location so that hosts can be assigned as worker nodes to the worker pool.
Non-ideal use cases Multizone clusters, geographically distributed data, or sharing data across multiple app instances. 







 File Storage for VPC 

Virtual Private Cloud



File Storage for VPC characteristics

 Characteristic Description 

 Multizone-capable No, as specific to a data center. Data can't be shared across zones, unless you implement your own data replication. 
 Ideal data types All 
 Data usage pattern Random read-write operations, sequential read-write operations, or write-intensive workloads 
 Access Via file system on mounted volume 
 Supported Kubernetes access writes ReadWriteOnce (RWO) 
 Performance Predictable due to assigned IOPS and size. IOPS are not shared between pods. 
 Consistency Strong 
 Durability High 
 Resiliency Medium as specific to a data center. File storage server is clustered by IBM with redundant networking. 
 Availability Medium as specific to a data center. 
 Scalability Difficult to extend beyond the data center. You can't change an existing storage tier. 
 Encryption None 
 Backup and recovery Run kubectl cp. 
 Common use cases Mass or single file storage or file sharing across a single zone cluster. 
 Non-ideal use cases Multizone clusters, geographically distributed data, or sharing data across multiple app instances. 







 Block Storage for VPC 

Virtual Private Cloud



Block Storage for VPC characteristics.

 Characteristics Description 

 Multizone-capable No, as specific to a data center. Data can't be shared across zones, unless you implement your own data replication. 
 Ideal data types All 
 Data usage pattern Random read-write operations, sequential read-write operations, or write-intensive workloads 
 Access Via file system on mounted volume 
 Supported Kubernetes access writes ReadWriteOnce (RWO) 
 Performance Predictable due to assigned IOPS and size. IOPS are not shared between pods. 
 Consistency Strong 
 Durability High 
 Resiliency Medium as specific to a data center. Block storage server is clustered by IBM with redundant networking. 
 Availability Medium as specific to a data center. 
 Scalability Difficult to extend beyond the data center. You can't change an existing storage tier. 
 Encryption Encryption in transit with Key Protect
* [Feature gates](https://cloud.ibm.com/docs/containers?topic=containers-service-settingsfeature-gates)







 Related links 

[Community Kubernetes documentation](https://kubernetes.io/docs/home/)

[IBM Developer - Containers](https://developer.ibm.com/technologies/containers/)

[IBM Developer - Kubernetes](https://developer.ibm.com/components/kubernetes/)





 VPC flavors 

[VPC flavors](https://cloud.ibm.com/docs/containers?topic=containers-vpc-flavorsvpc-flavors)



* [au-syd](https://cloud.ibm.com/docs/containers?topic=containers-vpc-flavorsau-syd)
* [br-sao](https://cloud.ibm.com/docs/containers?topic=containers-vpc-flavorsbr-sao)
* [ca-tor](https://cloud.ibm.com/docs/containers?topic=containers-vpc-flavorsca-tor)
* [eu-de](https://cloud.ibm.com/docs/containers?topic=containers-vpc-flavorseu-de)
* [eu-gb](https://cloud.ibm.com/docs/containers?topic=containers-vpc-flavorseu-gb)
* [jp-osa](https://cloud.ibm.com/docs/containers?topic=containers-vpc-flavorsjp-osa)
* [jp-tok](https://cloud.ibm.com/docs/containers?topic=containers-vpc-flavorsjp-tok)
* [us-east](https://cloud.ibm.com/docs/containers?topic=containers-vpc-flavorsus-east)
* [us-south](https://cloud.ibm.com/docs/containers?topic=containers-vpc-flavorsus-south)







 Classic flavors
Related links 



* [Ordering vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-req)
* [Adding clusters for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingclusters)
* [Adding ESXi servers to vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservers)
* [Deleting vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_deletinginstance)
If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)



1. Install the latest release of the version 3 [Helm CLI](https://github.com/helm/helm/releases) on your local machine.
2. Add the IBM Cloud Helm repositories to your Helm instance.

If you enabled [VRF](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf) and [service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointservice-endpoint) in your IBM Cloud account, you can use the private IBM Cloud Helm repository to keep your image pull traffic on the private network. If you can't enable VRF or service endpoints in your account, use the public registry domain: helm repo add iks-charts https://icr.io/helm/iks-charts.

helm repo add iks-charts https://private.icr.io/helm/iks-charts

helm repo add ibm-charts https://raw.githubusercontent.com/IBM/charts/master/repo/stable

helm repo add ibm-community https://raw.githubusercontent.com/IBM/charts/master/repo/community

helm repo add entitled https://raw.githubusercontent.com/IBM/charts/master/repo/entitled

helm repo add ibm-helm https://raw.githubusercontent.com/IBM/charts/master/repo/ibm-helm
3. Update the repos to retrieve the latest versions of all Helm charts.

helm repo update
4. List the Helm charts that are currently available in the IBM Cloud repositories.

helm search repo iks-charts

helm search repo ibm-charts

helm search repo ibm-community

helm search repo entitled
[Satellite hosts](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutcomponents-satellite-location-infrastructure-components) ⁣12. [Management plane](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutcomponents-other-supporting) 
 ⁣3. [Satellite Config](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutcomponents-ibm-cloud) ⁣7. [Link connector](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutcomponents-satellite-location-control-plane-workers) ⁣13. [Other application services](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutcomponents-other-supporting) 
 ⁣4. [IBM Cloud services](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutfinancial-services-validated-services) ⁣8. [Monitoring](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutcomponents-satellite-location-control-plane-workers) 
 ⁣9. [Cluster 1 master](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutcomponents-satellite-location-control-plane-workers) <br>⁣9. [Cluster 2 master](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-satellite-architecture-aboutcomponents-satellite-location-control-plane-workers) 
 ⁣10.
ibmcloud ks worker ls --cluster <cluster_name_or_ID>



 Allow worker nodes to communicate with cluster master 

To allow worker nodes to communicate with the cluster master over the public cloud service endpoint, allow outgoing network traffic from the source <each_worker_node_publicIP> to the destination TCP/UDP port range 30000-32767 and port 443, and the following IP addresses and network groups.

This table is moving. For the latest IP lists and continued updates, see the public network isolation folder in the IBM/kube-samples[repo](https://github.com/IBM-Cloud/kube-samples/tree/master/calico-policies/public-network-isolation). You can Watch pull requests in the repo for updates.



* TCP/UDP port range 30000-32767, port 443 FROM <each_worker_node_publicIP> TO <public_IPs>
* Replace <public_IPs> with the public IP addresses of the region that your cluster is located.





Table 1. IP addresses to open for outgoing traffic

 Region Public IP address 

 AP North (che01,seo01, sng01, tok02, tok04, tok05) 119.81.194.90, 119.81.222.210, 128.168.106.194, 128.168.71.117, 128.168.75.194, 128.168.85.154, 135.90.69.66, 135.90.69.82, 161.202.126.210, 161.202.154.10, 161.202.186.226, 161.202.56.10, 161.202.57.34, 165.192.69.69, 165.192.80.146, 165.192.83.202, 165.192.95.90, 169.38.68.178, 169.38.70.10, 169.38.79.170, 169.56.1.162, 169.56.132.234, 169.56.48.114, 169.56.69.242, 169.56.96.42
DELETE/v1/clusters/{idOrName}/usersubnets/{subnetId}/vlans/{vlanId} Remove a user-managed subnet from a cluster. containers-kubernetes.cluster.operate containers-kubernetes.vlan.delete 
 GET/v1/clusters List the clusters that you have access to. containers-kubernetes.cluster.read N/A 
 GET/v1/clusters/{idOrName} View details for a cluster. containers-kubernetes.cluster.read N/A 
 GET/v1/clusters/{idOrName}/addons View details of the add-ons that are enabled in a cluster. containers-kubernetes.cluster.read N/A 
 GET/v1/clusters/{idOrName}/apiserverconfigs/auditwebhook View details for an audit webhook configuration. containers-kubernetes.cluster.read N/A 
 GET/v1/clusters/{idOrName}/config Get the cluster-specific configuration and certificates. containers-kubernetes.cluster.read containers-kubernetes.cluster.config 
 GET/v1/clusters/{idOrName}/services List the IBM Cloud services bound to a cluster across all namespaces. containers-kubernetes.cluster.read N/A 
 GET/v1/clusters/{idOrName}/services/{namespace} List the IBM Cloud services bound to a specific namespace in a cluster. containers-kubernetes.cluster.read N/A 
 GET/v1/clusters/{idOrName}/subnets List subnets from your IBM Cloud infrastructure account that are bound to a cluster. containers-kubernetes.cluster.read N/A 
 GET/v1/clusters/{idOrName}/usersubnets List user-managed subnets that are bound to a cluster. containers-kubernetes.cluster.read N/A 
 GET/v1/clusters/{idOrName}/webhooks List all webhooks for a cluster.
Cluster networking <br><br> * Set up cluster management components, such as public or private cloud service endpoints, VLANs, and load balancers.<br> * Fulfill requests for more infrastructure, such as attaching worker nodes to existing VLANs or subnets upon resizing a worker pool.<br> * Create clusters with subnet IP addresses reserved to use to expose apps externally.<br> * Set up a Konnectivity connection between the master and worker nodes when the cluster is created.<br> * Provide the ability to set up a VPN connection with on-premises resources such as through the strongSwan IPSec VPN service or the IBM Cloud VPC VPN.<br> * Provide the ability to isolate network traffic with edge nodes.<br><br><br> <br><br> * Use the provided API, CLI, or console tools to adjust [cluster networking configuration](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_network_cluster) to meet the needs of your workload, such as configuring service endpoints, adding VLANs to provide IP addresses for more worker nodes, setting up a VPN connection, or edge node worker pools.<br><br><br> 
 App networking <br><br> * Set up a public application load balancer (ALB) that is multizone, if applicable. Provide the ability to set up private ALBs and public or private network load balancers (NLBs).<br> * Support native Kubernetes public and private load balancers and Ingress routes for exposing services externally.<br> * Install Calico as the container networking interface, and set up default Calico network policies to control basic cluster traffic.<br><br><br> <br><br> * Set up any additional app networking capabilities that are needed, such as private ALBs, public or private NLBs, or additional Calico network policies.<br><br><br> 
 Observability <br><br> * Provide Log Analysis and Monitoring as managed add-ons to enable observability of your cluster and container environments.
To determine whether a location has a multizone region, your can run ibmcloud ks locations and look for the value in the Multizone Metro column.



Available multizone metro locations for classic clusters in IBM Cloud Kubernetes Service.

 Geography Country Metro Region Zones 

 Asia Pacific Australia Sydney au-syd syd01, syd04, syd05 
 Asia Pacific Japan Osaka jp-osa osa21, osa22, osa23 
 Asia Pacific Japan Tokyo jp-tok tok02, tok04, tok05 
 Europe Germany Frankfurt de-fra fra02, fra04, fra05 
 Europe United Kingdom London uk-lon lon02, lon04, lon05, lon06 
 North America United States Dallas us-dal dal10, dal12, dal13 
 North America United States Washington DC us-wdc wdc04, wdc06, wdc07 



* lon05 replaces lon02. New clusters must use lon05, which supports highly available masters that are spread across zones.





 Classic single zone regions 

If you create a classic cluster in a single zone region, you can create multiple worker nodes but you can't spread them across data centers (zones). The highly available master includes three replicas on separate hosts, but is not spread across zones.

Classic single zone clusters are managed from the regional endpoint located in the nearest region that supports classic multizone, such as mon01 to us-east or sao01 to us-south.



Available single zone data center locations for classic clusters in IBM Cloud Kubernetes Service.

 Geography Country Metro Region Zone Managed from region 

 Asia Pacific India Chennai in-che che01 AP North (ap-north, jp-tok) 
 Asia Pacific Singapore Singapore sng-mtr sng01 AP North (ap-north, jp-tok) 
 Europe Italy Milan it-mil mil01 EU Central (eu-central, eu-de) 
 Europe Netherlands Amsterdam nl-ams ams03 EU Central (eu-central, eu-de) 
 North America Canada Montreal ca-mon mon01 US East (us-east)