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.
cisco-open · Mar 20, 2023 · f33ca78 · f33ca78
1 parent 225c86d
commit f33ca78
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 5 deletions.
diff --git 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
@@ -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
@@ -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
@@ -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