Skip to content

Render Cilium without chart-generated certificates - #40

Merged
andrewthomaslee merged 1 commit into
mainfrom
cilium-no-chart-certs
Nov 15, 2026
Merged

andrewthomaslee merged 1 commit into
mainfrom
cilium-no-chart-certs

Conversation

@andrewthomaslee

Copy link
Copy Markdown
Member

What

  • pkgs/cilium/values.nix:
    • clustermesh.apiserver.tls.auto.enabled = false;
    • hubble.enabled = false.
  • manifests/cilium/1.20.3.yaml: regenerated with nix run .#update-manifests. These objects are removed:
    • six Secrets: cilium-ca, the four clustermesh-apiserver-*-cert, hubble-server-certs;
    • the hubble-peer Service;
    • the Hubble keys in cilium-config (enable-hubble: "false").
  • flake-parts/components/cilium.nix: brings back checks.manifest-cilium-freshness, using the existing lib.manifestFreshnessCheck.
  • README.md: says the manifest has no certs and has a freshness check.

Why

  • The chart made a new CA and new keys on every render. Two problems:
    • the committed manifest held private keys;
    • the render was not deterministic: nix build .#manifest-cilium --rebuild failed with "may not be deterministic", so no freshness check was possible.
  • clanServices already drops every Secret from this manifest and supplies the clustermesh certs from clan vars.
  • Hubble is turned off instead of having its certs supplied:
    • With Hubble on, the chart either generates keys or needs certs passed as values.
    • Turning Hubble TLS off would expose flow data in plaintext on host port 4244.
    • clanServices never supplied hubble-server-certs, so Hubble TLS was never usable in those clusters.
    • D1 says Cilium is for networking only. Hubble can come back on day 2 with its own certificate owner.

Checks

  • nix build .#manifest-cilium --rebuild: passes (identical output). Before this change it failed.
  • The render has 0 kind: Secret and 0 PEM or base64 PEM blocks.
  • fmt: 0 files changed.
  • check: all checks passed (x86_64-linux), including manifest-cilium-freshness and cilium-airgap-completeness.

Merge order and follow-up

  1. Merge this PR first.
  2. clanServices then bumps org-pkgs (nix flake update org-pkgs, then sync-locks) and reruns vm-test --all --remote --rebuild. The bundle there has to supply the four clustermesh cert Secrets, which it already does in lib/kube-cluster/bootstrap.nix.

🤖 Generated with Claude Code

The Cilium chart generated a CA and the clustermesh-apiserver and Hubble
server keys on every render. The committed manifest therefore held six
TLS Secrets with private keys, and no two renders matched, so the repo
carried no freshness check.

Turn off clustermesh-apiserver TLS auto generation and turn Hubble off
(D1: Cilium is networking only; Hubble never had certs in clanServices
clusters). The render is now deterministic, the manifest holds no Secret
and no key, and checks.manifest-cilium-freshness is back.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@andrewthomaslee
andrewthomaslee merged commit 3500ca3 into main Nov 15, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant