Mirrors/flux2
1
0
Fork 0
mirror of synced 2026-02-06 19:05:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update semver flag in image update guide

Browse Source 
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
This commit is contained in:
Stefan Prodan
2021-02-12 18:23:25 +02:00
parent 11f8e2ffde
commit 0fbeb6d2cd
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/guides/image-update.md
View File

@@ -170,7 +170,7 @@ Create an `ImagePolicy` to tell Flux which semver range to use when filtering ta
```sh ```sh
flux create image policy podinfo \ flux create image policy podinfo \
--image-ref=podinfo \ --image-ref=podinfo \
--semver=5.0.x \ --select-semver=5.0.x \
--export > ./clusters/my-cluster/podinfo-policy.yaml --export > ./clusters/my-cluster/podinfo-policy.yaml
``` ```
@@ -471,7 +471,7 @@ Assuming you've configured Flux to update an app to its latest stable version:
```sh ```sh
flux create image policy podinfo \ flux create image policy podinfo \
--image-ref=podinfo \ --image-ref=podinfo \
--semver=">=5.0.0" --select-semver=">=5.0.0"
``` ```
If the latest version e.g. `5.0.1` causes an incident in production, you can tell Flux to If the latest version e.g. `5.0.1` causes an incident in production, you can tell Flux to
@@ -480,7 +480,7 @@ revert the image tag to a previous version e.g. `5.0.0` with:
```sh ```sh
flux create image policy podinfo \ flux create image policy podinfo \
--image-ref=podinfo \ --image-ref=podinfo \
--semver=5.0.0 --select-semver=5.0.0
``` ```
Or by changing the semver range in Git: Or by changing the semver range in Git:
@@ -505,7 +505,7 @@ and tell Flux to consider only versions greater than `5.0.1`:
```sh ```sh
flux create image policy podinfo \ flux create image policy podinfo \
--image-ref=podinfo \ --image-ref=podinfo \
--semver=">5.0.1" --select-semver=">5.0.1"
``` ```
## ImageRepository cloud providers authentication ## ImageRepository cloud providers authentication