You don't have javascript enabled. Good luck! :(

Installation Docs

Find the official installation docs for v2.23 at teamhephy.info.

If you have any issues, please be sure to report it on the slack community — (Edit: temporarily, the inviter is down! Please bear with us until it's resolved...), or report them on the issue tracker on GitHub.

  Sep 12, 2022     Team Hephy     attic  UPDATE: Mar 4, 2024

Chartmuseum, and What Comes After That

blog 2022 attic tutorial

I needed a place to put this Chartmuseum doc in case someone asks about what happened to the Chartmuseum example under this HelmReleases guide heading. What comes after? (Well, click on that link and you’ll see! Flux’s new OCIRepository source API is what’s recommended now, for performance and scalability reasons!)

The text below is provided as it was from the link above, without alteration and for posterity

It should not be interpreted to mean that I am still recommending Chartmuseum above OCI Charts.


A better option is to use Chartmuseum and run a cluster local Helm repository that can be used by source controller. Chartmuseum has support for multiple different cloud storage solutions such as S3, GCS, and Azure Blob Storage, meaning that you are not limited to only using storage providers that support the S3 protocol.

You can deploy a Chartmuseum instance with a HelmRelease that exposes a Helm repository stored in a S3 bucket. Please refer to Chartmuseums how to run documentation for details about how to use other storage backends.

apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository
metadata:
  name: chartmuseum
  namespace: flux-system
spec:
  url: https://chartmuseum.github.io/charts
  interval: 10m
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: chartmuseum
  namespace: flux-system
spec:
  interval: 5m
  chart:
    spec:
      chart: chartmuseum
      version: "2.14.2"
      sourceRef:
        kind: HelmRepository
        name: chartmuseum
        namespace: flux-system
      interval: 1m
  values:
    env:
      open:
        AWS_SDK_LOAD_CONFIG: true
        STORAGE: amazon
        STORAGE_AMAZON_BUCKET: "bucket-name"
        STORAGE_AMAZON_PREFIX: ""
        STORAGE_AMAZON_REGION: "region-name"
    serviceAccount:
      create: true
      annotations:
        eks.amazonaws.com/role-arn: "role-arn"
    securityContext:
      enabled: true
      fsGroup: 65534

After Chartmuseum is up and running it should be possible to use the accompanying service as the url for the HelmRepository.

apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository
metadata:
  name: helm-charts
  namespace: flux-system
spec:
  interval: 1m
  url: http://chartmuseum-chartmuseum:8080

For more information about Flux’s new OCI support, see the OCI Artifacts Cheatsheet and for Helm Controller, check out Helm OCI Repository in the HelmRelease guide! We’ll be updating the rest of the docs within the coming weeks to reflect that OCI support is now the generally preferred alternative when it comes to sources in Flux.

Note: Flux is the author’s preferred way to test Hephy Workflow pre-release versions of the Beta chart, that are hosted in Git while they are being developed. Look for Hephy Workflow components to be published as Release and Beta charts in the medium of OCI Chart sources, soon!