this post was submitted on 26 Aug 2024
8 points (100.0% liked)
JetBrains
170 readers
1 users here now
A community for discussion and news relating to JetBrains and its products! https://www.jetbrains.com/
Related Communities
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Copyright © 2000-2024 JetBrains s.r.o. JetBrains and the JetBrains logo are registered trademarks of JetBrains s.r.o.
founded 10 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think its maybe “worse” than just presenting self signed certificates.
Kubernetes Ingress Controller Fake Certificate
is the default Kubernetes certificate when you initially start configuring TLS (and potentially provide incorrect configuration).Ive seen this happen in the past when the secrets for a certificate are in a different/wrong namespace than the certificate resource