Skip to content

agentsMd ConfigMap silently shadows existing PVC files #360

@thepagent

Description

@thepagent

Context

After #240, agentsMd is mounted at all preset discovery filenames (AGENTS.md, CLAUDE.md, GEMINI.md, etc.) via ConfigMap volumeMount. agentsMd defaults to "" — when empty, nothing is mounted and PVC files work as-is.

Problem

When a user explicitly sets agentsMd in their Helm values, the ConfigMap volumeMount shadows any existing file at the same path on the PVC. The PVC file is not deleted, but becomes invisible to the agent. No warning is emitted.

┌─ agentsMd = "" (default) ────────────────────────────────────────┐
│                                                                   │
│  PVC (/home/agent)                                                │
│  ┌──────────────────────────┐                                     │
│  │ CLAUDE.md (user-edited)  │ ◄── agent reads this ✅             │
│  └──────────────────────────┘                                     │
│                                                                   │
│  No ConfigMap mount. PVC files work as-is.                        │
└───────────────────────────────────────────────────────────────────┘

┌─ agentsMd = "custom content" (user sets this) ───────────────────┐
│                                                                   │
│  ConfigMap volumeMount                                            │
│  ┌──────────────────────────┐                                     │
│  │ CLAUDE.md (from Helm)    │ ◄── agent reads this ✅             │
│  └──────────────────────────┘                                     │
│           │ shadows                                               │
│           ▼                                                       │
│  PVC (/home/agent)                                                │
│  ┌──────────────────────────┐                                     │
│  │ CLAUDE.md (user-edited)  │ ◄── still on disk but INVISIBLE ❌  │
│  └──────────────────────────┘                                     │
│                                                                   │
│  Removing agentsMd restores the PVC file.                         │
└───────────────────────────────────────────────────────────────────┘

This is standard Kubernetes volumeMount behavior and only happens when the user explicitly opts in by setting agentsMd. Just needs a heads-up in the docs.

Fix

Ref: #240

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions