> To make a cluster useful for the average workload a menagerie of add-ons will be required. Some of them almost everyone uses, others are somewhat niche.
This is the concern I have with k8s. All this complexity introduces operational and security concerns, while adding more work to do before you can just deploy business value (compared to launching on standard auto-scaling cloud instances)
If you are using a managed kubernetes cluster from a cloud provider you mostly don't need to worry about these sorts of things. If you're not, and deploying to bare metal, the main things you need to worry about are: load balancers, storage & monitoring. If you're large enough that you can effectively run kube on bare metal you probably have enterprise solutions for load balacing [0], storage [1] & monitoring your applications that you've already validated as being secure/stable.
If you want to go all out you can also grab an operator to manage rolling out databases for you (postgres [2], mongo, etc).
A lot of the complexity people bump into with kube is really poorly planned out tools like Istio that have way too many features, a very overly complex mode of operation (out of the box it breaks CronJobs!!!), and very sub-standard community documentation. If you avoid Istio, or anything that injects sidecars and initcontainers, you'll find the experience enjoyable.
It's the classic trade-off of cost vs benefit. In places I've worked, the benefit has been worth it. The kind of add-ons mentioned in the article are in keeping with the decision for the orchestrator (which is already complex) not trying to do absolutely everything. I feel that is a good thing.
It's kind of like an API gateway with traditional microservice instances. If you have DNS and load balancers pushing requests directly to your services, you might wonder why you would ever need such a thing. Until you do.
As a rule of thumb, the quality of engineering of the core Kubernetes distribution is rock solid and incredible, but anything that's not is in varying stages of maturity.
How much Kubernetes-adjacent code you actually need to adopt (and therefore, how much risk you take on) depends from project to project and organization to organization.
That's not a really accurate portrayal of events. Federalism may have increased as an outcome, but that was not why the war started, nor why the Union-aligned states continued to fight for several years despite losses
I have too. Staring at my keyboard in complete disbelief that a password I used hours before had fallen out of my head. Still amazes me that I can forget things so easily
Indeed. I forget where I read it, but it provides that power increase for (IIRC) some small double digits number of seconds before you need to throttle back, or the engine eats itself. If you are able to make it back to base, and that WEP wire is broken, the engine needs a rebuild before it flies again. Definitely an impressive power boost though.
The MiG-25 also have something similar where the engine redline is marked around Mach 2.8, but there's no system stopping the pilot from keeping it maxed to somewhere above Mach 3 but damaging the engine in the process.
Funnily enough I believe the SR-71 has the opposite problem, where the engines would merrily go above Mach 3.5 with no issue but the airframe and everything attached to it would get torn apart by the intense heat if the pilot tried to go any faster
No, SR-71s are still limited by engine temperature. They measure the Compressor Inlet Temperature, but I suspect that actual limitation is the turbine inlet temp. That said, it'll merrily try to go above that without issue if you don't throttle back.
Additionally, there's the Mach Cone. The shock wave off the nose forms a cone shape, with the angle determined by the speed of the aircraft. From the nose to the wingtip forms an angle of about 17.5 degrees, which corresponds well with the max speed from the CIT of Mach 3.3.
That both methods of determining max speed agree shouldn't be surprising. Skunk Works was filled with good engineers.
MiG-31 has limiter on engine controls connected to airspeed and mach number indicators, because the engine will happily run above Ma 3, with no issues.
The airframe, however, will get bent from temperature and you better hope the missile cooling loops don't fail.
The power isn't dialed down at lower speeds in order to provide thrust for maneuvering and climb.
She never actually outright called her boss an idiot. The most literal interpretation of the title is "if you feel this way about your boss, then here is why you may feel that way." I certainly hope that was her intended meaning, because the counterfactual is very risque. I did think the title was unnecessary though, and the naming.
Sounds good, but I don’t know a lot of “active” Google Sites admins. Is Google going to offer a searchable cache? When I google search a hard question, many times I’m brought to Google Sits
We’re going to lose a valuable source of old data if former admins don’t show up, do the work, and rehost
This is the concern I have with k8s. All this complexity introduces operational and security concerns, while adding more work to do before you can just deploy business value (compared to launching on standard auto-scaling cloud instances)