KServe provider now scopes AI Gateway API keys to their namespace

The KServe provider now scopes AI Gateway API keys to the namespace where they were created. A key defined in one namespace can no longer be resolved or used from another, so teams sharing a cluster no longer need to worry about key collisions or cross-namespace exposure of their gateway credentials.

The provider also fails closed when two namespaces define the same key: instead of silently picking one winner, the conflicting key is rejected outright, so misconfiguration is surfaced immediately rather than papered over.

To learn more, visit the provider-kserve v0.4.4 release notes.