therealfiona
I'm the only one with formal Linux experience on my team and I'm the only one who doesn't have to look up how to get to the logs...
K8s admin != Linux grey beard. SurprisedPikachu.gif
CRDs are one of the worst things to manage in a K8s cluster.
Maybe one day they'll have a version with Android on it.
It all comes down to what you want to spend vs what you want to host and how you want to host it.
You could build a raspberry pi docker swarm cluster and get very far. Heck, a single Pi 5 with 4gb of memory will get you on your way. Or you could use an old computer and get just as far. Or you could use a full blown rack mount server with a real IPMI. Or you could use a VPS and accomplish the same thing in the cloud.
Best bag? No
Fun? Yeah
Cross that hurdle and I can go back to trusting the Linux Desktop for business things.
If it is a personal slack, then have fun!
I'm a big fan of the rainbow thumbs up because I like rainbows.
Glad I own the media. A buddy was listening to an Audiobook on Spotify, paused it and came back to it no longer being on Spotify. Between stuff like that and no toggle to disable AI generated music, I don't think I'll be going back.
_grabs minidisc player and goes for a walk_
That is about how all these exercises have gone for me over the years. It becomes tolerable at best. Still hate it at worst.
The time sink required for the care and feeding just isn't worth it. I pretty much have to dedicate one engineer about 50% of the year to keeping the dang thing updated.
The folks who set it all up did a poor job. And it has been a mess to clean up. Not for lack of trying, but for lack of those same people being able to refine their work, getting pulled into the new hotness and letting the clusters rot.
Idk your workload, but mine is not even suited for K8s... The app doesn't like to scale. And if the leader node gets terminated from a scale down, or an EC2 fails, processing stops while the leader is reelected. Hopefully not another node that is going down in a few seconds... Most of the app teams stopped trying to scale their app up and down because of this ...
I would run on ECS if AWS was my cloud at a start up. Then if scaling was getting too crazy, move to EKS.
But for the love of God ... Keep your monitoring and logging separated from your apps. Give it its own ECS cluster, or buy a fully managed solution. It is hard to record downtime if your monitoring goes down during your K8s upgrade.
But yeah... This is mostly because I had ADHD and depression which caused me to drop out of mechanical engineering school. Probably making a comparable or better wage than I would have. Wish I would have learned to code sooner though...
Wake up 4:45am, start work 5am (9am or 10am central). Make a bagel or something easy. Get drinks as needed. Get a snack before standup at 1pm central if needed. Get off at 1pm (5pm or 6pm central). Make lunch at that time. Eat dinner about 5-6pm. Head to bed at 7:30pm to 8pm.
I don't take a lunch. And if I do, I'll just work later or start earlier the next day.
I have to get on meetings at 4am sometimes when we do a deployment or have meetings with people who are more important than me. I've had to be on a 3am equivalent meeting once in the past 4 years. Small price to pay for the privilege of living in Hawaii.
Of course some places I've known sooner, but those are the exception.
If it wasn't for the quality of life my current jobs is providing, I'd probably find something else. I just can't find anything right now that is intriguing enough and pays enough for me to make the jump without losing benefits.
It sucks. But my body could be broken in other ways. I'll take this inconvenience. Hopefully it doesn't get worse before I retire.
But yeah, leaderboard is broken.
This is surprised Pikachu.