3 ms·
If they are reluctant and only do it because they have to, are they really the right vendor for managed k8s? What about them makes for a good trade-off when co
by verdverm 3y ago
If they are reluctant and only do it because they have to, are they really the right vendor for managed k8s?
What about them makes for a good trade-off when considering the many other vendors?
- szundi 3y agoIf their reluctance were based on valid reasons that they handled in a unique way - might be good. In theory.
- verdverm 3y agok8s has become a standard api and platform for running apps, having a * on it makes the implementation an outlier from the standard, not normally considered a good thing because you have to be aware of the nuanced differences.
- paxys 3y agoMaybe a got fit for someone who is reluctant to use Kubernetes but has to for whatever reason.
- nailer 3y agoIf someone isn't a cloud provider they should be reluctant to use Kubernetes.
- paxys 3y agoPlenty of companies/teams qualify as "cloud providers" even though all the usage is internal.
- verdverm 3y agoAren't most k8s users not cloud providers? It's more about good abstractions and APIs for running applications in the cloud. Cloud providers are the one's offering the APIs and abstractions we use, and increasingly putting k8s abst/apis at the forefront, because that is where industry has moved to
- nailer 3y ago> Aren't most k8s users not cloud providers? Yes. The point still stands.
- verdverm 3y agoPeople and companies use it because it makes this easier in several areas, it's industry standard at this point. Can you explain why we should be reluctant to use k8s?
- nailer 3y ago> People and companies use it because it makes this easier in several areas Compute on demand is significantly more complex using k8s than what most companies already pay for from their own cloud provider, AWS is the industry standard for this purpose, followed by Azure, then TF, then Pulumi maybe. k8s is a meme for resume-driven development.
- verdverm 3y agoOk, you're obviously just a hater and aren't worth taking seriously
- deleted 3y ago[deleted]
- tptacek 3y agoWe're not a K8s vendor. We're a lower-level platform than that. If all you care about is K8s, and no part of the rest of our platform is interesting to you --- the global distribution and Anycast, the fly-proxy features, the Machines API --- we're not a natural fit for what you're doing. We were surprised at how FKS turned out, which is part of why we decided to launch it as a feature and all of why we wrote it up this way. That's all.
- verdverm 3y ago> We're not a K8s vendor It might now be more accurate to say "You were not a k8s vendor", but now you are based on > If K8s is important for your project, and that’s all that’s been holding you back from trying out Fly.io, we’ve spent the past several months building something for you. If it's fundamentally different, maybe you shouldn't call it Kubernetes, perhaps a Kubernetes API compatible alternative? fwiw/context, I use GKE and also many of the low-level services on GCP Is Fly supposed to be simpler for the average developer?
- kasey_junk 3y agoAre any of the cloud provided managed K8s offerings just K8s under the covers? I’ve always assumed all of them shim the K8s api onto other more bespoke orchestration systems.
- verdverm 3y agoMost are pretty much actually k8s, though they tend to have different ways of handling the masters, my understanding is that it's the same k8s binaries and code What I've seen is the k8s APIs working their way into other systems like cloud functions and servers, so you can use the same Yaml across vendors and products. This is further solidifying k8s APIs as an industry standard Searching "managed kubernetes providers" is a good starting point to learn about the various offerings
- kasey_junk 3y ago
- frenchman99 3y agoProbably good for people already used to fly or interested in fly for other reasons, that could also use k8s ? Sometimes you just want to run k8s without thinking too much about it, without having all the requirements that gcp have answers to.
- grossvogel 3y agoI'm excited about this as a way to configure my Fly.io apps in a more declarative way. One of my biggest gripes about Fly.io is that there's a lightly documented bespoke config format to learn (fly.toml), and at the same time there's a ton of stuff you can't even do with that config file. I love Kubernetes because the .yaml gives you have the entire story, but I'd _really_ love to get that experience w/o having to run Kubernetes. (Even in most managed k8s setups, I've found the need to run lots of non-managed things inside the cluster to make it user-friendly.)