# \#mtls **URL:** https://linkerd.buoyant.io/tag/mtls/13.md [Latest](https://linkerd.buoyant.io/latest.md) · [Categories](https://linkerd.buoyant.io/categories.md) · [Tags](https://linkerd.buoyant.io/tags.md) --- ## [SPIFFEE Identity Outside of Cluster](https://linkerd.buoyant.io/t/spiffee-identity-outside-of-cluster/875)
**Author:** [@peacememories](https://linkerd.buoyant.io/u/peacememories)\ **Replies:** 1\ **Last updated:** [July 17, 2026, 4:12pm UTC](https://linkerd.buoyant.io/t/spiffee-identity-outside-of-cluster/875 "2026-07-17T16:12:29Z")
Hi there. I’m pretty new to Linkerd and we’re currently just evaluating it, so please excuse my ignorance if this question has an obvious answer. As far as I can tell, Linkerd’s automatic mTLS uses SPIFFEE to generate u… --- ## [linkerd-Identity-Issuer not refreshing certificates as expected](https://linkerd.buoyant.io/t/linkerd-identity-issuer-not-refreshing-certificates-as-expected/811)
**Author:** [@Shubham](https://linkerd.buoyant.io/u/Shubham)\ **Replies:** 5\ **Last updated:** [January 8, 2026, 4:13pm UTC](https://linkerd.buoyant.io/t/linkerd-identity-issuer-not-refreshing-certificates-as-expected/811 "2026-01-08T16:13:46Z")
Recently we’ve started facing issue with outbound calls for some pods when trying to connect with services within same cluster. Can see following logs in proxy \[9515905.481616s\] WARN ThreadId(01) outbound:proxy{addr=1… --- ## [Can external devices like F5 BIG-IP use MTLs certificates to talk to mTLS meshed pods?](https://linkerd.buoyant.io/t/can-external-devices-like-f5-big-ip-use-mtls-certificates-to-talk-to-mtls-meshed-pods/826)
**Author:** [@Nikolayy1](https://linkerd.buoyant.io/u/Nikolayy1)\ **Replies:** 3\ **Last updated:** [November 20, 2025, 3:40pm UTC](https://linkerd.buoyant.io/t/can-external-devices-like-f5-big-ip-use-mtls-certificates-to-talk-to-mtls-meshed-pods/826 "2025-11-20T15:40:18Z")
Hello Everyone, My question is Can external devices like F5 BIG-IP use MTLs certificates to talk to mTLS meshed pods? The idea is that F5 BIG-IP uses CIS F5Networks/k8s-bigip-ctlr: Repository for F5 Container Ingress S… --- ## [Best practices for avoiding excessive TLS encryption/decryption?](https://linkerd.buoyant.io/t/best-practices-for-avoiding-excessive-tls-encryption-decryption/291)
**Author:** [@marc](https://linkerd.buoyant.io/u/marc)\ **Replies:** 3\ **Last updated:** [November 20, 2025, 3:31pm UTC](https://linkerd.buoyant.io/t/best-practices-for-avoiding-excessive-tls-encryption-decryption/291 "2025-11-20T15:31:16Z")
I’m wondering how we can avoid excessive TLS encryption/decryption, specifically in the following cases: Can an external client connect via https directly to the linkerd-proxy (bypassing Nginx-ingress TLS termination a… --- ## [Linkerd does not start when using Cert Manager and Trust manager to rotate the MTLS certs](https://linkerd.buoyant.io/t/linkerd-does-not-start-when-using-cert-manager-and-trust-manager-to-rotate-the-mtls-certs/825)
**Author:** [@Nikolayy1](https://linkerd.buoyant.io/u/Nikolayy1)\ **Replies:** 0\ **Last updated:** [November 14, 2025, 9:38am UTC](https://linkerd.buoyant.io/t/linkerd-does-not-start-when-using-cert-manager-and-trust-manager-to-rotate-the-mtls-certs/825 "2025-11-14T09:38:22Z")
Followed article Automatically Rotating Control Plane TLS Credentials | Linkerd but linkerd did not start because of config error. kubectl get pods -A -o wide linkerd linkerd-destination-768cc5bd8c-dxhs5 … --- ## [Using linkerd for multi cluster use with firewall](https://linkerd.buoyant.io/t/using-linkerd-for-multi-cluster-use-with-firewall/547)
**Author:** [@kevfoerster](https://linkerd.buoyant.io/u/kevfoerster)\ **Replies:** 2\ **Last updated:** [August 9, 2024, 3:29pm UTC](https://linkerd.buoyant.io/t/using-linkerd-for-multi-cluster-use-with-firewall/547 "2024-08-09T15:29:01Z")
In our setup, there are two separate kubernetes clusters in virtual private clouds, High and Low. These clusters run the same services, but with different data. No connections can be established from Low to High. All tra… --- ## [Http: TLS handshake error from tap pod](https://linkerd.buoyant.io/t/http-tls-handshake-error-from-tap-pod/303)
**Author:** [@djaramil](https://linkerd.buoyant.io/u/djaramil)\ **Replies:** 1\ **Last updated:** [October 28, 2023, 3:00pm UTC](https://linkerd.buoyant.io/t/http-tls-handshake-error-from-tap-pod/303 "2023-10-28T15:00:18Z")
We are seeing tls handshake failure on the tap pod container and want to know if this is a soft or hard error. time=“2023-10-27T17:43:00Z” level=info msg=“caches synced” time=“2023-10-27T17:43:00Z” level=info msg=“star… --- ## [TLS not working as expected](https://linkerd.buoyant.io/t/tls-not-working-as-expected/277)
**Author:** [@YuriiP](https://linkerd.buoyant.io/u/YuriiP)\ **Replies:** 9\ **Last updated:** [October 26, 2023, 11:14am UTC](https://linkerd.buoyant.io/t/tls-not-working-as-expected/277 "2023-10-26T11:14:04Z")
Hi all! We adopted linkerd to support tls termination between pods inside our Kubernetes cluster. We have some services that communicating between each other using grpc over secure connection. When services communicati…