Resource Partitioning
You can partition storage system resources by limiting the LDEV ID range added to the resource group for a specific Kubernetes cluster. You can also isolate impacts between Kubernetes clusters.
NoteResource Partitioning is not supported for VSSB.
Storage system requirements
Set your storage system to meet the following requirements:
| Storage system resources | Descriptions |
| Resource group | Only one resource group for one Kubernetes is supported. Virtual storage machine is not supported. For more notes, see Unsupported configuration examples. |
| Storage system user group and Storage system user | Storage system users must have access only to the resource group that you created. The storage system user must not have access to other resource groups. |
| Pool | Create a pool from pool volumes with the resource group that you have created. |
| LDEV | Allocate the necessary number of undefined LDEV IDs to the resource group. |
| Host Group | Allocate the necessary number of undefined host group IDs to the resource group for each storage system port defined in StorageClass. The number of host group IDs must be equal to the number of hosts for all ports. |
Unsupported configuration examples
The following configurations are unsupported examples. Before using the resource partitioning feature, carefully check these examples and the above table when configuring system configurations.
- Example 1: Mixing Secret and StorageClass with resource group configuration and
without resource group configuration for the same storage system in a single Kubernetes
cluster is not supported.
- Example 2: Mixing more than two Secret and StorageClass for different
resource groups of the same storage system in a single Kubernetes cluster is not
supported.
Secret settings
Example of secret settings.
apiVersion: v1 kind: Secret metadata: name: secret-sample type: Opaque data: url: aHR0cDovLzE3Mi4xNi4xLjE= user: VXNlcjAx password: UGFzc3dvcmQwMQ== stringData: resourceGroupID: "1" # Specify resource group ID
StorageClass settings
If you use iSCSI as a storage system connection, specify the port IP address in number order. If you use FC as a storage system connection, no additional setting is required for StorageClass.
apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: sc-sample provisioner: hspc.csi.hitachi.com reclaimPolicy: Delete volumeBindingMode: Immediate allowVolumeExpansion: true parameters: serialNumber: "54321" poolID: "1" portID : CL1-A,CL2-A connectionType: iscsi portIP: “192.168.10.10, 192.168.10.11” # iSCSI Port IP Addresses. <...>