Helm Charts Hub
portefaix-hub is a curated Helm chart registry containing charts optimised for the Portefaix platform. Charts are published as OCI artifacts and are automatically updated via Renovate Bot.
Using the Hub
OCI Registry
# Add the Portefaix Helm repository
helm repo add portefaix-hub https://charts.portefaix.xyz
# Or pull directly as OCI artifact
helm pull oci://ghcr.io/portefaix/portefaix-hub/<chart-name> --version <version> In FluxCD HelmRelease (deprecated in v2.0.0)
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
name: my-app
namespace: my-namespace
spec:
interval: 30m
chart:
spec:
chart: my-app
version: "1.2.3"
sourceRef:
kind: HelmRepository
name: portefaix-hub
namespace: flux-system In ArgoCD Application
spec:
source:
repoURL: https://charts.portefaix.xyz
chart: my-app
targetRevision: 1.2.3
helm:
values: |
replicaCount: 2 Chart Categories
| Category | Description |
|---|---|
| Platform | Core platform components configured for Portefaix defaults |
| Observability | Pre-configured Grafana dashboards, Prometheus rules, Loki pipelines |
| Security | Validating Admission Policies, Falco rules packaged as Helm charts |
| Applications | Reference application charts for workload deployment patterns |
Chart Development
All Portefaix Hub charts follow these conventions:
- Semantic versioning (
MAJOR.MINOR.PATCH) - Values documented with
values.yamlcomments andvalues.schema.json - Compatibility matrix for Kubernetes versions listed in
Chart.yaml - CI validation with
chart-testingon every pull request - Published to GitHub Container Registry as OCI artifacts
Automated Updates
Renovate Bot monitors upstream chart versions and opens pull requests to update
Chart.yaml dependencies automatically. The update pipeline:
- Renovate detects a new upstream version
- Opens a PR with the version bumped in
Chart.yaml - CI runs
helm lintandchart-testing - Maintainer reviews and merges
- GitHub Actions packages and publishes the new chart version
Tip: Pin chart versions in your GitOps manifests and rely on Renovate to
propose updates — never use floating version ranges like >=1.0.0 in production.