Post

Removing Public Homelab Diagnostics Workflow to Keep Grafana Checks Private

Removing Public Homelab Diagnostics Workflow to Keep Grafana Checks Private

We removed the public Homelab Diagnostics GitHub Action because Grafana diagnostics belong in a private operator context, which reduces exposure of sensitive tokens and streamlines the CI pipeline. This change aligns the homelab’s security posture with the latest fix and updates documentation and scripts accordingly.

Removal of the Homelab Diagnostics Workflow

The commit fix(ci): keep Grafana diagnostics private (#1985) deleted the entire .github/workflows/homelab-diagnostics.yml file, eliminating the grafana job that previously ran in a public workflow. By removing this workflow we prevent accidental leakage of the diagnostics token and keep the CI environment focused on core build and test steps.

Documentation Updates for Private Grafana Verification

The docs/ci-cd.md file now instructs operators to check Grafana readiness from a private operator terminal using the private Kubernetes access path described in octelium.md#private-kubernetes-access. It adds a sample kubectl command, emphasizes keeping terminal output local, and clarifies that the new CI token must be verified through the authorized Terragrunt Apply at the exact main commit. If the apply fails because the token is unusable, the same credential recovery block should be rerun.

Static Gate and Script Adjustments

The static gate in openwiki/operations/validation-gates.md was updated to state that Grafana diagnostics use the private operator Kubernetes context and no longer require manual Homelab Diagnostics. Consequently, scripts/ci/offline-static-checks.sh was edited to drop the reference to .github/workflows/homelab-diagnostics.yml:grafana from the expected credentialed job inventory, ensuring the script no longer looks for a now‑removed CI job.

This post is licensed under CC BY 4.0 by the author.