Instruction-how-to-change-image-on-47lining-cluster.md

@@ -18,7 +18,14 @@
    kubectl -n osdu-instance-r3m18-core get deployment os-storage -o yaml \> storage-deployment.20240521.yaml
 
    ![image.png](uploads/ee26d93036af0f1967b7afc4619bb872/image.png){width="519" height="17"}
-5. Edit deploy
+5. For finding path to new image we should run pipeline with new functionality. Job aws-containerize should be green. Go to job containerize -\> aws-containerize
+
+   ![image.png](uploads/42c7e90d254080851758f7f1e4758c92/image.png){width="580" height="277"}
+
+   In our case string 63 successfully tagged. And copy this path
+
+   ![image.png](uploads/7972b1256bf12b6125c8f15e8e92cdac/image.png){width="616" height="115"}
+6. Edit deploy
 
    kubectl -n osdu-instance-r3m18-core edit deploy os-storage
 
@@ -33,13 +40,6 @@
    After:
 
    ![image.png](uploads/1076e221d406d452a3c71ed11c1194b2/image.png){width="396" height="449"}
-6. Find path to new image we can in pipeline. Go to job containerize -\> aws-containerize
-
-   ![image.png](uploads/42c7e90d254080851758f7f1e4758c92/image.png){width="580" height="277"}
-
-   In our case string 63 successfully tagged. And copy this path
-
-   ![image.png](uploads/7972b1256bf12b6125c8f15e8e92cdac/image.png){width="616" height="115"}
 7. At the end we can watch the pods. It should be running
 
    kubectl -n osdu-instance-r3m18-core get pod | grep os-storage