5.4. Persistent storage using Logical Volume Manager Storage

Procedure

1. Create a YAML file with the configuration for creating a namespace:

   Example YAML configuration for creating a namespace

   apiVersion: v1
   kind: Namespace
   metadata:
     labels:
       openshift.io/cluster-monitoring: "true"
       pod-security.kubernetes.io/enforce: privileged
       pod-security.kubernetes.io/audit: privileged
       pod-security.kubernetes.io/warn: privileged
     name: openshift-lvm-storage

2. Create the namespace by running the following command:

   $ oc create -f <file_name>

3. Create an OperatorGroup CR YAML file:

   Example OperatorGroup CR

   apiVersion: operators.coreos.com/v1
   kind: OperatorGroup
   metadata:
     name: openshift-storage-operatorgroup
     namespace: openshift-lvm-storage
   spec:
     targetNamespaces:
     - openshift-storage

4. Create the OperatorGroup CR by running the following command:

   $ oc create -f <file_name>

5. Create a Subscription CR YAML file:

   Example Subscription CR

   apiVersion: operators.coreos.com/v1alpha1
   kind: Subscription
   metadata:
     name: lvms
     namespace: openshift-lvm-storage
   spec:
     installPlanApproval: Automatic
     name: lvms-operator
     source: redhat-operators
     sourceNamespace: openshift-marketplace

6. Create the Subscription CR by running the following command:

   $ oc create -f <file_name>

Verification

1. To verify that LVM Storage is installed, run the following command:

   $ oc get csv -n openshift-lvm-storage -o custom-columns=Name:.metadata.name,Phase:.status.phase

   Example output

   Name                         Phase
   4.13.0-202301261535          Succeeded

Procedure

1. Log in to the OpenShift Container Platform web console.
2. Click Ecosystem Software Catalog.
3. Click LVM Storage on the software catalog page.

4. Set the following options on the Operator Installation page:

   1. Update Channel as stable-4.21.
   2. Installation Mode as A specific namespace on the cluster.
   3. Installed Namespace as Operator recommended namespace openshift-storage. If the openshift-lvm-storage namespace does not exist, it is created during the operator installation.

   4. Update approval as Automatic or Manual.

      注意

      If you select Automatic updates, the Operator Lifecycle Manager (OLM) automatically updates the running instance of LVM Storage without any intervention.

      If you select Manual updates, the OLM creates an update request. As a cluster administrator, you must manually approve the update request to update LVM Storage to a newer version.

5. Optional: Select the Enable Operator recommended cluster monitoring on this Namespace checkbox.
6. Click Install.

Procedure

1. Follow the steps in the "Creating the image set configuration" procedure. To create an ImageSetConfiguration custom resource (CR) for LVM Storage, you can use the following example ImageSetConfiguration CR configuration:

   Example ImageSetConfiguration CR for LVM Storage

   kind: ImageSetConfiguration
   apiVersion: mirror.openshift.io/v1alpha2
   archiveSize: 4 

   1

   
   storageConfig: 

   2

   
     registry:
       imageURL: example.com/mirror/oc-mirror-metadata 

   3

   
       skipTLS: false
   mirror:
     platform:
       channels:
       - name: stable-4.21 

   4

   
         type: ocp
       graph: true 

   5

   
     operators:
     - catalog: registry.redhat.io/redhat/redhat-operator-index:v4.21 

   6

   
       packages:
       - name: lvms-operator 

   7

   
         channels:
         - name: stable 

   8

   
     additionalImages:
     - name: registry.redhat.io/ubi9/ubi:latest 

   9

   
     helm: {}

   1

   Set the maximum size (in GiB) of each file within the image set.

   2

   Specify the location in which you want to save the image set. This location can be a registry or a local directory. You must configure the storageConfig field unless you are using the Technology Preview OCI feature.

   3

   Specify the storage URL for the image stream when using a registry. For more information, see Why use imagestreams.

   4

   Specify the channel from which you want to retrieve the OpenShift Container Platform images.

   5

   Set this field to true to generate the OpenShift Update Service (OSUS) graph image. For more information, see About the OpenShift Update Service.

   6

   Specify the Operator catalog from which you want to retrieve the OpenShift Container Platform images.

   7

   Specify the Operator packages to include in the image set. If this field is empty, all packages in the catalog are retrieved.

   8

   Specify the channels of the Operator packages to include in the image set. You must include the default channel for the Operator package even if you do not use the bundles in that channel. You can find the default channel by running the following command: $ oc mirror list operators --catalog=<catalog_name> --package=<package_name>.

   9

   Specify any additional images to include in the image set.

2. Follow the procedure in the "Mirroring an image set to a mirror registry" section.
3. Follow the procedure in the "Configuring image registry repository mirroring" section.

Procedure

1. Log in to the RHACM CLI using your OpenShift Container Platform credentials.

2. Create a namespace.

   $ oc create ns <namespace>

3. Create a Policy CR YAML file:

   Example Policy CR to install and configure LVM Storage

   apiVersion: apps.open-cluster-management.io/v1
   kind: PlacementRule
   metadata:
     name: placement-install-lvms
   spec:
     clusterConditions:
     - status: "True"
       type: ManagedClusterConditionAvailable
     clusterSelector: 

   1

   
       matchExpressions:
       - key: mykey
         operator: In
         values:
         - myvalue
   ---
   apiVersion: policy.open-cluster-management.io/v1
   kind: PlacementBinding
   metadata:
     name: binding-install-lvms
   placementRef:
     apiGroup: apps.open-cluster-management.io
     kind: PlacementRule
     name: placement-install-lvms
   subjects:
   - apiGroup: policy.open-cluster-management.io
     kind: Policy
     name: install-lvms
   ---
   apiVersion: policy.open-cluster-management.io/v1
   kind: Policy
   metadata:
     annotations:
       policy.open-cluster-management.io/categories: CM Configuration Management
       policy.open-cluster-management.io/controls: CM-2 Baseline Configuration
       policy.open-cluster-management.io/standards: NIST SP 800-53
     name: install-lvms
   spec:
     disabled: false
     remediationAction: enforce
     policy-templates:
     - objectDefinition:
         apiVersion: policy.open-cluster-management.io/v1
         kind: ConfigurationPolicy
         metadata:
           name: install-lvms
         spec:
           object-templates:
           - complianceType: musthave
             objectDefinition: 

   2

   
               apiVersion: v1
               kind: Namespace
               metadata:
                 labels:
                   openshift.io/cluster-monitoring: "true"
                   pod-security.kubernetes.io/enforce: privileged
                   pod-security.kubernetes.io/audit: privileged
                   pod-security.kubernetes.io/warn: privileged
                 name: openshift-lvm-storage
           - complianceType: musthave
             objectDefinition: 

   3

   
               apiVersion: operators.coreos.com/v1
               kind: OperatorGroup
               metadata:
                 name: openshift-storage-operatorgroup
                 namespace: openshift-lvm-storage
               spec:
                 targetNamespaces:
                 - openshift-lvm-storage
           - complianceType: musthave
             objectDefinition: 

   4

   
               apiVersion: operators.coreos.com/v1alpha1
               kind: Subscription
               metadata:
                 name: lvms
                 namespace: openshift-lvm-storage
               spec:
                 installPlanApproval: Automatic
                 name: lvms-operator
                 source: redhat-operators
                 sourceNamespace: openshift-marketplace
           remediationAction: enforce
           severity: low

   1

   Set the key field and values field in PlacementRule.spec.clusterSelector to match the labels that are configured in the clusters on which you want to install LVM Storage.

   2

   Namespace configuration.

   3

   The OperatorGroup CR configuration.

   4

   The Subscription CR configuration.

4. Create the Policy CR by running the following command:

   $ oc create -f <file_name> -n <namespace>

   Upon creating the Policy CR, the following custom resources are created on the clusters that match the selection criteria configured in the PlacementRule CR:

   • Namespace
   • OperatorGroup
   • Subscription