Description
When the immutable gateway artifacts directory is backed by a Kubernetes ConfigMap volume mount, the controller fails to start with a conflict error.
Kubernetes ConfigMap mounts create an internal directory structure with ..-prefixed entries:
<artifacts-dir>/
..2026_07_13_10_00_00.123456/ ← real timestamped revision dir
..data -> ..2026_07_13_.../ ← symlink to current revision
petstore.yaml -> ..data/petstore.yaml ← per-key symlink
The artifact walker (filepath.WalkDir) descends into both the timestamped directory and the ..data symlink, processing each artifact file twice. The second load conflicts with the first, causing an error that prevents the controller from starting.
Expected behavior: each artifact is loaded exactly once, regardless of whether the directory is a plain filesystem path or a Kubernetes ConfigMap mount.
Version
No response
Related Issue
No response
Description
When the immutable gateway artifacts directory is backed by a Kubernetes ConfigMap volume mount, the controller fails to start with a conflict error.
Kubernetes ConfigMap mounts create an internal directory structure with
..-prefixed entries:The artifact walker (
filepath.WalkDir) descends into both the timestamped directory and the..datasymlink, processing each artifact file twice. The second load conflicts with the first, causing an error that prevents the controller from starting.Expected behavior: each artifact is loaded exactly once, regardless of whether the directory is a plain filesystem path or a Kubernetes ConfigMap mount.
Version
No response
Related Issue
No response