I spent a lot of time in the medical imaging space... most of the owners of the businesses never understood that they were in the IT services / solutions space, and not just in the medical imaging space. The reason we did so well, was not just the diagnosis part, was but the IT services space and the platforms that were created by non-radiologists that also tried to learn what radiologists wanted to be more effective.
Yeah, I am that super knowledgeable K8s guy, but I’d still say true mainframe admins are still a higher metric.
But in regards to K8s talent, lots of the people who think they know Kubernetes in production but have never had to actually upgrade the cluster, or go through the process of having to update manifests, deployments, and CSIs, and having to actually deal with api removals.
Meme or not, it legitimately was my favorite "social media" site ever. I'd read interesting things on my feed, and share it to a pool with my other friends, who'd also share the interesting things they read, and we'd all be able to discuss it. It was like reddit but just for my group of friends. It was great.
I watched the recent developments to Twitter, Google and Reddit, and loved it all.
One way for self-hosted service to catch up is to wait for the big companies to mess up, and they're messed up very well at this moment.
Google previously changed their account expiration policy, and decided to lock users out of their usernames instead of allowing the old owner to re-active it, making the expiration permanently destructive for the user.
This effectively told their users that use of Google services is not "maintenance-free", you have to constantly engage with Google to keep it alive. And funny enough... maintenance costs is one of the reasons why people choose to abandoned their soft-host services.
Kubernetes has a default (and considered best practice) limit of 110 pods per node. Are you seeing them cap it lower than that? I've never checked this personally on EKS, TBH.
Also, what do you mean by capping resources? In my experience with EKS, I haven't had any issues fully utilizing a nodes resources, even in EKS.
A salesperson that I worked closely with like to use: “Drinking our own champagne.” I liked it enough I started using it though the engineer in me tends to be fine with “dogfooding”.
