Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

As Kubernetes grows, a startup ecosystem develops in its wake

techcrunch.com

Post reply on HN
Print view View original

91–100 of 156 posts

Re: As Kubernetes grows, a startup ecosystem develops in its wake

#91

Post by shaklee3 »

anoncoward1234 wrote: post #55

Kubernetes is cool and all, but there needs to be a lot of simplification for it to be "nice to use". Essentially the problem is that it's the "opposite" of Golang - the number of ways to do the same thing is massive leading to huge numbers of headaches in trying to get things done. Recently, I spun up a simple pod-to-pod communication example but I found it pretty difficult. If you look up cluster networking in Kube…

Kops, kubeadm, rancher, kubespray all do what you want, but differently depending on your needs. What were you looking for?

Re: As Kubernetes grows, a startup ecosystem develops in its wake

#93

Post by praveenweb »

daxfohl wrote: post #86

There needs to be a digitalocean or heroku for containerization. Currently to start a k8s whatever you need to go through various manual rigamaroles and spend a lot of money, or go through the big lockin providers and spend a lot of money. For those of us not backed by venture capital and not charging SV ex-googler rates to our clients, we need something to say "we'll host you on this git push containerization thing,…

Check out https://hasura.io - you get git push based deployment on a kubernetes cluster.

Re: As Kubernetes grows, a startup ecosystem develops in its wake

#94

Post by hermitdev »

I'm curious: how does containerization work for systems that utilize kernel-bypass? Is it even possible?

I did a (admittedly short) search for kubernetes and kernel bypass, and the only thing that seem remotely relevant was [0], however it didn't indicate whether they work together.

For background, I work for a Dark Pool Alternative Trading System, and we currently utilize kernel bypass for all of our networking using Solarflare NICs & openonload [1].

In the same vein, curious how containers work with CPU shielding and pinning threads to specific cores. Is it possible, and how do multiple containers on the same box interact in that regard. Do they need to be quasi-aware of each other so as to not pin a thread to the same core?

I'd greatly appreciate if anyone with experience with containers can answer these questions. I'm genuinely curious, but it's not worth researching further if there's no solution that can handle these strict requirements (e.g. it's a non-starter if containers increase latency).

[0] https://thenewstack.io/life-post-container-world/ [1] http://openonload.org/

Re: As Kubernetes grows, a startup ecosystem develops in its wake

#95

Post by iampims »

daxfohl wrote: post #86

There needs to be a digitalocean or heroku for containerization. Currently to start a k8s whatever you need to go through various manual rigamaroles and spend a lot of money, or go through the big lockin providers and spend a lot of money. For those of us not backed by venture capital and not charging SV ex-googler rates to our clients, we need something to say "we'll host you on this git push containerization thing,…

https://hyper.sh aimed to be a CaaS (Container as a service) and Joyent’s Triton as well. It’s an interesting premise, but from the outside both don't have much traction.

Re: As Kubernetes grows, a startup ecosystem develops in its wake

#96

Post by outworlder »

lobster_johnson wrote: post #14
praseodym wrote: post #11

Earlier quoted context omitted.

Actually it is already possible to create persistent disks through Kubernetes by creating a persistent volume claim (pvc) which triggers an actual persistent volume to be created. Cloud provider controllers take care of this, just like they create load balancers for services. Also there’s already work being done on supporting cluster management from Kubernetes itself: https://github.com/kubernetes-sigs/cluster-api

That's not what I meant, though. A Kubernetes PV is an abstraction that causes a controller allocate a GCE disk (which of course is another abstraction), but if you create a GCE disk through the CLI/UI/API, then you don't get a PV.

You can add a PV manually to tie to some resource that was already created, but you don't get the bi-directional link. I'm not sure I'd even want K8s adding PV's for all volumes (maybe filtering by labels/tags would be ok).

This is approaching Terraform levels of complexity though. Unless you mean that cloud providers should do that when you create a volume, in which case I understand where you are coming from and well, they could do that. Although I'd much have them exposing a native K8s interface to take care of this PV and PVC for me and not showing me the underlying volumes at all.

Re: As Kubernetes grows, a startup ecosystem develops in its wake

#97

Post by outworlder »

yebyen wrote: post #22
colemickens wrote: post #15

Earlier quoted context omitted.

I think the point is that I don't have to touch the cloud provider's control plane in 99% of cases. Which brings the portability that first attracted me to Kubernetes.

The portability is not as attractive as a fully integrated solution though, for types of people that are not already attracted to Kubernetes. Where I work, we use AWS and say that "we love vendor lock-in." The more integration with the rest of the vendor's cloud platform, the better. I think it's a great example to say it is idiosyncratic that I can create a PD by creating a PV, but I can't reciprocally enumerate PDs…

I think I'm missing something.

K8s needs a role with the correct IAM permissions to create the resources on the AWS side, it can't do it magically. Which means that someone granted these permissions before.

If anything, your InfoSec department should love that. IAM is pretty fine-grained, so they can control what gets created. Types of resources, and whatnot. Just don't grant star permissions to all of EC2.

Re: As Kubernetes grows, a startup ecosystem develops in its wake

#98

Post by manigandham »

atombender wrote: post #3

Kubernetes is one of those rare cases where the industry is rallying around a technologically sound platform that emerged from the trenches, and not something that was designed to create jobs for consultants. It's great. Right now, there's a bunch of fairly traditional players such as Red Hat, but none of them are in a position to mess it up. What I'm waiting for, though, is for a big player to do a modern, clean "Ku…

>> Whoever wants to compete in this space have to compete not just with GKE, but with the technical awesomeness of GCP.

After years of using all the major clouds - Google Cloud has the best performance and primitives, but the worst support and operational/business features. If you want the fastest VMs/storage/networking, and are fine with non-standard APIs and beta SDKs, then it's a great platform and has super simple billing.

AWS and Azure are much better suited for most companies and startups though in terms of actually getting your business running with standard tooling, large ecosystems, and a massive portfolio of services.

Re: As Kubernetes grows, a startup ecosystem develops in its wake

#99

Post by manigandham »

lobster_johnson wrote: post #14
praseodym wrote: post #11

Earlier quoted context omitted.

Actually it is already possible to create persistent disks through Kubernetes by creating a persistent volume claim (pvc) which triggers an actual persistent volume to be created. Cloud provider controllers take care of this, just like they create load balancers for services. Also there’s already work being done on supporting cluster management from Kubernetes itself: https://github.com/kubernetes-sigs/cluster-api

That's not what I meant, though. A Kubernetes PV is an abstraction that causes a controller allocate a GCE disk (which of course is another abstraction), but if you create a GCE disk through the CLI/UI/API, then you don't get a PV.

Why would you expect that? Or use it that way? The clouds are IaaS, and Kubernetes is like a virtual human that creates resources using the same APIs you would. It's on K8S to keep track of what it's creating.

Re: As Kubernetes grows, a startup ecosystem develops in its wake

#100

Post by anoncoward1234 »

shaklee3 wrote: post #91
anoncoward1234 wrote: post #55

Kubernetes is cool and all, but there needs to be a lot of simplification for it to be "nice to use". Essentially the problem is that it's the "opposite" of Golang - the number of ways to do the same thing is massive leading to huge numbers of headaches in trying to get things done. Recently, I spun up a simple pod-to-pod communication example but I found it pretty difficult. If you look up cluster networking in Kube…

Kops, kubeadm, rancher, kubespray all do what you want, but differently depending on your needs. What were you looking for?

EXACTLY
Post reply on HN