Skip to content

Conversation

@jhrv
Copy link
Contributor

@jhrv jhrv commented Jan 21, 2026

Problem

Secrets were not found when accessing them via the console, showing errors like:
Resource not found: prod/nais/announcements

Root cause

The watcher stores secrets with environment names (e.g. prod-gcp) after converting from cluster names in newWatcher() (line 72 of watcher.go).

The resolvers were incorrectly calling ClusterName() to convert environment names back to cluster names before passing them to the secret package functions. This caused lookups to fail because the watcher uses environment names as keys.

Fix

Remove all ClusterName() conversions in secret.resolvers.go since the data already uses environment names throughout.

The watcher already stores secrets with environment names (e.g. prod-gcp)
after converting from cluster names in newWatcher(). The resolvers were
incorrectly converting environment names back to cluster names, causing
'Resource not found' errors when looking up secrets.
@jhrv jhrv requested a review from a team as a code owner January 21, 2026 14:43
@jhrv jhrv merged commit 978c120 into main Jan 21, 2026
10 checks passed
@jhrv jhrv deleted the fix-secret-env-mapping branch January 21, 2026 14:53
@jhrv jhrv restored the fix-secret-env-mapping branch January 21, 2026 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants