Persistent storage using Fibre Channel

    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. Persistent volumes are not bound to a single project or namespace; they can be shared across the OKD cluster. Persistent volume claims are specific to a project or namespace and can be requested by users.

    Additional resources

    To provision Fibre Channel volumes using the API the following must be available:

    • The filesystem type.

    A persistent volume and a LUN have a one-to-one mapping between them.

    Prerequisites

    • Fibre Channel LUNs must exist in the underlying infrastructure.

    Use LUN partitions to enforce disk quotas and size constraints. Each LUN is mapped to a single persistent volume, and unique names must be used for persistent volumes.

    Enforcing quotas in this way allows the end user to request persistent storage by a specific amount, such as 10Gi, and be matched with a corresponding volume of equal or greater capacity.

    Fibre Channel volume security

    Users request storage with a persistent volume claim. 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.