From f33ca782732c2c3f8d1ba3905ef80661f4cfe7e5 Mon Sep 17 00:00:00 2001
From: openwithcode <123649857+openwithcode@users.noreply.github.com>
Date: Mon, 20 Mar 2023 16:40:08 +0200
Subject: [PATCH] build: use the flame version for which the code was released
 for (#371)

This is useful to avoid future issues in case we release new versions, but the local flame code/cluster is not upgraded to use the latest released code.
---
 docs/03-b-amzn2-gpu.md               | 2 +-
 docs/03-c-mac.md                     | 2 +-
 fiab/helm-chart/control/values.yaml  | 4 ++--
 fiab/helm-chart/deployer/values.yaml | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/03-b-amzn2-gpu.md b/docs/03-b-amzn2-gpu.md
index ca164028f..c69c0a401 100644
--- a/docs/03-b-amzn2-gpu.md
+++ b/docs/03-b-amzn2-gpu.md
@@ -231,7 +231,7 @@ Error: INSTALLATION FAILED: failed post-install: timed out waiting for the condi
 This issue may be because container images are large or the Internet connection is slow.
 The issue has been reported in minikube [github](https://github.com/kubernetes/minikube/issues/14789).
 The latest minikube still doesn't contain the patched component (cri-dockerd 0.2.6).
-A workaround is to pull images manually (e.g. `minikube ssh docker pull ciscoresearch/flame:latest`).
+A workaround is to pull images manually (e.g. `minikube ssh docker pull ciscoresearch/flame:v0.2.2`).
 The command `kubectl get pods -n flame` gives a list of pods and their status.
 The pods with `ErrImagePull` or `ImagePullBackOff` status are ones that might be affected by the issue.
 Identifying the required image can be done by running a `kubectl describe` command
diff --git a/docs/03-c-mac.md b/docs/03-c-mac.md
index 18c790124..a1c1c172e 100644
--- a/docs/03-c-mac.md
+++ b/docs/03-c-mac.md
@@ -181,7 +181,7 @@ Error: INSTALLATION FAILED: failed post-install: timed out waiting for the condi
 This issue may be because container images are large or the Internet connection is slow.
 The issue has been reported in minikube [github](https://github.com/kubernetes/minikube/issues/14789).
 The latest minikube still doesn't contain the patched component (cri-dockerd 0.2.6).
-A workaround is to pull images manually (e.g. `minikube ssh docker pull ciscoresearch/flame:latest`).
+A workaround is to pull images manually (e.g. `minikube ssh docker pull ciscoresearch/flame:v0.2.2`).
 The command `kubectl get pods -n flame` gives a list of pods and their status.
 The pods with `ErrImagePull` or `ImagePullBackOff` status are ones that might be affected by the issue.
 Identifying the required image can be done by running a `kubectl describe` command
diff --git a/fiab/helm-chart/control/values.yaml b/fiab/helm-chart/control/values.yaml
index 6f2dd5338..c6cbf960b 100644
--- a/fiab/helm-chart/control/values.yaml
+++ b/fiab/helm-chart/control/values.yaml
@@ -64,9 +64,9 @@ minio:
       - minio.flame.test
 
 imageName: ciscoresearch/flame
-imageTag: latest
+imageTag: v0.2.2
 workerImageName: ciscoresearch/flame
-workerImageTag: latest
+workerImageTag: v0.2.2
 
 broker:
   - sort: mqtt
diff --git a/fiab/helm-chart/deployer/values.yaml b/fiab/helm-chart/deployer/values.yaml
index 65fc60bf9..0b2181e43 100644
--- a/fiab/helm-chart/deployer/values.yaml
+++ b/fiab/helm-chart/deployer/values.yaml
@@ -22,7 +22,7 @@ minio:
       policy: readwrite
 
 imageName: ciscoresearch/flame
-imageTag: latest
+imageTag: v0.2.2
 
 frontDoorUrl:
   apiserver: apiserver.flame.test      # apiserver url needs to be updated