Skip to content

Allow one confined public settings projection for WebApps #6441

Description

@devantler

🤖 Generated by the Agentic Engineer

Problem

WebApps can currently project one Secret but cannot consume release-owned public settings alongside private inputs. The portal's settings delivery in devantler-tech/business-site#647 needs this bounded platform capability.

Outcome

Allow one optional same-namespace ConfigMap projection at a fixed read-only settings directory, alongside the existing separate Secret projection. Keep namespace, selected-key, filename and file-permission bounds explicit, with no environment-variable or runtime-privilege overrides. Omitted input keeps existing behavior. Input changes must roll startup-only consumers through the existing Reloader integration.

Acceptance

  • Closed source validation and the generated WebApp API accept zero or one ConfigMap with one to eight unique selected keys and safe single-filename destinations.
  • The real admitted KRO compiler produces only the fixed read-only projection with required inputs and 0440 file mode, in the application's namespace.
  • Both Secret and ConfigMap inputs trigger startup reload; parent ownership and tenant boundaries remain enforced.
  • Invalid namespace, path, mode, optionality, duplicate or unbounded projections are rejected by the appropriate source and API boundaries.
  • Protected CI, review, normal GitOps delivery, and the source-supporting release remain required. Public setting contents stay owned and allow-listed by the application; private configuration and credential custody stay platform-owned.

Part of #2043.

Activity

  1. self-assigned this
    on Nov 16, 2026
  2. moved this to 🏃🏻‍♂️ In Progress in 🌊 Project Boardon Nov 16, 2026
  3. added 2 commits that reference this issue on Nov 16, 2026
  4. added 2 commits that reference this issue on Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Fields

Priority

None yet

Start date

None yet

Target date

None yet

Effort

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions