This is a cache of https://docs.openshift.com/container-platform/3.3/install_config/persistent_storage/persistent_storage_fibre_channel.html. It is a snapshot of the page at 2024-11-27T04:20:18.038+0000.
Using Fibr<strong>e</strong> Chann<strong>e</strong>l - Configuring P<strong>e</strong>rsist<strong>e</strong>nt Storag<strong>e</strong> | Installation and Configuration | Op<strong>e</strong>nShift Contain<strong>e</strong>r Platform 3.3
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. explore the new docs experience today.
  1. Documentation
    2. history
&times;

Persistent Storage Using Fibre Channel

Overview

You can provision your OpenShift Container Platform cluster with persistent storage using Fibre Channel. Some familiarity with Kubernetes and Fibre Channel is assumed.

The Kubernetes persistent volume framework allows administrators to provision a cluster with persistent storage and gives users a way to request those resources without having any knowledge of the underlying infrastructure.

High-availability of storage in the infrastructure is left to the underlying storage provider.

Provisioning

Storage must exist in the underlying infrastructure before it can be mounted as a volume in OpenShift Container Platform. All that is required for Fibre Channel persistent storage is the targetWWNs (array of Fibre Channel target’s World Wide Names), a valid LUN number, and filesystem type, and the PersistentVolume API. Note, the number of LUNs must correspond to the number of Persistent Volumes that are created. In the example below, we have LUN as 2, therefore we have created two Persistent Volume definitions.

Fiber Channel does not support the 'Recycle' reclaim policy.
example 1. Persistent Volumes Object Definition
apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv0001
spec:
  capacity:
    storage: 1Gi
  accessModes:
    - ReadWriteOnce
  fc:
    targetWWNs: ['500a0981891b8dc5', '500a0981991b8dc5']
    lun: 2
    fsType: ext4
apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv0002
spec:
  capacity:
    storage: 1Gi
  accessModes:
    - ReadOnlyMany
  fc:
    targetWWNs: ['500a0981891b8dc5', '500a0981991b8dc5']
    lun: 2
    fsType: ext4

Changing the value of the fstype parameter after the volume has been formatted and provisioned can result in data loss and pod failure.

enforcing Disk Quotas

Use LUN partitions to enforce disk quotas and size constraints. each LUN is one persistent volume. Kubernetes enforces unique names for persistent volumes.

enforcing quotas in this way allows the end user to request persistent storage by a specific amount (e.g, 10Gi) and be matched with a corresponding volume of equal or greater capacity.

Fibre Channel Volume Security

Users request storage with a PersistentVolumeClaim. This claim only lives in the user’s namespace and can only be referenced by a pod within that same namespace. Any attempt to access a persistent volume across a namespace causes the pod to fail.

each Fibre Channel LUN must be accessible by all nodes in the cluster.