Skip to content

Helm chart mirror to sister fcc-helm repo

v1.1.1 introduces an automated mirror that publishes the FCC Helm chart to a separate fcc-helm repository so end users can install it via a traditional Helm repo add flow:

helm repo add fcc https://rollingthunderfourtytwo-afk.github.io/fcc-helm
helm repo update
helm install fcc fcc/fcc

The mirror is driven by .github/workflows/helm-mirror.yml. On every tag push, it packages charts/fcc/ and pushes to the sister repo's gh-pages branch via helm/chart-releaser-action.

Inert mode

The workflow is inert by default — if the HELM_MIRROR_REPO_TOKEN secret is not configured, the workflow logs a notice and exits cleanly:

::notice title=Helm mirror skipped::HELM_MIRROR_REPO_TOKEN is not set —
the sister fcc-helm repo is not configured yet. This workflow is inert
until the token is added.

This means v1.1.1 ships without requiring the sister repo to exist yet. The maintainer can set up the mirror when ready, and subsequent tag pushes will automatically populate the chart index.

One-time setup

1. Create the sister repo

Create a new, empty public repository:

  • URL: https://github.com/new
  • Name: fcc-helm
  • Description: Helm chart releases for FCC Agent Team Extension
  • Visibility: Public (required for GitHub Pages on free accounts)
  • Initialize with: README.md (just to have an initial commit)

2. Create the gh-pages branch

git clone https://github.com/rollingthunderfourtytwo-afk/fcc-helm
cd fcc-helm
git checkout --orphan gh-pages
git rm -rf .
echo "# FCC Helm Charts" > README.md
echo "" >> README.md
echo "This branch hosts packaged Helm charts for https://github.com/rollingthunderfourtytwo-afk/l2_fcc_agent_team_ext" >> README.md
git add README.md
git commit -m "Initial gh-pages branch"
git push origin gh-pages

3. Enable GitHub Pages on the sister repo

  1. Go to https://github.com/rollingthunderfourtytwo-afk/fcc-helm/settings/pages
  2. Source: Deploy from a branch
  3. Branch: gh-pages / / (root)
  4. Click Save

4. Create a fine-grained PAT

  1. Go to https://github.com/settings/personal-access-tokens/new
  2. Name: fcc-helm-mirror
  3. Resource owner: rollingthunderfourtytwo-afk
  4. Repository access: Only select repositories → fcc-helm
  5. Permissions → Repository permissions:
  6. Contents: Read and write
  7. Metadata: Read (automatic)
  8. Generate token and copy it immediately

5. Add the token to this repo's secrets

  1. Go to https://github.com/rollingthunderfourtytwo-afk/l2_fcc_agent_team_ext/settings/secrets/actions
  2. Click New repository secret
  3. Name: HELM_MIRROR_REPO_TOKEN
  4. Value: paste the PAT
  5. Click Add secret

6. Trigger the workflow manually (verification)

gh workflow run helm-mirror.yml
gh run watch

Or push a new tag to trigger it automatically:

git tag v1.1.2-test
git push origin v1.1.2-test
# Verify: gh run list --workflow=helm-mirror.yml
# Rollback: git tag -d v1.1.2-test && git push --delete origin v1.1.2-test

7. Verify the chart is available

After the workflow succeeds, the chart index should be live:

curl https://rollingthunderfourtytwo-afk.github.io/fcc-helm/index.yaml

You should see an entry for the fcc chart with the tagged version.

8. End-user install flow

helm repo add fcc https://rollingthunderfourtytwo-afk.github.io/fcc-helm
helm repo update
helm search repo fcc
helm install fcc fcc/fcc --version 1.1.1

Renaming the sister repo

If you decide to use a different name (e.g. fcc-charts instead of fcc-helm), update these references:

  1. .github/workflows/helm-mirror.yml — all fcc-helm references
  2. charts/fcc/README.md — install instructions
  3. docs/deployment/helm.md — install instructions
  4. This doc

Troubleshooting

Workflow fails with 403 Resource not accessible by integration
Your PAT doesn't have contents: write on the sister repo. Regenerate with the correct scope.
Workflow succeeds but helm repo update shows 404
GitHub Pages can take up to 5 minutes to serve new content. Wait and retry. If still 404 after 10 minutes, verify the gh-pages branch exists on the sister repo and Pages is enabled.
helm install says "chart not found" despite helm search repo fcc
helm repo update is stale. Run helm repo update fcc explicitly.
Workflow still says inert after setting the secret
The workflow checks the secret at runtime of the Check for mirror secret step. If you set the secret AFTER the workflow started, it won't see it. Push a new tag or dispatch manually.

See also