1- < h1 id ="installing-linstor-operator-v2 "> Installing LINSTOR Operator v2</ h1 >
2- < p > After < a href ="https://charts.linstor.io/migration/3-remove-operator-v1.html "> removing the LINSTOR Operator v1 deployment</ a > , you can install LINSTOR Operator v2.</ p >
3- < p > You can deploy the LINSTOR Operator v2 by using either the < a href ="https://kubernetes.io/docs/tasks/manage-kubernetes-objects/kustomization "> Kustomize</ a > tool, integrated with < code > kubectl</ code > , or else by using Helm and a LINBIT Helm chart.</ p >
4- < p > This is the last step when migrating the LINSTOR Operator from version 1 (v1) to version 2 (v2).</ p >
5- < h2 id ="prerequisites "> Prerequisites</ h2 >
6- < p > To install the LINSTOR Operator v2 into your current deployment, you will need to install the following tools:</ p >
7- < ul >
8- < li > < a href ="https://kubernetes.io/docs/tasks/tools/ "> < code > kubectl</ code > </ a > </ li >
9- < li > < a href ="https://docs.helm.sh/docs/intro/install/ "> Helm</ a > </ li >
10- </ ul >
11- < h2 id ="deploying-linstor-operator-v2-by-using-kustomize "> Deploying LINSTOR Operator v2 by Using Kustomize</ h2 >
12- < p > You can use < code > kubectl</ code > and the built-in < code > kustomize</ code > feature to deploy LINSTOR Operator v2.</ p >
13- < p > For instructions on how to do this, refer to the documentation in the
14- < a href ="https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-creating-operator-v2-kustomize "> < em > LINSTOR User’s
15- Guide</ em > </ a > . Follow the user’s guide instructions for deploying the Operator v2, After deploying the Operator, return to this page (Step 4) and continue to the “Deploying the LINBIT SDS Cluster” instructions below.</ p >
16- < h2 id ="deploying-linstor-operator-v2-by-using-helm "> Deploying LINSTOR Operator v2 by Using Helm</ h2 >
17- < p > You can also use Helm to deploy LINSTOR Operator v2.</ p >
18- < p > Instructions on how to do this are also in the < a href ="https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-creating-operator-helm "> < em > LINSTOR User’s
19- Guide</ em > </ a > . Follow the user’s guide instructions for deploying the Operator v2, After deploying the Operator, return to this page (Step 4) and continue to the “Deploying the LINBIT SDS Cluster” instructions below.</ p >
20- < h2 id ="deploying-the-linbit-sds-cluster "> Deploying the LINBIT SDS Cluster</ h2 >
21- < p > LINBIT SDS is the term that describes a LINSTOR and DRBD deployment. The LINSTOR
22- Operator is a part of a LINBIT SDS deployment in Kubernetes. After deploying the
23- LINSTOR Operator v2, you can fully deploy LINBIT SDS in your Kubernetes cluster by using the resources that you generated in < a href ="https://charts.linstor.io/migration/2-collect-information.html "> Step 2</ a > .</ p >
24- < h3 id ="creating-a-secret "> Creating a Secret</ h3 >
25- < p > When installing the LINSTOR Operator v1 by using Helm, Helm automatically generates a passphrase for LINSTOR. After Helm initializes LINSTOR with the passphrase, the LINSTOR controller will not be able to fully start without supplying the passphrase. In < a href ="https://charts.linstor.io/migration/2-collect-information.html "> Step 2</ a > of the migration instructions, you collected the passphrase from your existing Operator v1 deployment. You will use that passphrase to create a secret that you can use to migrate your resources into the Operator v2 deployment.</ p >
26- < p > To create the secret, enter the following commands:</ p >
27- < pre > < code > # PASSPHRASE=<passphrase-collected-from-kubectl-get-secrets-command-in-step-2>
28- # cat << EOF | kubectl apply -f - --server-side
1+ <!DOCTYPE html>
2+ < html lang ="en " xmlns ="http://www.w3.org/1999/html ">
3+ < head >
4+ < title > Removing the LINSTOR Operator v1 Deployment</ title >
5+ < meta http-equiv ="Content-Type " content ="text/html; charset=UTF-8 ">
6+ < meta name ="viewport " content ="width=device-width, initial-scale=1 ">
7+ < link rel ="stylesheet " href ="/content/mvp.css "/>
8+ < link rel ="icon " href ="/content/symbol.svg "/>
9+ </ head >
10+ < body >
11+ < header >
12+ < nav >
13+ < img alt ="Logo " src ="/content/linbit_sds.svg " height ="70 "/>
14+ < ul >
15+ < li > < a href ="/ "> Operator v2</ a > </ li >
16+ < li > < a href ="/migration/ "> Migration ▾</ a >
17+ < ul >
18+ < li > < a href ="1-migrate-db.html "> 1. Migrate Database</ a > </ li >
19+ < li > < a href ="2-collect-information.html "> 2. Collect Information</ a > </ li >
20+ < li > < a href ="3-remove-operator-v1.html "> 3. Remove Operator v1</ a > </ li >
21+ < li > 4. Install Operator v2</ li >
22+ </ ul >
23+ </ li >
24+ < li > < a href ="/helm.html "> Operator v1</ a > </ li >
25+ </ ul >
26+ </ nav >
27+
28+ < h1 id ="installing-linstor-operator-v2 "> Installing LINSTOR Operator v2</ h1 >
29+ </ header >
30+ < main >
31+ < article >
32+ < p >
33+ After < a href ="./3-remove-operator-v1.html "> removing the LINSTOR Operator v1 deployment</ a > , you can install
34+ LINSTOR Operator v2.
35+ </ p >
36+
37+ < p >
38+ You can deploy the LINSTOR Operator v2 by using either the
39+ < a href ="https://kubernetes.io/docs/tasks/manage-kubernetes-objects/kustomization "> Kustomize</ a > tool,
40+ integrated with < code > kubectl</ code > , or else by using Helm and a LINBIT Helm chart.
41+ </ p >
42+
43+ < p > This is the last step when migrating the LINSTOR Operator from version 1 (v1) to version 2 (v2).</ p >
44+
45+ < h2 id ="prerequisites "> Prerequisites</ h2 >
46+ < p >
47+ To install the LINSTOR Operator v2 into your current deployment, you will need to install the following
48+ tools:
49+ </ p >
50+
51+ < ul >
52+ < li > < a href ="https://kubernetes.io/docs/tasks/tools/ "> kubectl</ a > </ li >
53+ < li > < a href ="https://docs.helm.sh/docs/intro/install/ "> Helm</ a > </ li >
54+ </ ul >
55+
56+ < h2 id ="deploying-linstor-operator-v2-by-using-kustomize "> Deploying LINSTOR Operator v2 by Using Kustomize</ h2 >
57+ < p >
58+ You can use < code > kubectl</ code > and the built-in < code > kustomize</ code > feature to deploy LINSTOR Operator
59+ v2.</ p >
60+
61+ < p >
62+ For instructions on how to do this, refer to the documentation in the
63+ < em > < a href ="https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-creating-operator-v2-kustomize "> LINSTOR User’s Guide</ a > </ em > .
64+ Follow the user’s guide instructions for deploying the Operator v2, After deploying the Operator, return to
65+ this page (Step 4) and continue to the “Deploying the LINBIT SDS Cluster” instructions below.
66+ </ p >
67+
68+ < h2 id ="deploying-linstor-operator-v2-by-using-helm "> Deploying LINSTOR Operator v2 by Using Helm</ h2 >
69+ < p > You can also use Helm to deploy LINSTOR Operator v2.</ p >
70+
71+ < p >
72+ Instructions on how to do this are also in the
73+ < em > < a href ="https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-creating-operator-helm "> LINSTOR User’s Guide</ a > </ em > .
74+ Follow the user’s guide instructions for deploying the Operator v2, After deploying the Operator, return to
75+ this page (Step 4) and continue to the “Deploying the LINBIT SDS Cluster” instructions below.
76+ </ p >
77+
78+ < h2 id ="deploying-the-linbit-sds-cluster "> Deploying the LINBIT SDS Cluster</ h2 >
79+ < p >
80+ LINBIT SDS is the term that describes a LINSTOR and DRBD deployment. The LINSTOR
81+ Operator is a part of a LINBIT SDS deployment in Kubernetes. After deploying the
82+ LINSTOR Operator v2, you can fully deploy LINBIT SDS in your Kubernetes cluster by using the resources that
83+ you generated in < a href ="./2-collect-information.html#running-the-data-collection-script "> Step 2</ a > .
84+ </ p >
85+
86+ < h3 id ="creating-a-secret "> Creating a Secret</ h3 >
87+ < p >
88+ When installing the LINSTOR Operator v1 by using Helm, Helm automatically generates a passphrase for LINSTOR.
89+ After Helm initializes LINSTOR with the passphrase, the LINSTOR controller will not be able to fully start
90+ without supplying the passphrase. In < a href ="./2-collect-information.html#collecting-helm-generated-secrets "> Step 2</ a > of the migration
91+ instructions, you collected the passphrase from your existing Operator v1 deployment. You will use that
92+ passphrase to create a secret that you can use to migrate your resources into the Operator v2 deployment.
93+ </ p >
94+ < p > To create the secret, enter the following commands:</ p >
95+ < pre > < code > < span class ="console "> PASSPHRASE=<passphrase-collected-from-kubectl-get-secrets-command-in-step-2></ span >
96+ < span class ="console "> cat << EOF | kubectl apply -f - --server-side</ span >
2997apiVersion: v1
3098kind: Secret
3199metadata:
@@ -34,36 +102,48 @@ <h3 id="creating-a-secret">Creating a Secret</h3>
34102data:
35103 MASTER_PASSPHRASE: $PASSPHRASE
36104EOF
37- # unset PASSPHRASE</ code > </ pre >
38- < p > Output from a successful < code > kubectl apply</ code > command will show that the secret was
39- applied.</ p >
40- < pre > < code > secret/linstor-op-passphrase serverside-applied</ code > </ pre >
41- < h3 id ="applying-resources "> Applying Resources</ h3 >
42- < p > Next, apply the resources that you collected in a < code > v2-resources.yaml</ code > file by
43- running the collection script in the < a href ="https://charts.linstor.io/migration/3-remove-operator-v1.html "> Step
44- 2</ a > instructions.</ p >
45- < pre > < code > # kubectl apply -f v2-resources.yaml --server-side</ code > </ pre >
46- < blockquote >
47- < p > 💡 < strong > TIP:</ strong > In < a href ="https://charts.linstor.io/migration/2-collect-information.html "> Step
48- 2</ a > , you ran
49- the information collection script from the < code > piraeus-operator</ code > directory that
50- you cloned locally from the upstream GitHub project. Unless you moved it, this
51- is the directory where you can find the script-generated < code > v2-resources.yaml</ code >
52- file.</ p >
53- </ blockquote >
54- < p > Output from a successful command will show that your resources were created.</ p >
55- < pre > < code > linstorcluster.piraeus.io/linstorcluster serverside-applied
105+ < span class ="console "> unset PASSPHRASE</ span > </ code > </ pre >
106+
107+ < p > Output from a successful < code > kubectl apply</ code > command will show that the secret was applied.</ p >
108+ < pre > < code > secret/linstor-op-passphrase serverside-applied</ code > </ pre >
109+
110+ < h3 id ="applying-resources "> Applying Resources</ h3 >
111+ < p >
112+ Next, apply the resources that you collected in a < code > v2-resources.yaml</ code > file by running the
113+ collection script in the < a href ="./2-collect-information.html#running-the-data-collection-script "> Step 2</ a >
114+ instructions.
115+ </ p >
116+
117+ < pre > < code class ="console "> kubectl apply -f v2-resources.yaml --server-side</ code > </ pre >
118+
119+ < p > Output from a successful command will show that your resources were created.</ p >
120+
121+ < pre > < code > linstorcluster.piraeus.io/linstorcluster serverside-applied
56122linstorsatelliteconfiguration.piraeus.io/host-networking serverside-applied
57123linstorsatelliteconfiguration.piraeus.io/linstor-op-ns serverside-applied</ code > </ pre >
58- < p > Now the cluster will come up, using the existing data to restore the cluster state.</ p >
59- < h2 id ="verifying-cluster-state "> Verifying Cluster State</ h2 >
60- < p > Before verifying your cluster state, you can change your < code > kubectl</ code > command
61- context to the < code > linbit-sds</ code > namespace, by entering the following command:</ p >
62- < pre > < code > # kubectl config set-context --current --namespace=linbit-sds</ code > </ pre >
63- < p > Next, you can check the cluster state by using various < code > linstor</ code > command line client commands:</ p >
64- < pre > < code > # kubectl exec deploy/linstor-controller -- linstor node list
65- # kubectl exec deploy/linstor-controller -- linstor storage-pool list
66- # kubectl exec deploy/linstor-controller -- linstor resource list-volumes
67- # kubectl exec deploy/linstor-controller -- linstor error-reports list</ code > </ pre >
68- < p > You can also < a href ="https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-basic-configuration-and-deployment "> provision new
69- volumes</ a > , to verify that the cluster is operational.</ p >
124+
125+ < p > Now the cluster will come up, using the existing data to restore the cluster state.</ p >
126+
127+ < h2 id ="verifying-cluster-state "> Verifying Cluster State</ h2 >
128+ < p >
129+ Before verifying your cluster state, you can change your < code > kubectl</ code > command context to the
130+ < code > linbit-sds</ code > namespace, by entering the following command:
131+ </ p >
132+
133+ < pre > < code class ="console "> kubectl config set-context --current --namespace=linbit-sds</ code > </ pre >
134+
135+ < p > Next, you can check the cluster state by using various < code > linstor</ code > command line client commands:</ p >
136+ < pre > < code > < span class ="console "> kubectl exec deploy/linstor-controller -- linstor node list</ span >
137+ < span class ="console "> kubectl exec deploy/linstor-controller -- linstor storage-pool list</ span >
138+ < span class ="console "> kubectl exec deploy/linstor-controller -- linstor resource list-volumes</ span >
139+ < span class ="console "> kubectl exec deploy/linstor-controller -- linstor error-reports list</ span > </ code > </ pre >
140+
141+ < p >
142+ You can also
143+ < a href ="https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-basic-configuration-and-deployment "> provision new volumes</ a > ,
144+ to verify that the cluster is operational.
145+ </ p >
146+ </ article >
147+ </ main >
148+ </ body >
149+ </ html >
0 commit comments