Live data from Hacker News

Microsoft launches new open-source projects around Kubernetes and microservices

techcrunch.com

61–70 of 129 posts

Re: Microsoft launches new open-source projects around Kubernetes and microservices

#62
post #29

Earlier quoted context omitted.

i honestly have trouble understanding the love for yaml when decades ago everything was xml and it was almost universally hated. technically you can define a yaml-xml isomorphism and as a consequence they both should be treated as unsuitable, and yet... yaml somehow is cool and xml isn't. am i just old?

I don't really understand what you're saying here. It's definitely not a matter of being "cool" or not. There's always going to be a need for some structured static configuration file format. Be it XML, INI, TOML, JSON, YAML, properties files, or whatever. From my perspective, YAML and JSON have been more successful and well-liked than XML because they map much more directly to the basic data types common to all prog…

serialization is explicitly not the problem being discussed. JSON also sucks at serialization but much less than YAML or XML both. i don't care that much about serialization.

what i care about is writing yaml for the purpose of configuration and not have any feedback about whether the data i've prepared by hand is actually a valid configuration. not having to have a schema is a bug in the spec for this use case in all those nice acronyms and shortcuts you've listed above and they're all guilty of it. i'd like my configs strongly typed and well documented and none of the above helps developers do that - and that's where my confusion comes from.

Re: Microsoft launches new open-source projects around Kubernetes and microservices

#64

Basically this is a helm chart. Which is one of the problems of k8s - a typical application consists of multiple services that need to be deployed together. In Docker Swarm, that's a Stack. K8s has no equivalent. So there's no answer to "how do i deploy/update my flask api and celery workers together"

I don't think there is anything stopping you from bundling multiple services/deployments in the same helm chart. Many of the "curated" helm charts do it: https://github.com/helm/charts

Re: Microsoft launches new open-source projects around Kubernetes and microservices

#65
post #7

OAM is essentially a YAML file. It can be put in a service catalog or marketplace and deployed from there. But what’s maybe most important, says Russinovich, is that the developer can hand off the specification to the ops team and the ops team can then deploy it without having to talk to the developer. This statement sounds very backwards to me. Isn't this increasing the separation between devs and ops which we want…

Wouldn't this be because they want the ops team to be Azure and don't want the developer to talk to customer support?

Re: Microsoft launches new open-source projects around Kubernetes and microservices

#66
Worry about vendor lock-in is real.

RedHat OpenShift (yes yes IBM) is gaining momentum because of it. But the field is still wide open. And the burden will fall on small ISVs to provide open solutions around data portability, redundancy, security, and a host of other concerns.

In the early days of Cloud technologies, the original vision was highly commoditized. You'd pull a Docker container from a registry hub and perhaps not even know where it ran. Perhaps even an exchange would handle pricing and performance. Instead, we have the Big 4 vendors in a highly fragmented space offering roughly the same services.

Re: Microsoft launches new open-source projects around Kubernetes and microservices

#68
post #67

All of this is well and good. Now find folks who understand the entire stack and can support it. Tell me you are saving money after you hire them :)

I really don't understand how this point isn't more widely acknowledged. k8 expertise is expensive. I'm seeing companies jump in head-first without doing any cost-benefit analysis, and winding up in some really difficult situations.

Re: Microsoft launches new open-source projects around Kubernetes and microservices

#69
post #67

All of this is well and good. Now find folks who understand the entire stack and can support it. Tell me you are saving money after you hire them :)

I really don't understand how this point isn't more widely acknowledged. k8 expertise is expensive . I'm seeing companies jump in head-first without doing any cost-benefit analysis, and winding up in some really difficult situations.

First mover advantage. And when the recession hits you fire them and your pipeline should be mostly automated by then... The rest is still paying full monolithic big servers. And slow deployments.

Re: Microsoft launches new open-source projects around Kubernetes and microservices

#70
Somehow these enterprise people have turned Kubernetes, which basically was an advanced job scheduler for compute resources, into a unnecessary complex monster (just look at the LOC of kube-api). And that's still pretty decent compared to all the other projects in the ecosystem (looking at OpenShift, Istio ...). I really don't believe a lot of people have a valid use case for these projects like OAM when you look at the complexity, failure cases and administrative tasks these systems introduce.

The one of the main design ideas behind the original Borg system (which Kubernetes is inspired by) was utilisation of resources and simplicity. Now we just stuff all the compute power we got with unnecessary proxy systems that provide minimal value. I truly believe we have lost our way.

Post reply on HN