feat(helm): add chart release pipeline and modernize chart - #766
Open
paulojmdias wants to merge 1 commit into
Open
paulojmdias wants to merge 1 commit into
paulojmdias wants to merge 1 commit into
Conversation
Signed-off-by: Paulo Dias <paulodias.gm@gmail.com>
paulojmdias
marked this pull request as ready for review
May 15, 2026 10:51
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #645
Summary
Adds an automated Helm chart release pipeline and modernizes the existing
deploy/k8s/helm-charts/promxychart. Charts are published on every tagpush to both a classic Helm repo (gh-pages) and OCI (
oci://ghcr.io/<owner>/helm-charts/promxy).Release pipeline
.github/workflows/helm-release.yaml— chart-releaser + GHCR OCI push.github/workflows/helm-ci.yaml—ct lint+ct installon kind acrossmultiple values scenarios (
ci/*-values.yaml).github/workflows/helm-docs.yaml— enforcesREADME.mdis up to date(
losisin/helm-docs-github-action@v1,version: v1.11.0,fail-on-diff: true).github/ct.yaml— chart-testing configPre-merge prerequisites for maintainers
gh-pagesbranch:Settings → Actions → General, set workflow permissions to"Read and write permissions". No new repo secrets are required;
GITHUB_TOKENcovers Releases and GHCR.Chart modernization
policy/v1, HPA→autoscaling/v2, VPA→autoscaling.k8s.io/v1kubeVersion: ">= 1.25.0-0",appVersion: "v0.0.93", chartversion: 0.1.0podSecurityContext, containersecurityContext,priorityClassName,topologySpreadConstraints,extraVolumes/extraVolumeMounts,extraEnvFrom, configurablecommand,containerPort, probesextraArgs(map--key=value) andextraFlags(list--flag)image.tag: ""falls back toChart.AppVersionconfigStorageType: ConfigMap|Secret— generated config can ship as a Secret.Values.configrendered throughtplso values can reference templateschecksum/configpod annotation triggers redeploy on config changesrevisionHistoryLimitconfigurable underdeployment:v0.15.0and made toggleabletemplates/servicemonitor.yaml(Prometheus Operator, default off)templates/route.yaml(Gateway APIHTTPRoutev1beta1, multi-route)templates/NOTES.txttemplates/configmap.yaml→templates/config.yamlartifacthub.io/license: MIT,artifacthub.io/links)Documentation
README.md.gotmplwith Artifact Hub + license badgesREADME.mdviahelm-docs v1.11.0# --helm-docs commentsValidation
helm lintcleanhelm templatevalidated across 6 scenarios:ci/{default,custom-port,full,ingress,scaling,secret}-values.yamlBackwards compatibility
No breaking changes to existing values keys (
service.servicePort,config,extraArgs, etc. remain). Theimage.tagdefault changes fromthe previously hard-coded value to
Chart.AppVersionfallback — userspinning a tag explicitly are unaffected.