vania-janet/multiturn-rag-retrieval-data huggingface dataset:
When you delete the PVC, only the PVC is deleted. The PV, the physical storage device in your IBM Cloud infrastructure account, and your data still exist. To reclaim the storage and use it in your cluster again, you must remove the PV and follow the steps for [using existing block storage](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageexisting_block).
* If you want the PV, the data, and your physical block storage device to be deleted when you delete the PVC, choose a storage class without retain.



6. Choose if you want to be billed hourly or monthly. The default setting is hourly billing.







 Setting up encryption for Block Storage for Classic 

You can set up encryption for Block Storage for Classic by using IBM Key Protect.

The following example explains how to create a service ID with the required access roles for Key Protect and your cluster. The credentials of this service ID are used to enable encryption for your Block Storage for Classic volumes.

You can enable encryption by creating a Kubernetes secret that uses your personal API key as long as you have the Reader service access role for your Key Protect instance as well as the Viewer platform access role and the Writer service access role for your cluster.

[Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)



1. Make sure that you are assigned the Editor platform access role and the Writer service access role for Key Protect so that you can create your own root key that you use to encrypt your Block Storage for Classic instance. You can review your IAM access roles in the [IAM console](https://cloud.ibm.com/iam). For more information about IAM roles, see [IAM access](https://cloud.ibm.com/docs/account?topic=account-userroles).
2.
For more information about cluster availability, see [Planning your cluster for high availability](https://cloud.ibm.com/docs/openshift?topic=openshift-ha_clusters).



* The zones are filtered based on the VPC that you selected, and include the VPC subnets that you previously created.
* To create a single zone cluster, select one zone only. You can [add zones to your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-add_workersadd_zone) later.
* To create a multizone cluster, select multiple zones.





10. In the Worker pool section, choose your worker node flavor and number. You can add more worker pools to your cluster later. To change worker node operating systems, size, or storage, click Change flavor.



* Default: The default flavor comes with 4 vCPUs of computing power and 16 GB of memory. This virtual flavor is billed hourly. Other types of flavors include the following.
* Bare metal: Bare metal servers are provisioned manually by IBM Cloud infrastructure after you order, and can take more than one business day to complete. Bare metal is best suited for high-performance applications that need more resources and host control. Be sure that you want to provision a bare metal machine. Because it is billed monthly, if you cancel it immediately after an order by mistake, you are still charged the full month.
* Virtual - shared: Infrastructure resources, such as the hypervisor and physical hardware, are shared across you and other IBM customers, but each worker node is accessible only by you. Although this option is usually less expensive and sufficient, you might want to verify your performance and infrastructure requirements with your company policies. Virtual machines are billed hourly.
* Virtual - dedicated: Your worker nodes are hosted on infrastructure that is devoted to your account. Your physical resources are completely isolated. Virtual machines are billed hourly.



11. Optional: If the flavor that you want to use has a configurable secondary disk, you can modify the secondary disk by clicking the Edit icon !
You can only create RSA SSH keys. For an Ed25519 SSH key, you must upload the key information.s Ed25519 can only be used if the operating system supports this key type. Ed25519 can't be used with Windows or VMware images. 
 For more information, see [SSH keys](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys). 
 Data volumes You can add one or more secondary data volumes to be included when you provision the instance. To add a volume, click Create and specify the information in Table 2. When finished, click Save. 
 Network interfaces Assign networking options to connect into the IBM Cloud VPC. You can create and assign up to five network interfaces to each instance. 
 Attached block storage volume You can add one or more secondary data volumes to be included when you provision the instance. To add a volume, click New block storage volume and specify the information in Table 2. When finished, click Create volume. 
 Virtual Private Cloud Select 'my-vpc' for the Virtual Private Cloud 





Table 2. Block storage volume values specified when provisioning an instance

 Field Value 

 Name Specify a unique, meaningful name for your volume, for example, 'my-data-volume' You can later edit the name if you want. Volume names must be unique the entire VPC infrastructure. 
 Size Enter a volume size in GBs. Volume sizes can be between 10 GB and 2 TBs. 
 Encryption Encryption with IBM-managed keys is enabled by default on all volumes. You can also choose Customer Managed and use your own encryption key. For more information about one-time set up procedure, see [Prerequisites for setting up customer-managed encryption](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-planningbyok-encryption-prereqs). 



A block storage volume is created and attached to the virtual server instance. On the instance details page, the Attached block storage volumes list is updated to show the new volume.





 Step 3: Creating an access group for the dedicated host group
* If you have a firewall, [allow egress access](https://cloud.ibm.com/docs/containers?topic=containers-firewallvyatta_firewall) for the IBM Cloud infrastructure IP ranges of the zones that your clusters are in so that you can create PVCs.
* Install the [IBM Cloud block storage plug-in](https://cloud.ibm.com/docs/containers?topic=containers-block_storageinstall_block).
* [Decide on a pre-defined storage class](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_predefined_storageclass) or create a [customized storage class](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_custom_storageclass).



Looking to deploy block storage in a stateful set? For more information, see [Using block storage in a stateful set](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_statefulset).

To add block storage:



1. Create a configuration file to define your persistent volume claim (PVC) and save the configuration as a .yaml file.



* Example for bronze, silver, gold storage classes: The following .yaml file creates a claim that is named block-storage-pvc of the "ibmc-block-silver" storage class, billed hourly, with a gigabyte size of 24Gi.

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: block-storage-pvc
labels:
billingType: "hourly"
region: us-south
zone: dal13
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 24Gi
storageClassName: ibmc-block-silver
3. Create a configuration file for your stateful set and the service that you use to expose the stateful set. The following example shows how to deploy NGINX as a stateful set with three replicas. For each replica, a 20 gigabyte block storage device is provisioned based on the specifications that are defined in the ibmc-block-retain-bronze storage class. All storage devices are provisioned in the dal10 zone. Because block storage can't be accessed from other zones, all replicas of the stateful set are also deployed onto worker nodes that are located in dal10.

apiVersion: v1
kind: Service
metadata:
name: nginx
labels:
app: nginx
spec:
ports:
- port: 80
name: web
clusterIP: None
selector:
app: nginx
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: nginx
spec:
serviceName: "nginx"
replicas: 3
podManagementPolicy: Parallel
selector:
matchLabels:
app: nginx
billingType: "hourly"
region: "us-south" Enter the region where your cluster is located.
zone: "dal10"
template:
metadata:
labels:
app: nginx
billingType: "hourly"
region: "us-south"
zone: "dal10"
spec:
containers:
- name: nginx
image: nginx
ports:
- containerPort: 80
name: web
volumeMounts:
- name: myvol
mountPath: /usr/share/nginx/html
volumeClaimTemplates:
- metadata:
name: myvol
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
iops: "300" required only for performance storage
storageClassName: ibmc-block-retain-bronze
To create your customized storage class, see [Customizing a storage class](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_custom_storageclass). Then, [use your customized storage class in your PVC](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageadd_block).



 Creating topology-aware storage 

To use block storage in a multizone cluster, your pod must be scheduled in the same zone as your block storage instance so that you can read and write to the volume. Before topology-aware volume scheduling was introduced by Kubernetes, the dynamic provisioning of your storage automatically created the block storage instance when a PVC was created. Then, when you created your pod, the Kubernetes scheduler tried to deploy the pod to the same data center as your block storage instance.

Creating the block storage instance without knowing the constraints of the pod can lead to unwanted results. For example, your pod might not be able to be scheduled to the same worker node as your storage because the worker node has insufficient resources or the worker node is tainted and does not allow the pod to be scheduled. With topology-aware volume scheduling, the block storage instance is delayed until the first pod that uses the storage is created.

To use topology-aware volume scheduling, make sure that you installed the IBM Cloud Block Storage plug-in version 1.2.0 or later.

The following examples show how to create storage classes that delay the creation of the block storage instance until the first pod that uses this storage is ready to be scheduled. To delay the creation, you must include the volumeBindingMode: WaitForFirstConsumer option. If you don't include this option, the volumeBindingMode is automatically set to Immediate and the block storage instance is created when you create the PVC.

Example for Endurance block storage.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-block-bronze-delayed
parameters:
billingType: hourly
classVersion: "2"
fsType: ext4
A way to describe a notification that travels from a cloud service to a human destination. In other contexts, service-to-human is also categorized as app-to-person.







 Subscription 

An association of one topic to one destination. If a destination requires additional information to operate correctly (for example, email addresses for an email destination), then that information is included in the subscription.





 Subscriber 

An entity that is targeted by a subscription. For webhooks, the webhook host is the subscriber. For human destinations, email addresses and phone numbers (or the people who own them) are subscribers.

One subscription can have only one destination, but it can have many subscribers within that destination.





 Outbound digital message 

An event notification that is sent from the Event Notifications service to a subscriber. Outbound digital messages are a primary billing metric for the Event Notifications service. The price for outbound digital messages varies by destination (for example, outbound digital messages to SMS are priced differently than outbound digital messages to email). In most cases a dispatch (attempt to deliver) is considered an outbound digital message, regardless of whether the delivery was successfully.





 Digital message origin 

The originating phone number or origin ID for a text message, and the originating domain or IP address for email. In, most countries the sender is obligated by law to be transparent about the origin of a digital message. If you select the IBM SMS Service or IBM Email Service as a destination for your subscriptions, the text messages that user receives has an origin that is owned by IBM.





 SMS message 

A text message in Simple Messaging Service format.



 SMS message segment 

A group of 160 characters within an SMS text message. A single message can contain many segments. Each message segment counts as one outbound digital message for billing purposes.





 SMS unit 

A pricing unit for SMS text messages.
ip_version <br>Always included <br>string The IP version(s) supported by this subnet. <br>Possible values:[ipv4] 
 ipv4_cidr_block <br>Always included <br>string The IPv4 range of the subnet, expressed in CIDR format. <br>Possible values: 9 ≤ length ≤ 18, Value must match regular expression `^(([0-9] 
 name <br>Always included <br>string The name for this subnet. The name is unique across all subnets in the VPC. <br>Possible values: 1 ≤ length ≤ 63, Value must match regular expression `^-?([a-z] 
 network_acl Always included <br>NetworkACLReference 
 resource_group <br>Always included <br>ResourceGroupReference The resource group for this subnet. 
 resource_type <br>Always included <br>string The resource type. <br>Possible values: 1 ≤ length ≤ 128, Value must match regular expression ^[a-z](_[a-z0-9]+)$ <br>Example:subnet 
 routing_table <br>Always included <br>RoutingTableReference The routing table for this subnet. 
 status <br>Always included <br>string The status of the subnet. <br>Possible values:available,deleting,failed, pending 
 total_ipv4_address_count <br>Always included <br>int64 
 vpc <br>Always included <br>VPCReference The VPC this subnet resides in. 
 zone <br>Always included <br>ZoneReference The zone this subnet resides in. 
 public_gateway <br>PublicGatewayReference The public gateway to use for internet-bound traffic for this subnet. 





Table 6. Retrieve status codes

 Status Code 

 200 The subnet was retrieved successfully. 
 404 A subnet with the specified identifier could not be found.
Therefore, add ESXi servers to vCenter Server only for on-premises ESXi servers or ESXi servers that you don't manage in the IBM Cloud for VMware Solutions console.
* vSAN storage requires at least 4 ESXi servers.









 Procedure to add ESXi servers 



1. From the IBM Cloud for VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2. In the vCenter Server table, click the instance for which you want to expand capacity.
3. Click the Infrastructure tab.
4. In the Clusters table, click the cluster to which you want to add ESXi servers.
5. In the ESXi servers table, click Add.
6. In the Add server window, enter the number of servers that you want to add.
7. Optionally, select the checkbox to add servers during maintenance mode. The checkbox is selected by default.

When you provision the new ESXi server, virtual machines (VMs) are immediately migrated to the new servers if you do not select the Maintenance mode checkbox. You do not receive a confirmation message before the migration begins.
8. Complete the bare metal configuration.



* Select a configuration from the existing hosts in the cluster.
* Select a new bare metal server configuration.



* Select the CPU model and the RAM size.
* Complete the storage configuration. Specify the disk types for the capacity and cache disks, the number of disks, and the vSAN license edition. If you want more storage, check the High performance with Intel Optane box.





9. Review the estimated price and click Add.

You can also add the provisioned resources to the IBM Cloud estimate tool, by clicking Add to estimate. This option is useful if you want to estimate the price of the selected IBM Cloud for VMware Solutions resources together with other IBM Cloud resources that you might consider to purchase.





 Results after you add ESXi servers 



1. You might experience a slight delay on the console while the instance status changes from Available to Modifying. Allow the operation to complete before you make more changes to the instance.
2.
To use File Storage for Classic in a multizone cluster, your pod must be scheduled in the same zone as your File Storage for Classic instance so that you can read and write to the volume. Before topology-aware volume scheduling was introduced by Kubernetes, the dynamic provisioning of your storage automatically created the File Storage for Classic instance when a PVC was created. Then, when you created your pod, the Kubernetes scheduler tried to deploy the pod to a worker node in the same data center as your File Storage for Classic instance.

Creating the File Storage for Classic instance without knowing the constraints of the pod can lead to unwanted results. For example, your pod might not be able to be scheduled to the same worker node as your storage because the worker node has insufficient resources or the worker node is tainted and does not allow the pod to be scheduled. With topology-aware volume scheduling, the File Storage for Classic instance is delayed until the first pod that uses the storage is created.

The following examples show how to create storage classes that delay the creation of the File Storage for Classic instance until the first pod that uses this storage is ready to be scheduled. To delay the creation, you must include the volumeBindingMode: WaitForFirstConsumer option. If you don't include this option, the volumeBindingMode is automatically set to Immediate and the File Storage for Classic instance is created when you create the PVC.

Example for Endurance File Storage for Classic.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-file-bronze-delayed
parameters:
billingType: hourly
classVersion: "2"
iopsPerGB: "2"
sizeRange: '[20-12000]Gi'
type: Endurance
provisioner: ibm.io/ibmc-file
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer

Example for Performance File Storage for Classic.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: ibmc-file-performance-storageclass
labels:
provisioner: ibm.io/ibmc-file
parameters:
type: "Endurance"
iopsPerGB: "2"
sizeRange: "[1-12000]Gi"
mountOptions: nfsvers=4.1,hard
billingType: "hourly"
reclaimPolicy: "Delete"
classVersion: "2"
gidAllocate: "true"
gidFixed: "65165"
Show more

To create the storage class in your cluster, run kubectl apply -f storageclass.yaml.
2. Create a YAML file for your PVC that uses the storage class that you created.

kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: gid-pvc
labels:
billingType: "monthly"
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: 20Gi
storageClassName: ibmc-file-bronze-gid
3. Create the PVC in your cluster.

kubectl apply -f pvc.yaml
4. Wait a few minutes for the file storage to be provisioned and the PVC to change to a Bound status. Note that if you created the PVC in a multizone cluster, the PVC remains in a pending state.

kubectl get pvc

Example output

NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
gid-pvc Bound pvc-5e4acab4-9b6f-4278-b53c-22e1d3ffa123 20Gi RWX ibmc-file-bronze-gid 2m54s
5. Create a YAML file for your deployment that mounts the PVC that you created. In the spec.template.spec.securityContext.runAsUser field, specify the non-root user ID that you want to use. This user ID is automatically added to the supplemental group ID that is defined in the storage class to gain read and write access to the file storage.
<-- </section "id="section-histogram-example" "> --><-- </section "id="section-histogram" "> --><-- <section "id="section-max" "> --> max Returns the highest value in the specified field across all matching documents.<-- <section "id="section-max-syntax" "> --> Syntax max(field)
<-- </section "id="section-max-syntax" "> --><-- <section "id="section-max-example" "> --> Example <-- <table> -->Table 2. Sample product prices| Product | Price || -------- | ----- || I Series | 200 || J Series | 450 || X Series | 325 |<-- </table ""> -->When the max aggregation type is applied to a set of documents in which the price field contains the values that are shown in Table 2, the result is 450. max(price)=450
This aggregation type performs a terminal operation. When combined with other aggregations, the output is not used as input for the next aggregation. The output is returned in a discrete group.<-- </section "id="section-max-example" "> --><-- </section "id="section-max" "> --><-- <section "id="section-min" "> --> min Returns the lowest value in the specified field across all matching documents.<-- <section "id="section-min-syntax" "> --> Syntax min(field)
<-- </section "id="section-min-syntax" "> --><-- <section "id="section-min-example" "> --> Example <-- <table> -->Table 3.
<br><br> * id <br> Always included <br> string<br><br><br> The unique identifier for this subnet <br>Possible values: 1 ≤ length ≤ 64, Value must match regular expression ^[-0-9a-z_]+$ <br>Example:7ec86020-1c6e-4889-b3f0-a15f2e50f87e 
 ip_version <br>Always included <br>string The IP version(s) supported by this subnet. <br>Possible values:[ipv4] 
 ipv4_cidr_block <br>Always included <br>string The IPv4 range of the subnet, expressed in CIDR format. <br>Possible values: 9 ≤ length ≤ 18, Value must match regular expression `^(([0-9] 
 name <br>Always included <br>string The name for this subnet. The name is unique across all subnets in the VPC. <br>Possible values: 1 ≤ length ≤ 63, Value must match regular expression `^-?([a-z] 
 network_acl Always included <br>NetworkACLReference 
 resource_group <br>Always included <br>ResourceGroupReference The resource group for this subnet. 
 resource_type <br>Always included <br>string The resource type. <br>Possible values: 1 ≤ length ≤ 128, Value must match regular expression ^[a-z](_[a-z0-9]+)$ <br>Example:subnet 
 routing_table <br>Always included <br>RoutingTableReference The routing table for this subnet. 
 status <br>Always included <br>string The status of the subnet. <br>Possible values:available,deleting,failed, pending 
 total_ipv4_address_count <br>Always included <br>int64 
 vpc <br>Always included <br>VPCReference The VPC this subnet resides in. 
 zone <br>Always included <br>ZoneReference The zone this subnet resides in.