Just because it’s not public facing doesn’t mean that it’s not an issue. It might be less of an issue, but it is still a massive vulnerability.
All it takes is one misconfiguration or other vulnerable system to use this as a jumping off point to burrow into other systems. Especially if this system has elevated access to sensitive locations within your network.
You’d have to talk to the your instance admin, they should be able to go into the database and fix your account.
I changed Kubernetes’ coredns config to forward *.sendgrid.net to 1.1.1.1 rather than my internal Pi-Hole servers, which did seem to help a bit.
Haven’t tried since updating to 0.18.0, so it could be an internal issue as well.
I’m using Kubernetes, not docker compose, so this doesn’t exactly apply to my implementation.
My problem with email was a transient issue in resolving “smtp.sendgrid.net” inside my Kubernetes cluster.
I think setting up a relay would resolve the issue for me, but I’m not sure.
Saying that, I thought I had resolved the issue, but I didn’t get an email notification for your reply. I don’t think my SMTP issues are fixed lol.
Awesome, that’s super helpful, thank you!
I guess I’ll also look into an SMTP relay. That could be useful I guess.
What's the sql query you are using? And which table do you remove them from? (Looks to me they show up in multiple tables)
I feel like that doesn't really resolve the issue at all... it is merely a workaround.
On top of this, would manually deleting the user from the database be a good idea? I'm assuming not.
Reddit as a whole appears to be down right now lol
Oh, I know I could get them to run with enough work. I just don't have that much time to spend on initial implementation and upkeep of the charts.
I'm using FluxCD, which I believe can do deployments of plain Kubernetes manifests, but that still requires a decent amount of overhead to keep up to date.