vania-janet/multiturn-rag-retrieval-data huggingface dataset:
After you deploy the Block Storage for VPC driver, you can create deployments that leverage Block Storage for VPC. The following stateful set dynamically provisions Block Storage for VPC volumes by creating PVCs that use ibmc-vpc-block-5iops-tier storage class.



1. Save the following YAML configuration as a file on your local machine called statefulset.yaml.

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: web
spec:
serviceName: "nginx"
replicas: 2
podManagementPolicy: "Parallel"
selector:
matchLabels:
app: nginx
template:
metadata:
labels:
app: nginx
spec:
containers:
- name: nginx
securityContext:
privileged: false
image: k8s.gcr.io/nginx-slim:0.8
ports:
- containerPort: 80
name: web
volumeMounts:
- name: www
mountPath: /usr/share/nginx/html
tolerations:
- operator: Exists
volumeClaimTemplates:
- metadata:
annotations:
volume.beta.kubernetes.io/storage-class: ibmc-vpc-block-5iops-tier
name: www
spec:
accessModes:
- ReadWriteOnce access mode
resources:
requests:
storage: 25Gi 
Show more
2. Create the stateful set in your cluster.

kubectl create -f statefulset.yaml
3. Verify that the stateful set pods are running.

kubectl get pods
User can override this default
encrypted: "false" By default, all PVC using this class will only be provider managed encrypted. The user can override this default
encryptionKey: "" If encrypted is true, then a user must specify the encryption key used associated KP instance
resourceGroup: "" Use resource group if specified here. else use the one mentioned in storage-secrete-store
zone: "" By default, the storage vpc driver will select a zone. The user can override this default
tags: "" A list of tags "a, b, c" that will be created when the volume is created. This can be overidden by user
classVersion: "1"
uid: "" The initial user identifier for the file share.
gid: "" The initial group identifier for the file share.
reclaimPolicy: "Delete"
allowVolumeExpansion: true
Show more

name
: Enter a name for your storage class.

profile
: Enter the profile that you selected in the previous step, or enter custom to use a custom IOPs value. To find supported storage sizes for a specific profile, see [Tiered IOPS profile](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles). Any PVC that uses this storage class must specify a size value that is within this range.

encrypted
: In the parameters, enter true to create a storage class that sets up encryption for your File Storage for VPC volume. If you set this option to true, you must provide the root key CRN of your Key Protect service instance that you want to use in parameterencryptionKey.

encryptionKey
: If you entered true for parameters.encrypted, then enter the root key CRN of your Key Protect service instance that you want to use to encrypt your File Storage for VPC volume.

zone
: In the parameters, enter the VPC zone where you want to create the Block Storage for VPC instance.
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: 5iops-tier
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Delete
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-custom
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
iops: "400"
profile: custom
region: ""
resourceGroup: ""
sizeIOPSRange: |-
[10-39]GiB:[100-1000]
[40-79]GiB:[100-2000]
[80-99]GiB:[100-4000]
[100-499]GiB:[100-6000]
[500-999]GiB:[100-10000]
[1000-1999]GiB:[100-20000]
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Delete
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.3_354
labels:
addonmanager.kubernetes.io/mode: Reconcile
<br> * Check whether Cloud Object Storage network access is restricted to a specific IP range<br> * Check whether account has at least one VPN or Direct Link configured<br> * Check whether Virtual Private Cloud (VPC) classic access is disabled<br> * Check whether Virtual Private Cloud (VPC) has no rules in the default security group<br> * Check whether all network interfaces of a virtual server instance have at least one Virtual Private Cloud (VPC) security group attached<br> * Check whether Container Registry image pushes and pulls take place only over private endpoints<br> * Check whether Virtual Servers for VPC instance has the minimum # interfaces<br> * Check whether Hyper Protect Crypto Services is accessible only through private endpoints<br> * Check whether Cloud Object Storage public access is disabled in IAM settings (not applicable to ACLs managed using S3 APIs)<br> * Check whether Virtual Private Cloud (VPC) network access control lists don't allow ingress from 0.0.0.0/0 to RDP port<br> * Check whether App ID redirect URIs are not using localhost or 127.0.0.1<br> * Check whether Virtual Private Cloud (VPC) network access control lists don't allow ingress from 0.0.0.0/0 to SSH port<br><br><br>
Select Attach volume.
4. Select a volume from the list of available resources and click Attach. Messages display on the instance details page to indicate that the volume is being attached. When it completes, the Storage volumes list is updated to include the new volume.









 Attaching a Block Storage for VPC volume from the CLI 

Follow these instructions to use the CLI to attach a Block Storage for VPC volume to a virtual server instance. Each instance can have [many volume attachments](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storagevol-attach-limits), but a single volume attachment connects one volume to one instance.



 Before you begin 

Before you can use the CLI, you must install the IBM Cloud CLI and the VPC CLI plug-in. For more information, see the [CLI prerequisites](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentcli-prerequisites-setup).



1. Log in to the IBM Cloud.

ibmcloud login --sso -a cloud.ibm.com

This command returns a URL and prompts for a passcode. Go to that URL in your browser and log in. If successful, you get a one-time passcode. Copy this passcode and paste it as a response on the prompt. After successful authentication, you are prompted to choose your account. If you have access to multiple accounts, select the account that you want to log in as. Respond to any remaining prompts to finish logging in.
2. Select the current generation of VPC.

ibmcloud is target --gen 2







 Attaching a Block Storage for VPC volume from the CLI 

To attach a volume to a virtual server instance in the current resource group, run this command.

ibmcloud is instance-volume-attachment-add NAME INSTANCE_ID VOLUME_ID [--auto-delete true | false] [--json]

NAME is the name that you provide for the volume attachment and INSTANCE_ID is the ID of the virtual server instance.
For an overview of all available storage profiles, see [VPC Block Storage Profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-profiles).





 Storage for SAP HANA - single-node 

To fulfill the KPIs defined by SAP HANA, each profile needs different storage volumes that are listed in details in the following sections. These configurations are mandatory storage configurations, not sample storage configurations, because they are the tested and certified storage layouts that comply with SAP HANA Tailored Data Center Integration (TDI) Phase 5. It is highly recommended to stick to these specific specifications.

Customers who want to choose different layouts are advised to follow the [SAP HANA TDI Overview](https://www.sap.com/documents/2017/09/e6519450-d47c-0010-82c7-eda71af511fa.html) and [SAP HANA TDI FAQ](https://www.sap.com/documents/2016/05/e8705aae-717c-0010-82c7-eda71af511fa.html) when they order different storage sizes and types. Then, they must run SAP's performance measurement tool HCMT - see [SAP Note 2493172 - SAP HANA Hardware and Cloud Measurement Tools](https://launchpad.support.sap.com//notes/2493172) and follow the instructions of the [HCMT guide](https://help.sap.com/viewer/product/HANA_HW_CLOUD_TOOLS/latest/en-US).

For all of the following layouts consider that the volume names might differ - we assume that the naming follows the sequence of ordering the storage, that is, 1st order -> vdd, 2nd order -> vde, and so on. All block storage volumes must be ordered with the predefined profile of 10 IOPS/GB (high performance). One exception might be /hana/shared partition where 5 IOPS/GB (medium performance) are sufficient - but ONLY IF you assigned a dedicated volume for this partition.
ibmcloud is flow-log-create --bucket STORAGE_BUCKET_NAME --target TARGET_ID [--name NAME] --active ACTIVE [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME] [--json]

Where:



* --bucket is the name of the Object Storage bucket.
* --target is the target for the flow log.
* --name is the new name for the flow log.
* --active indicates whether this collector is active.
* --resource-group-id is the ID of the resource group. This option is mutually exclusive with --resource-group-name.
* --resource-group-name is the name of the resource group. This option is mutually exclusive with --resource-group-id.
* --json formats the output in JSON.







 Creating a flow log collector with the API 

To create a flow log collector by using the API, follow these steps:



1. Set up your [API environment](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentapi-prerequisites-setup) with the right variables.
2. Store the following values in variables to be used in the API command:



* ResourceGroupId - First, get your resource group and then populate the variable:



export ResourceGroupId=<your_resourcegroup_id>



* VpcId - Find by using the list vpc command (with the preceding variables) and then populate the variable based on the provided ID:



export VpcId=<your_VPC_id>



* COSbucket - The name of the Object Storage bucket.



export COSbucket=<your_COS_bucket_name>
3. When all variables are initiated, provision a flow log collector for the specific VPC:

curl -X POST
-sH "Authorization:${iam_token}"
[menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Storage > Block storage volumes to view a list of your block storage volumes.
2. Select New volume.
3. Enter the information in Table 1 to define your new block storage volume.
4. Update the fields in the Encryption section (see Table 2). When your changes are complete, click Create Volume.
5. Optionally, attach the volume to an instance. For more information, see [Next steps](https://cloud.ibm.com/docs/vpc?topic=vpc-block-storage-vpc-encryptionnext-step-create-byok-volumes-vpc).





Table 1. Block storage volume provisioning information

 Field Value 

 Name Specify a meaningful name for your volume. For example, provide a name that describes your compute or workload function. The volume name can be up to 63 lowercase alpha-numeric characters and include the hyphen (-), and must begin with a lowercase letter. Volume names must be unique across the entire VPC infrastructure. You can later edit the name. 
 Resource Group Specify a [resource group](https://cloud.ibm.com/docs/vpc?topic=vpc-iam-getting-startedresources-and-resource-groups). 
 Tags Specify a tag to organize your resources. A tag is a label that you assign to a resource for easy filtering of resources in your resource list. For more information about tags, see [Working with tags](https://cloud.ibm.com/docs/account?topic=account-tag). 
 Location The availability zone, inherited from the VPC (for example, Dallas-1). You can select a different zone in your location from the list. 
 Size Enter a volume size in GBs. Volume sizes can be between 10 GB - 2 TBs. Expanded capacity IOPS tiers increase volume size up to 16 TB and 48,000 IOPS. This Beta feature is available for evaluation and testing purposes.
The profiles include attached NVIDIA 16 GB PCIe v100 GPUs. Drivers must be installed separately. You can use these instances to accelerate certain processing functions for workloads such as inferencing and machine learning. For more information about this service, see [Managing GPUs](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-gpus).





 05 October 2021 

New regions for Very High Memory instance profile family (LA)
: Very High Memory profiles now are available in the United Kingdom (London), Japan (Osaka), and Australia (Sydney) regions. For more information, see [Very High Memory profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles&interface=uivhmemory).





 01 October 2021 

File Storage for VPC (LA)
: IBM Cloud® File Storage for VPC is now available in the United Kingdom (London) region. For more information about this service, see [About File Storage for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-about).







 September 2021 



 23 September 2021 

VNF routing mode for network load balancers
: With IBM Cloud VPC, you can provision Virtual Network Function (VNF) devices to gain better and more affordable scalability than you would by purchasing physical network devices. IBM Cloud VPC network load balancers with routing mode that you use to send traffic to only VNF devices as back-end targets. In addition, their health checks ensure that workloads only travel through healthy VNF devices. For more information about this service, see [Creating a network load balancer with routing mode for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-vnf).





 14 September 2021 

Terraform available for Placement Groups
: You can now create and manage placement groups in your IBM Cloud VPC by using Terraform.
Select an unattached volume from the [list of block storage volumes](https://cloud.ibm.com/docs/vpc?topic=vpc-viewing-block-storage&interface=uiviewvols-ui).
2. From the volume details page, in the Virtual server instances tile, click Attach.
3. On the side panel, select a virtual server instance and click Save. If the list shows no virtual server instances, click Create server to go to the [instance provisioning](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers) page. The boot or data volume is shown on the instance provisioning page in their respective fields.
4. Messages display that the volume is being attached to the image. When it completes, the image name appears under Attached instances.







 Attaching a volume to an instance from the instance details page 

Attach a Block Storage for VPC volume from the virtual server instance details page.



1. In the [IBM Cloud console)](https://cloud.ibm.com/login), go to menu icon ![menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Virtual server instances.
2. Select an instance from the list of all virtual server instances. If any Block Storage for VPC volumes are attached, they are listed under Storage volumes.
3. Select Attach volume.
4. Select a volume from the list of available resources and click Attach. Messages display on the instance details page to indicate that the volume is being attached. When it completes, the Storage volumes list is updated to include the new volume.









 Attaching a Block Storage for VPC volume from the CLI 

Follow these instructions to use the CLI to attach a Block Storage for VPC volume to a virtual server instance.
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-retain-10iops-tier
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: 10iops-tier
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Retain
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.2_285
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
razee/force-apply: "true"
name: ibmc-vpc-block-retain-5iops-tier
parameters:
billingType: hourly
classVersion: "1"
csi.storage.k8s.io/fstype: ext4
encrypted: "false"
encryptionKey: ""
profile: 5iops-tier
region: ""
resourceGroup: ""
sizeRange: '[10-2000]GiB'
tags: ""
zone: ""
provisioner: vpc.block.csi.ibm.io
reclaimPolicy: Retain
- apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
version: 2.0.2_285
labels:
addonmanager.kubernetes.io/mode: Reconcile
app: ibm-vpc-block-csi-driver
: The name of the storage class that you want to use to provision File Storage for VPC. You can choose to use one of the [IBM-provided storage classes](https://cloud.ibm.com/docs/openshift?topic=openshift-storage-file-vpc-sc-ref) or [create your own storage class](https://cloud.ibm.com/docs/containers?topic=containers-vpc-blockcustom-sc-vpc-block). If you don't specify a storage class, the PV is created with the default storage class ibmc-vpc-file-3iops-tier.
2. Create the PVC.

oc apply -f mypvc.yaml
3. Verify that your PVC is created and bound to the PV. This process can take a few minutes.

oc describe pvc mypvc

Example output

Name: mypvc
Namespace: default
StorageClass: ""
Status: Bound
Volume: pvc-0d787071-3a67-11e7-aafc-eef80dd2dea2
Labels: <none>
Capacity: 20Gi
Access Modes: RWX
Events:
FirstSeen LastSeen Count From SubObjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
3m 3m 1 {ibm.io/ibmc-vpc-file 31898035-3011-11e7-a6a4-7a08779efd33 } Normal Provisioning External provisioner is provisioning volume for claim "default/my-persistent-volume-claim"
3m 1m 10 {persistentvolume-controller } Normal ExternalProvisioning can't find provisioner "ibmc-vpc-file-retain-5iops-tier ", expecting that a volume for the claim is provisioned either manually or via external software
Block Storage for VPC add-on versions 4.4.17_1829, 5.0.7_1836, and 5.1.2_1828.
: For more information, see [the change log](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog).





 20 February 2023 

Ingress ALB version 1.3.1_3777_iks, 1.4.0_3783_iks, and 1.5.1_3779_iks
: For more information, see the [change log](https://cloud.ibm.com/docs/containers?topic=containers-cluster-add-ons-changelog).





 17 February 2023 

Cluster autoscaler add-on version 1.0.7_944.
: For more information, see [the change log](https://cloud.ibm.com/docs/containers?topic=containers-ca_changelog).





 14 February 2023 

Istio add-on 1.15.5 and 1.16.2
: For more information, see the [change log](https://cloud.ibm.com/docs/containers?topic=containers-istio-changelog1162).





 13 February 2023 

IBM Cloud Object Storage plug-in version 2.2.9 is available.
: For more information, see the [change log](https://cloud.ibm.com/docs/containers?topic=containers-cos_plugin_changelog).

Worker node fix packs 1.23.16_1562, 1.24.10_1553, 1.25.6_1531, and 1.26.1_1521.
The lifecycle of instance storage is critical to understand. Without a proper understanding of its temporary nature, workloads could experience data loss.

The instance storage space is allocated and attached to the virtual server instance at the time of provisioning. It is an integral and inseparable element of the virtual server instance. If you reboot your instance (either from its operating system or through an IBM Cloud Management interface), the instance storage data is retained and the instance is reconnected to its original disks.

However, when an instance is stopped or shut down, the instance storage attached to the virtual server instance is cryptographically erased and the instance storage is no longer available. The instance's boot volume is not affected. For auditing purposes, when an instance that has one or more storage disks is shut down, an IBM Cloud Activity Tracker event is published for each disk indicating it was "wiped". The event action is is.instance.disk.wipe. Refer to the Compute Events table on the [Activity Tracker page](https://cloud.ibm.com/docs/vpc?topic=vpc-at-eventsevents-compute) for listing of such events.

When a virtual server is powered off and then powered back on in order to complete a host or data center maintenance, the instance storage ephemeral data is not restored. However, advanced notice is given for maintenance windows. See [Understanding cloud maintenance operations](https://cloud.ibm.com/docs/vpc?topic=vpc-about-cloud-maintenance) for more information.

In the event of a Host Failure, the data on the instance storage disk is lost. The instance is restarted on another host automatically unless Host failure auto restart is set to stop. The provisioned disks are now empty.

In rare cases, a physical disk error might occur. If a physical disk error occurs, the instance fails to read/write to the failed disk. The instance is not automatically restarted in this scenario. Contact your support representative to report the problem and identify next steps. You can stop and then start your instance to effectively place it on a different disk that is functional.
Get the name of your ocscluster resource.

oc get ocscluster

Example output

NAME AGE
ocscluster-vpc 19d
2. Run the following command to edit your ocscluster resource.

oc edit ocscluster OCS-CLUSTER-NAME
3. Set the ocsUpgrade parameter to true.

...
spec:
billingType: hourly
monSize: 20Gi
monStorageClassName: ibmc-vpc-block-10iops-tier
numOfOsd: 1
ocsUpgrade: true
osdSize: 100Gi
osdStorageClassName: ibmc-vpc-block-10iops-tier
status:
storageClusterStatus: Decreasing the capacity not allowed
4. Save and close the file.
5. Wait for the update to complete.
6. Verify that the storagecluster and cephcluster resources are both deployed correctly.

oc get storagecluster -n openshift-storage
NAME AGE PHASE EXTERNAL CREATED AT VERSION
ocs-storagecluster 43h Ready 2023-06-21T09:22:00Z 4.11.0

oc get cephcluster -n openshift-storage
NAME DATADIRHOSTPATH MONCOUNT AGE PHASE MESSAGE HEALTH EXTERNAL
ocs-storagecluster-cephcluster /var/lib/rook 3 43h Ready Cluster created successfully HEALTH_OK

oc get csv -n openshift-storage
NAME DISPLAY VERSION REPLACES PHASE
mcg-operator.v4.11.8 NooBaa Operator 4.11.8 mcg-operator.v4.11.7 Succeeded
ocs-operator.v4.11.8 OpenShift Container Storage 4.11.8 ocs-operator.v4.11.7 Succeeded
odf-csi-addons-operator.v4.11.8 CSI Addons 4.11.8 odf-csi-addons-operator.v4.11.7 Succeeded
Block Storage for VPC add-on versions 4.4.17_1829, 5.0.7_1836, and 5.1.2_1828.
: For more information, see [the change log](https://cloud.ibm.com/docs/containers?topic=containers-vpc_bs_changelog).





 3 March 2023 

IBM Cloud Object Storage plug-in version 2.2.10.
: For more information, see the [change log](https://cloud.ibm.com/docs/containers?topic=containers-cos_plugin_changelog).





 1 March 2023 

CLI version 1.0.498.
: For more information, see the [change log](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelog).

ALB OAuth Proxy add-on version 2.0.0_1487.
: For more information, see the [change log](https://cloud.ibm.com/docs/containers?topic=containers-alb-oauth-proxy-changelog).







 February 2023 



 27 February 2023 

Worker node fix packs 1.23.16_1563, 1.24.10_1554, 1.25.6_1532, and 1.26.1_1522.
: For more information, see the change logs: [1.23](https://cloud.ibm.com/docs/containers?topic=containers-changelog_123), [1.24](https://cloud.ibm.com/docs/containers?topic=containers-changelog_124), [1.25](https://cloud.ibm.com/docs/containers?topic=containers-changelog_125), and [1.26](https://cloud.ibm.com/docs/containers?topic=containers-changelog_126).





 23 February 2023 

Ingress ALB version 1.3.1_3807_iks, 1.4.0_3808_iks, and 1.5.1_3809_iks