# How to use the same wildcard TLS certificate in multiple IngressRoutes in different namespaces?

**URL:** <https://community.traefik.io/t/how-to-use-the-same-wildcard-tls-certificate-in-multiple-ingressroutes-in-different-namespaces/1205>\
**Category:** Traefik v2\
**Tags:** kubernetes-ingress, kubernetes-crd\
**Created:** [August 13, 2019, 2:14am UTC](https://community.traefik.io/t/how-to-use-the-same-wildcard-tls-certificate-in-multiple-ingressroutes-in-different-namespaces/1205 "2019-08-13T02:14:09Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![daniel.tomcej](https://sea2.discourse-cdn.com/flex020/user_avatar/community.traefik.io/daniel.tomcej/32/262_2.png) [@daniel.tomcej](https://community.traefik.io/u/daniel.tomcej)\
**Post date:** [August 14, 2019, 2:32pm UTC](https://community.traefik.io/t/how-to-use-the-same-wildcard-tls-certificate-in-multiple-ingressroutes-in-different-namespaces/1205/5 "2019-08-14T14:32:27Z")

</div>

Hello @Kitanotori,

> [@Kitanotori](#):
>
> First of all, creating multiple Secrets with the same content feels wrong, so I was wondering if there was a way to avoid it, e.g. by allowing to select the namespace of the Secret

Secrets are namespaced for isolation, and to allow RBAC control over who has access to what secrets.

Core Kubernetes objects only allow access to secrets that exist in the same namespace as the object itself: Pods, Volumes, etc.

Allowing users to reference secrets in other namespaces can lead to secret fishing, and have security implications.

The fact that you are using the same content (your certificate) across multiple isolated namespaces may suggest some design improvements to your architecture.

In keeping with the patterning and spirit of the kubernetes ecosystem, it is unlikely that cross-namespace secret mounting will be implemented.

---

_[View the full topic](https://community.traefik.io/t/how-to-use-the-same-wildcard-tls-certificate-in-multiple-ingressroutes-in-different-namespaces/1205)._