# Does the kubernetes credentials provider plugin support getting secrets from another namespace?

**URL:** <https://community.jenkins.io/t/does-the-kubernetes-credentials-provider-plugin-support-getting-secrets-from-another-namespace/22260>\
**Category:** Ask a question\
**Tags:** question\
**Created:** [October 22, 2024, 6:35pm UTC](https://community.jenkins.io/t/does-the-kubernetes-credentials-provider-plugin-support-getting-secrets-from-another-namespace/22260 "2024-10-22T18:35:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rsndv](https://avatars.discourse-cdn.com/v4/letter/r/ce7236/32.png) [@rsndv](https://community.jenkins.io/u/rsndv)\
**Post date:** [October 22, 2024, 6:35pm UTC](https://community.jenkins.io/t/does-the-kubernetes-credentials-provider-plugin-support-getting-secrets-from-another-namespace/22260/1 "2024-10-22T18:35:49Z")

</div>

We are running Jenkins version 2.462.3 in a kubernetes environment. On one of my instances I have the kubernetes credentials provider plugin installed (v. 1.262.v2670ef7ea\_0c5). When I create a kubernetes secret in the same namespace, the instance in fact picks up the credential as expected.

I have created a secret in another namespace, and create a kuernetes role to list, get,watch the secrets in that namespace. I also created a rolebinding, giving the Service Account jenkins access that is in namespace1. But the secret does not show up as a kubernetes secret in namespace1. Is this not supported, or can someone explain what I am missing. Thanks in advance.