Skip to content

Commit

Permalink
Add image registry example to story 2
Browse files Browse the repository at this point in the history
Signed-off-by: Stefan Prodan <[email protected]>
  • Loading branch information
stefanprodan committed Apr 1, 2022
1 parent 9ef9295 commit 2240dbe
Showing 1 changed file with 12 additions and 3 deletions.
15 changes: 12 additions & 3 deletions rfcs/helm-oci/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ And finally in Flux `HelmReleases`, refer to the ghcr-charts `HelmRepository`:
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
name: podinfo
name: my-app
namespace: default
spec:
interval: 60m
Expand All @@ -98,10 +98,19 @@ spec:
Given that charts are stored in container registries, you can use Flux image automation
and patch the chart version in Git, in the same way Flux works for updating container image tags.

Define an image policy using semver:
Define an image registry and a policy for the chart artifact:

```yaml
apiVersion: image.toolkit.fluxcd.io/v1beta1
kind: ImageRepository
metadata:
name: my-app
namespace: default
spec:
image: ghcr.io/my-org/charts/my-app
interval: 1m0s
---
apiVersion: image.toolkit.fluxcd.io/v1beta1
kind: ImagePolicy
metadata:
name: my-app
Expand All @@ -120,7 +129,7 @@ Then add the policy marker to the `HelmRelease` manifests in Git:
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
name: podinfo
name: my-app
namespace: default
spec:
interval: 60m
Expand Down

0 comments on commit 2240dbe

Please sign in to comment.