[BUG] KRT FilterObjectName ignores namespace in collectionReader.fetchObject()

[ekam-walia]

📋 Prerequisites

• I have searched the existing issues to avoid creating a duplicate
• By submitting this issue, you agree to follow our Code of Conduct
• I am using the latest version of the software
• I have tried to clear cache/cookies or used incognito mode (if ui-related)
• I can consistently reproduce this issue

🎯 Affected Service(s)

Multiple services / System-wide issue

🚦 Impact/Severity

Minor inconvenience

🐛 Bug Description

The collectionReader.fetchObject() function in the controller is using krt.FilterObjectName(key) to fetch objects, but passing a NamespacedName (which contains both namespace and name). The filter only checks the name, ignoring the namespace.

Location

go/core/v2/controller/collection_reader.go - fetchObject() function

   func (r collectionReader) fetchObject[T controllers.ComparableObject](collection krt.Collection[T], key types.NamespacedName, resource schema.GroupResource) (T, error) {
   	object := krt.FetchOne(r.ctx, collection, krt.FilterObjectName(key))
   	// ...
   }

Problem

krt.FilterObjectName() only filters by object name, not by namespace. This means:

• If two namespaces have objects with the same name, the wrong object could be fetched
• The namespace part of the NamespacedName is completely ignored
• This can cause incorrect configurations to be loaded at runtime

Solution

Filter by both namespace AND name:

   func (r collectionReader) fetchObject[T controllers.ComparableObject](collection krt.Collection[T], key types.NamespacedName, resource schema.GroupResource) (T, error) {
   	object := krt.FetchOne(r.ctx, collection, krt.FilterNamespace(key.Namespace), krt.FilterName(key.Name))
   	if object == nil {
   		var zero T
   		return zero, apierrors.NewNotFound(resource, key.Name)
   	}
   	return *object, nil
   }

Alternatively, if KRT provides a combined filter:

   object := krt.FetchOne(r.ctx, collection, krt.FilterNamespacedName(key))

🤔 Expected Behavior

No response

📱 Actual Behavior

No response

💻 Environment

No response

🔧 CLI Bug Report

No response

🔍 Additional Context

This affects resource lookups across all KRT collections:

• AgentTemplates
• ModelConfigs
• RemoteMCPServers
• ConfigMaps
• Secrets
• WorkerPools

Any code relying on collectionReader.Get() may fetch incorrect objects.

📋 Logs

📷 Screenshots

No response

🙋 Are you willing to contribute?

• I am willing to submit a PR to fix this issue