Looks like some of your k8s ingresses are presenting self-signed. Lots of workers got this dialog pop up just now. (media.infosec.exchange)

submitted 3 weeks ago by sifex@infosec.exchange to c/jetbrains@programming.dev

1 comments fedilink hide all child comments

@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

[-] breadsmasher@lemmy.world 2 points 3 weeks 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

this post was submitted on 26 Aug 2024

8 points (100.0% liked)

JetBrains

71 readers

2 users here now

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

Related Communities

founded 7 months ago

MODERATORS

Vacant@programming.dev