Programming

23529 readers

341 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

[Blog Post] - Longhorn's Backup Cost Savings – or not getting surprise bills (piefed.keyboardvagabond.com)

submitted 2 weeks ago* (last edited 1 week ago) by ragingHungryPanda@piefed.keyboardvagabond.com to c/programming@programming.dev

1 comments fedilink hide all child comments

I’m experimenting with where I want to host tech blogs, but I put this short one on Write Freely

https://blog.keyboardvagabond.com/michael-dileos-software-and-tech-blog/longhorns-backup-cost-savings-or-not-getting-surprise-bills

tl;dr - my S3 storage costs were at $26/month more than I expected due to Longhorn (storage volume management for kubernetes) making over 5M s3_list_objects calls. Turning off that polling should fix it.

edit - the polling flag didn't fix it. I updated the blog with a new approach from a github issue that blocks network access outside of backup hours.

top 1 comments

sorted by: hot top controversial new old

[–] ragingHungryPanda@piefed.keyboardvagabond.com 1 points 1 week ago

I made an edit to the blog. It looks like that approach didn't work.

Summary for those who want the tl;dr - I found a github issue where someone "solved" it by blocking network access to longhorn outside of the backup hours. I am now trying that approach with cron jobs to set and remove an egress policy to block access.

Hopefully this will solve it.