Skip to content

Commit f33ca78

Browse files
authored
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.
1 parent 225c86d commit f33ca78

File tree

4 files changed

+5
-5
lines changed

4 files changed

+5
-5
lines changed

docs/03-b-amzn2-gpu.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -231,7 +231,7 @@ Error: INSTALLATION FAILED: failed post-install: timed out waiting for the condi
231231
This issue may be because container images are large or the Internet connection is slow.
232232
The issue has been reported in minikube [github](https://github.com/kubernetes/minikube/issues/14789).
233233
The latest minikube still doesn't contain the patched component (cri-dockerd 0.2.6).
234-
A workaround is to pull images manually (e.g. `minikube ssh docker pull ciscoresearch/flame:latest`).
234+
A workaround is to pull images manually (e.g. `minikube ssh docker pull ciscoresearch/flame:v0.2.2`).
235235
The command `kubectl get pods -n flame` gives a list of pods and their status.
236236
The pods with `ErrImagePull` or `ImagePullBackOff` status are ones that might be affected by the issue.
237237
Identifying the required image can be done by running a `kubectl describe` command

docs/03-c-mac.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -181,7 +181,7 @@ Error: INSTALLATION FAILED: failed post-install: timed out waiting for the condi
181181
This issue may be because container images are large or the Internet connection is slow.
182182
The issue has been reported in minikube [github](https://github.com/kubernetes/minikube/issues/14789).
183183
The latest minikube still doesn't contain the patched component (cri-dockerd 0.2.6).
184-
A workaround is to pull images manually (e.g. `minikube ssh docker pull ciscoresearch/flame:latest`).
184+
A workaround is to pull images manually (e.g. `minikube ssh docker pull ciscoresearch/flame:v0.2.2`).
185185
The command `kubectl get pods -n flame` gives a list of pods and their status.
186186
The pods with `ErrImagePull` or `ImagePullBackOff` status are ones that might be affected by the issue.
187187
Identifying the required image can be done by running a `kubectl describe` command

fiab/helm-chart/control/values.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -64,9 +64,9 @@ minio:
6464
- minio.flame.test
6565

6666
imageName: ciscoresearch/flame
67-
imageTag: latest
67+
imageTag: v0.2.2
6868
workerImageName: ciscoresearch/flame
69-
workerImageTag: latest
69+
workerImageTag: v0.2.2
7070

7171
broker:
7272
- sort: mqtt

fiab/helm-chart/deployer/values.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ minio:
2222
policy: readwrite
2323

2424
imageName: ciscoresearch/flame
25-
imageTag: latest
25+
imageTag: v0.2.2
2626

2727
frontDoorUrl:
2828
apiserver: apiserver.flame.test # apiserver url needs to be updated

0 commit comments

Comments
 (0)