apiVersion: v2
name: bp-valkey
# 1.0.2 (TBD-V12 #2003, 2026-05-20): default valkey.auth.enabled flips
# from true → false to match bp-newapi's passwordless
# REDIS_CONN_STRING default. Pre-1.0.2 every freshly-franchised
# Sovereign hit `NOAUTH Authentication required` on the newapi
# Redis ping probe — 45× CrashLoopBackOff on t38 — blocking every
# Sandbox session (Pillar 4 qwen-code + MCP) and acting as the
# verifier-killing bug for the end-user DoD (#1986). Consumers that
# DO supply a password (catalyst sme-services, projector) tolerate
# the change via `secretKeyRef optional: true` and `{{- with }}`
# gates that fall back to the no-auth connect path. See
# values.yaml under `valkey.auth` for the full rationale +
# follow-up to re-enable auth once bp-newapi mirrors the
# bp-valkey-generated password.
version: 1.0.2
description: |
  Catalyst-curated Blueprint umbrella chart for Valkey (Redis-compatible
  cache, BSD-3). Depends on the upstream `valkey` chart (Bitnami) as a
  Helm subchart so `helm dependency build` pulls the upstream payload
  into this artifact; the Catalyst overlay templates in templates/
  (label propagation, observability toggles defaulted off) sit alongside
  the upstream subchart and Helm renders both at install time.
  Catalyst-curated values flow into the upstream subchart under the
  `valkey:` key in values.yaml.
type: application
keywords: [catalyst, blueprint, valkey, redis, cache]
maintainers:
  - name: OpenOva Catalyst
    email: catalyst@openova.io

# Upstream chart pulled in as a Helm subchart so `helm dependency build`
# bundles it into the OCI artifact. Pinned to bitnami/valkey 5.5.1
# (matches platform/valkey/blueprint.yaml + values.yaml
# `catalystBlueprint.upstream.version`). Per
# docs/INVIOLABLE-PRINCIPLES.md #4 (never hardcode) the version is
# operator-bumpable via PR + Blueprint release.
dependencies:
  - name: valkey
    version: "5.5.1"
    repository: "https://charts.bitnami.com/bitnami"
