mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
OSDOCS#15433: Updated the default namespace LVMS to openshift-lvm-storage
This commit is contained in:
srir
@@ -27,6 +27,7 @@ apiVersion: policy.open-cluster-management.io/v1
|
||||
kind: ConfigurationPolicy
|
||||
metadata:
|
||||
name: lvms
|
||||
namespace: openshift-lvm-storage
|
||||
spec:
|
||||
object-templates:
|
||||
- complianceType: musthave
|
||||
@@ -35,7 +36,7 @@ spec:
|
||||
kind: LVMCluster
|
||||
metadata:
|
||||
name: my-lvmcluster
|
||||
namespace: openshift-storage
|
||||
namespace: openshift-lvm-storage
|
||||
spec:
|
||||
storage:
|
||||
deviceClasses: <1>
|
||||
|
||||
@@ -36,6 +36,7 @@ apiVersion: lvm.topolvm.io/v1alpha1
|
||||
kind: LVMCluster
|
||||
metadata:
|
||||
name: my-lvmcluster
|
||||
namespace: openshift-lvm-storage
|
||||
spec:
|
||||
# ...
|
||||
storage:
|
||||
|
||||
@@ -27,7 +27,7 @@ You can only create a single instance of the `LVMCluster` custom resource (CR) o
|
||||
|
||||
. Log in to the {product-title} web console.
|
||||
. Click *Operators* -> *Installed Operators*.
|
||||
. In the `openshift-storage` namespace, click *LVM Storage*.
|
||||
. In the `openshift-lvm-storage` namespace, click *{lvms}*.
|
||||
. Click *Create LVMCluster* and select either *Form view* or *YAML view*.
|
||||
. Configure the required `LVMCluster` CR parameters.
|
||||
. Click *Create*.
|
||||
|
||||
@@ -20,7 +20,7 @@ You can delete the `LVMCluster` custom resource (CR) using the OpenShift CLI (`o
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ oc delete lvmcluster <lvm_cluster_name> -n openshift-storage
|
||||
$ oc delete lvmcluster <lvm_cluster_name> -n <namespace>
|
||||
----
|
||||
|
||||
.Verification
|
||||
@@ -35,5 +35,5 @@ $ oc get lvmcluster -n <namespace>
|
||||
.Example output
|
||||
[source,terminal]
|
||||
----
|
||||
No resources found in openshift-storage namespace.
|
||||
No resources found in openshift-lvm-storage namespace.
|
||||
----
|
||||
|
||||
@@ -56,7 +56,7 @@ spec:
|
||||
apiVersion: lvm.topolvm.io/v1alpha1
|
||||
metadata:
|
||||
name: my-lvmcluster
|
||||
namespace: openshift-storage <2>
|
||||
namespace: openshift-lvm-storage <2>
|
||||
---
|
||||
apiVersion: policy.open-cluster-management.io/v1
|
||||
kind: PlacementBinding
|
||||
@@ -87,7 +87,7 @@ spec:
|
||||
- myvalue
|
||||
----
|
||||
<1> The `spec.remediationAction` in `policy-template` is overridden by the preceding parameter value for `spec.remediationAction`.
|
||||
<2> This `namespace` field must have the `openshift-storage` value.
|
||||
<2> This `namespace` field must have the `openshift-lvm-storage` value.
|
||||
<3> Configure the requirements to select the clusters. {lvms} is uninstalled on the clusters that match the selection criteria.
|
||||
|
||||
. Create the `Policy` CR by running the following command:
|
||||
@@ -129,7 +129,7 @@ spec:
|
||||
apiVersion: lvm.topolvm.io/v1alpha1
|
||||
metadata:
|
||||
name: my-lvmcluster
|
||||
namespace: openshift-storage <2>
|
||||
namespace: openshift-lvm-storage <2>
|
||||
---
|
||||
apiVersion: policy.open-cluster-management.io/v1
|
||||
kind: PlacementBinding
|
||||
@@ -160,7 +160,7 @@ spec:
|
||||
- myvalue
|
||||
----
|
||||
<1> The `policy-template` `spec.remediationAction` is overridden by the preceding parameter value for `spec.remediationAction`.
|
||||
<2> The `namespace` field must have the `openshift-storage` value.
|
||||
<2> The `namespace` field must have the `openshift-lvm-storage` value.
|
||||
|
||||
. Create the `Policy` CR by running the following command:
|
||||
+
|
||||
|
||||
@@ -17,7 +17,7 @@ You can delete the `LVMCluster` custom resource (CR) using the {product-title} w
|
||||
|
||||
. Log in to the {product-title} web console.
|
||||
. Click *Operators* → *Installed Operators* to view all the installed Operators.
|
||||
. Click *LVM Storage* in the `openshift-storage` namespace.
|
||||
. Click *{lvms}* in the `openshift-lvm-storage` namespace.
|
||||
. Click the *LVMCluster* tab.
|
||||
. From the *Actions*, select *Delete LVMCluster*.
|
||||
. Click *Delete*.
|
||||
|
||||
@@ -8,6 +8,11 @@
|
||||
|
||||
As a cluster administrator, you can install {lvms} by using the OpenShift CLI.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
The default namespace for the {lvms} Operator is `openshift-lvm-storage`.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
|
||||
* You have installed the OpenShift CLI (`oc`).
|
||||
@@ -28,7 +33,7 @@ metadata:
|
||||
pod-security.kubernetes.io/enforce: privileged
|
||||
pod-security.kubernetes.io/audit: privileged
|
||||
pod-security.kubernetes.io/warn: privileged
|
||||
name: openshift-storage
|
||||
name: openshift-lvm-storage
|
||||
----
|
||||
|
||||
. Create the namespace by running the following command:
|
||||
@@ -47,7 +52,7 @@ apiVersion: operators.coreos.com/v1
|
||||
kind: OperatorGroup
|
||||
metadata:
|
||||
name: openshift-storage-operatorgroup
|
||||
namespace: openshift-storage
|
||||
namespace: openshift-lvm-storage
|
||||
spec:
|
||||
targetNamespaces:
|
||||
- openshift-storage
|
||||
@@ -69,7 +74,7 @@ apiVersion: operators.coreos.com/v1alpha1
|
||||
kind: Subscription
|
||||
metadata:
|
||||
name: lvms
|
||||
namespace: openshift-storage
|
||||
namespace: openshift-lvm-storage
|
||||
spec:
|
||||
installPlanApproval: Automatic
|
||||
name: lvms-operator
|
||||
@@ -90,7 +95,7 @@ $ oc create -f <file_name>
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ oc get csv -n openshift-storage -o custom-columns=Name:.metadata.name,Phase:.status.phase
|
||||
$ oc get csv -n openshift-lvm-storage -o custom-columns=Name:.metadata.name,Phase:.status.phase
|
||||
----
|
||||
+
|
||||
.Example output
|
||||
|
||||
@@ -8,6 +8,11 @@
|
||||
|
||||
You can install {lvms} by using the {product-title} web console.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
The default namespace for the {lvms} Operator is `openshift-lvm-storage`.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
|
||||
* You have access to the cluster.
|
||||
@@ -22,7 +27,7 @@ You can install {lvms} by using the {product-title} web console.
|
||||
.. *Update Channel* as *stable-{product-version}*.
|
||||
.. *Installation Mode* as *A specific namespace on the cluster*.
|
||||
.. *Installed Namespace* as *Operator recommended namespace openshift-storage*.
|
||||
If the `openshift-storage` namespace does not exist, it is created during the operator installation.
|
||||
If the `openshift-lvm-storage` namespace does not exist, it is created during the operator installation.
|
||||
.. *Update approval* as *Automatic* or *Manual*.
|
||||
+
|
||||
[NOTE]
|
||||
|
||||
@@ -91,24 +91,24 @@ spec:
|
||||
pod-security.kubernetes.io/enforce: privileged
|
||||
pod-security.kubernetes.io/audit: privileged
|
||||
pod-security.kubernetes.io/warn: privileged
|
||||
name: openshift-storage
|
||||
name: openshift-lvm-storage
|
||||
- complianceType: musthave
|
||||
objectDefinition: <3>
|
||||
apiVersion: operators.coreos.com/v1
|
||||
kind: OperatorGroup
|
||||
metadata:
|
||||
name: openshift-storage-operatorgroup
|
||||
namespace: openshift-storage
|
||||
namespace: openshift-lvm-storage
|
||||
spec:
|
||||
targetNamespaces:
|
||||
- openshift-storage
|
||||
- openshift-lvm-storage
|
||||
- complianceType: musthave
|
||||
objectDefinition: <4>
|
||||
apiVersion: operators.coreos.com/v1alpha1
|
||||
kind: Subscription
|
||||
metadata:
|
||||
name: lvms
|
||||
namespace: openshift-storage
|
||||
namespace: openshift-lvm-storage
|
||||
spec:
|
||||
installPlanApproval: Automatic
|
||||
name: lvms-operator
|
||||
@@ -134,3 +134,8 @@ Upon creating the `Policy` CR, the following custom resources are created on the
|
||||
* `Namespace`
|
||||
* `OperatorGroup`
|
||||
* `Subscription`
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
The default namespace for the {lvms} Operator is `openshift-lvm-storage`.
|
||||
====
|
||||
|
||||
@@ -42,7 +42,7 @@ spec:
|
||||
kind: LVMCluster
|
||||
metadata:
|
||||
name: my-lvmcluster
|
||||
namespace: openshift-storage
|
||||
namespace: openshift-lvm-storage
|
||||
spec:
|
||||
storage:
|
||||
deviceClasses:
|
||||
|
||||
@@ -17,7 +17,7 @@ You can scale up the storage capacity of the worker nodes on a cluster by using
|
||||
|
||||
. Log in to the {product-title} web console.
|
||||
. Click *Operators* -> *Installed Operators*.
|
||||
. Click *LVM Storage* in the `openshift-storage` namespace.
|
||||
. Click *{lvms}* in the `openshift-lvm-storage` namespace.
|
||||
. Click the *LVMCluster* tab to view the `LVMCluster` CR created on the cluster.
|
||||
. From the *Actions* menu, select *Edit LVMCluster*.
|
||||
. Click the *YAML* tab.
|
||||
|
||||
@@ -21,11 +21,11 @@ If the disk or node-related problems persist even after you have completed the t
|
||||
|
||||
.Procedure
|
||||
|
||||
. Switch to the `openshift-storage` namespace by running the following command:
|
||||
. Switch to the namespace where you have installed the {lvms} Operator by running the following command:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ oc project openshift-storage
|
||||
$ oc project <namespace>
|
||||
----
|
||||
|
||||
. Check if the `LogicalVolume` custom resources (CRs) are present by running the following command:
|
||||
|
||||
@@ -19,7 +19,7 @@ If you encounter the `storage class not found` error, check the `LVMCluster` cus
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ oc get lvmcluster -n openshift-storage
|
||||
$ oc get lvmcluster -n <namespace>
|
||||
----
|
||||
+
|
||||
.Example output
|
||||
@@ -31,11 +31,11 @@ my-lvmcluster 65m
|
||||
|
||||
. If the `LVMCluster` CR is not present, create an `LVMCluster` CR. For more information, see "Ways to create an LVMCluster custom resource".
|
||||
|
||||
. In the `openshift-storage` namespace, check that all the {lvms} pods are in the `Running` state by running the following command:
|
||||
. In the namespace where the operator is installed, check that all the {lvms} pods are in the `Running` state by running the following command:
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ oc get pods -n openshift-storage
|
||||
$ oc get pods -n <namespace>
|
||||
----
|
||||
+
|
||||
.Example output
|
||||
@@ -57,5 +57,5 @@ If the `vg-manager` pod is stuck while loading a configuration file, it is due t
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ oc logs -l app.kubernetes.io/component=vg-manager -n openshift-storage
|
||||
$ oc logs -l app.kubernetes.io/component=vg-manager -n <namespace>
|
||||
----
|
||||
|
||||
@@ -21,7 +21,7 @@ To identify the failed node, you can examine the restart count of the `topolvm-n
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ oc get pods -n openshift-storage
|
||||
$ oc get pods -n <namespace>
|
||||
----
|
||||
+
|
||||
.Example output
|
||||
|
||||
@@ -19,7 +19,7 @@ You can uninstall {lvms} using the {product-title} web console.
|
||||
|
||||
. Log in to the {product-title} web console.
|
||||
. Click *Operators* → *Installed Operators*.
|
||||
. Click *LVM Storage* in the `openshift-storage` namespace.
|
||||
. Click *{lvms}* in the `openshift-lvm-storage` namespace.
|
||||
. Click the *Details* tab.
|
||||
. From the *Actions* menu, select *Uninstall Operator*.
|
||||
. Optional: When prompted, select the *Delete all operand instances for this operator* checkbox to delete the operand instances for {lvms}.
|
||||
|
||||
@@ -82,24 +82,24 @@ spec:
|
||||
apiVersion: v1
|
||||
kind: Namespace
|
||||
metadata:
|
||||
name: openshift-storage
|
||||
name: openshift-lvm-storage
|
||||
- complianceType: mustnothave
|
||||
objectDefinition:
|
||||
apiVersion: operators.coreos.com/v1
|
||||
kind: OperatorGroup
|
||||
metadata:
|
||||
name: openshift-storage-operatorgroup
|
||||
namespace: openshift-storage
|
||||
namespace: openshift-lvm-storage
|
||||
spec:
|
||||
targetNamespaces:
|
||||
- openshift-storage
|
||||
- openshift-lvm-storage
|
||||
- complianceType: mustnothave
|
||||
objectDefinition:
|
||||
apiVersion: operators.coreos.com/v1alpha1
|
||||
kind: Subscription
|
||||
metadata:
|
||||
name: lvms-operator
|
||||
namespace: openshift-storage
|
||||
namespace: openshift-lvm-storage
|
||||
remediationAction: enforce
|
||||
severity: low
|
||||
- objectDefinition:
|
||||
|
||||
@@ -8,6 +8,11 @@
|
||||
|
||||
You can update {lvms} to ensure compatibility with the {product-title} version.
|
||||
|
||||
[NOTE]
|
||||
====
|
||||
The default namespace for the {lvms} Operator is `openshift-lvm-storage`.
|
||||
====
|
||||
|
||||
.Prerequisites
|
||||
|
||||
* You have updated your {product-title} cluster.
|
||||
@@ -26,7 +31,7 @@ You can update {lvms} to ensure compatibility with the {product-title} version.
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ oc patch subscription lvms-operator -n openshift-storage --type merge --patch '{"spec":{"channel":"<update_channel>"}}' <1>
|
||||
$ oc patch subscription lvms-operator -n openshift-lvm-storage --type merge --patch '{"spec":{"channel":"<update_channel>"}}' <1>
|
||||
----
|
||||
<1> Replace `<update_channel>` with the version of {lvms} that you want to install. For example, `stable-{product-version}`.
|
||||
|
||||
@@ -34,7 +39,7 @@ $ oc patch subscription lvms-operator -n openshift-storage --type merge --patch
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ oc get events -n openshift-storage
|
||||
$ oc get events -n openshift-lvm-storage
|
||||
----
|
||||
+
|
||||
.Example output
|
||||
@@ -56,7 +61,7 @@ $ oc get events -n openshift-storage
|
||||
+
|
||||
[source,terminal]
|
||||
----
|
||||
$ oc get subscription lvms-operator -n openshift-storage -o jsonpath='{.status.installedCSV}'
|
||||
$ oc get subscription lvms-operator -n openshift-lvm-storage -o jsonpath='{.status.installedCSV}'
|
||||
----
|
||||
+
|
||||
.Example output
|
||||
|
||||
Reference in New Issue
Block a user