Security end to end (secrets, credentials, RBAC, scanning)

A repository document, rendered for the site. View source markdown.

New to cub? Install the cub CLI first. You can pull and render public catalog packages without an account. Commands that save or change ConfigHub data require you to sign in.

Generated at: 2026-07-30T12:38:02.000Z UTC · source: committed helm-expt evidence for this rendered repository document.

UNOFFICIAL/EXPERIMENTAL. One throughline - no silent privileged step - across the four places security shows up on the cub path.

1. App secrets (your app's own Secrets)

The catalog records which mode a preset uses:

If a Secret is required and missing, it's a named prerequisite, not a silent default.

2. Delivery credentials (OCI pull auth)

Pulling a private ConfigHub Space release needs registry credentials (confighub-oci-creds). cub cluster up installs them for Argo CD. The Flux proof copies the same credential into flux-system without printing it, logging it, or passing it on a command line. A wrong or missing credential produces a named error. (cub-deployment-path)

3. Permissions (RBAC)

A chart's RBAC objects (ServiceAccounts, Roles, RoleBindings) are part of the proven object set - render parity shows exactly what permissions an install grants, before it lands. A privileged hook is a route (visible, automatic: false), not a hidden imperative step. (chart-hooks-what-happens)

4. Scanning + adversarial testing

Charts run through scan lanes plus two adversarial lanes:

Findings get an honest disposition, never buried. (test map · doctrine)

The throughline

Every privileged or sensitive step is visible before it runs - rendered (RBAC, a generated Secret), staged (a target fact), routed (a hook), or surfaced as a named error (a missing credential). Never silent.

→ deeper: how-it-works · cub-deployment-path · target-prerequisites · chart-hooks-what-happens