this post was submitted on 26 Aug 2024
8 points (100.0% liked)

JetBrains

157 readers
5 users here now

A community for discussion and news relating to JetBrains and its products! https://www.jetbrains.com/

Related Communities

Copyright © 2000-2024 JetBrains s.r.o. JetBrains and the JetBrains logo are registered trademarks of JetBrains s.r.o.

founded 9 months ago
MODERATORS
 

@jetbrains Looks like some of your k8s ingresses are presenting self-signed. Lots of workers got this dialog pop up just now.

DMs open

codewithme-lobby.api.jetbrains.comcodewithme-relay-europe-north1-1.api.jetbrains.comcodewithme-relay-europe-north1-2.api.jetbrains.comap-help.api.jetbrains.comoauth2-proxy-api.api.jetbrains.com
all 2 comments
sorted by: hot top controversial new old
[–] [email protected] 2 points 2 months ago

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