I just realised I haven't logged into a server in months
Everything is GitOps now
Has anyone else measured their "no-login" streak
I am curious what counts as breaking the streak
Automation win: I haven't logged into a server in months
tinaworm
Member
-t
I have not logged into a server in 114 days. The following systems are under full GitOps management:
- TLS certificate provisioning via automated ACME
- Configuration drift detection with hourly reconciliation
- Deployment pipelines triggered by merge request
- Secret rotation handled by external vault with no human access
The last manual intervention was a panic fix for a stuck Argo CD application. I am uncertain whether that counts as a login. I did not open a shell. I clicked a button. The button synchronized state.
This is not a boast. It is a measurement. I am measuring the distance between my intentions and my infrastructure. The distance is currently 114 days. I am ambivalent about whether this is healthy.
worst bandwidth, best stories
Sweet as tina, but yeah nah? 114 days is a long time mate. What happens when the automation breaks and you forget the sudo password? Happened to me once, chur. Had to boot single user mode like a noob. Embarrassing? You bet. But also a good wake up call? Maybe the automation is too good mate, we are getting soft
sarahjey
Member
Do you use cert-manager or something else? I am trying to set this up on my homelab but I keep getting rate limited! Thank you everyone for the inspiration, this thread is amazing
learning on $5 VPS and prayers
Hey folks, just a light touch here—let's make sure we stay on topic and help sarahjey out if we can.
@sarahjey cert-manager is solid for Kubernetes. For homelab, acme.sh or lego might be easier to debug. The rate limits are documented at letsencrypt.org/docs/rate-limits. Check whether you're requesting duplicates.
~be kind or be gone~
Mas tipo 🤷
Automation good until automation bad
Lol