Update Instruction how to change image on 47lining cluster authored by Pavel Barzou's avatar Pavel Barzou
...@@ -2,48 +2,50 @@ ...@@ -2,48 +2,50 @@
aws configure sso aws configure sso
![image.png](uploads/7ce4d148b24bb902245131bde26d1909/image.png){width=252 height=94} ![image.png](uploads/7ce4d148b24bb902245131bde26d1909/image.png){width="252" height="94"}
2. Find all deployments 2. Find all deployments
kubectl -n osdu-instance-r3m18-core get deployment kubectl -n osdu-instance-r3m18-core get deployment
![image.png](uploads/2cef9d6dd219418250296a13e5156de5/image.png){width=327 height=170} ![image.png](uploads/2cef9d6dd219418250296a13e5156de5/image.png){width="327" height="170"}
3. To see what image on server 3. To see what image on server
kubectl -n osdu-instance-r3m18-core get deploy os-storage -o yaml kubectl -n osdu-instance-r3m18-core get deploy os-storage -o yaml
![image.png](uploads/35dbc21244fbfa77c98f76e9711c62fa/image.png){width=330 height=52} ![image.png](uploads/35dbc21244fbfa77c98f76e9711c62fa/image.png){width="330" height="52"}
4. Save definition of deployment 4. Save definition of deployment
kubectl -n osdu-instance-r3m18-core get deployment os-storage -o yaml \> storage-deployment.20240521.yaml 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} ![image.png](uploads/ee26d93036af0f1967b7afc4619bb872/image.png){width="519" height="17"}
5. Edit deploy 5. Edit deploy
kubectl -n osdu-instance-r3m18-core edit deploy os-storage kubectl -n osdu-instance-r3m18-core edit deploy os-storage
![image.png](uploads/3d0fb30faf0aab5764d92c664f65e7aa/image.png){width=356 height=37} ![image.png](uploads/3d0fb30faf0aab5764d92c664f65e7aa/image.png){width="356" height="37"}
And after that to change in opened file path to image And after that to change in opened file path to image
Before: Before:
![image.png](uploads/9c35d3aa71242fed07bad711de0aee30/image.png){width=403 height=406} ![image.png](uploads/9c35d3aa71242fed07bad711de0aee30/image.png){width="403" height="406"}
After: After:
![image.png](uploads/1076e221d406d452a3c71ed11c1194b2/image.png){width=396 height=449} ![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 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} ![image.png](uploads/42c7e90d254080851758f7f1e4758c92/image.png){width="580" height="277"}
In our case string 63 successfully tagged. And copy this path In our case string 63 successfully tagged. And copy this path
![image.png](uploads/7972b1256bf12b6125c8f15e8e92cdac/image.png){width=616 height=115} ![image.png](uploads/7972b1256bf12b6125c8f15e8e92cdac/image.png){width="616" height="115"}
7. At the end we can watch the pods. It should be running 7. At the end we can watch the pods. It should be running
kubectl -n osdu-instance-r3m18-core get pod | grep os-storage kubectl -n osdu-instance-r3m18-core get pod | grep os-storage
![image.png](uploads/4eb30ee059b5a37918b25959f27d6625/image.png){width=457 height=42} ![image.png](uploads/4eb30ee059b5a37918b25959f27d6625/image.png){width="457" height="42"}
If you change image first time you should fix startup check, delete liveness check and health check. If you change image first time you should fix startup check, delete liveness check and health check.
![Fix startup check.mp4](uploads/30deae11eb67ca78feea8650fe92785e/Fix_startup_check.mp4)
\ No newline at end of file