Live data from Hacker News

Gravity: Upstream Kubernetes packaging tools

github.com

1–10 of 43 posts

Re: Gravity: Upstream Kubernetes packaging tools

#3
I find each new development in the field of deploying Kubernetes to be grimly humorous. We had lots of techniques to package and deploy things before Kubernetes, but they were complex and inadequate in some ways, and Kubernetes fixes some of those issues. But it turns out Kubernetes itself is substantially more complicated to package and deploy than the old solutions, if you're deploying it yourself rather than using some proprietary cloud. Oops!

What I just can't decide is whether we'll successfully put another layer of container-container-containers on top of Kubernetes, or whether the whole effort will eventually collapse and we'll extract the good parts out into something simpler.

Re: Gravity: Upstream Kubernetes packaging tools

#4
post #2

Hey all, I'm part of the team at Gravitational - a company behind this effort. Will be happy to answer any questions about this project.

This seems to assume that each app will run on a separate Kubernetes cluster. Have you given any thought to packaging apps which will run on a single Kubernetes cluster?

Re: Gravity: Upstream Kubernetes packaging tools

#5
post #2

Hey all, I'm part of the team at Gravitational - a company behind this effort. Will be happy to answer any questions about this project.

This seems to assume that each app will run on a separate Kubernetes cluster. Have you given any thought to packaging apps which will run on a single Kubernetes cluster?

Yep, check out integration with helm for multiple apps:

https://gravitational.com/gravity/docs/catalog/#publish-an-a...

It's something we support right now, but still polishing UX, the idea is to add more support for Helm 3.0 in the future in addition to Helm 2.0 we already support.

Re: Gravity: Upstream Kubernetes packaging tools

#6
post #3

I find each new development in the field of deploying Kubernetes to be grimly humorous. We had lots of techniques to package and deploy things before Kubernetes, but they were complex and inadequate in some ways, and Kubernetes fixes some of those issues. But it turns out Kubernetes itself is substantially more complicated to package and deploy than the old solutions, if you're deploying it yourself rather than using…

Kubernetes cluster is hard to operate indeed. Techniques that we always had to deploy before Kubernetes, for example package managers, don't always translate to operating a distributed system on a hundreds or thousands of servers.

Some of this complexity is definitely incidental, not all components are not always coordinating well with each other, e.g. docker and API server, networking layer during upgrades for example.

On the other hand lots of this complexity is essential - K8s is a distributed system with database, network and container orchestration layer solving a hard problem.

Re: Gravity: Upstream Kubernetes packaging tools

#8
post #5

Earlier quoted context omitted.

This seems to assume that each app will run on a separate Kubernetes cluster. Have you given any thought to packaging apps which will run on a single Kubernetes cluster?

Yep, check out integration with helm for multiple apps: https://gravitational.com/gravity/docs/catalog/#publish-an-a... It's something we support right now, but still polishing UX, the idea is to add more support for Helm 3.0 in the future in addition to Helm 2.0 we already support.

Looks like that functionality is locked behind the Enterprise edition correct?

Re: Gravity: Upstream Kubernetes packaging tools

#9
post #8
post #5

Earlier quoted context omitted.

Yep, check out integration with helm for multiple apps: https://gravitational.com/gravity/docs/catalog/#publish-an-a... It's something we support right now, but still polishing UX, the idea is to add more support for Helm 3.0 in the future in addition to Helm 2.0 we already support.

Looks like that functionality is locked behind the Enterprise edition correct?

Seems like we have to fix the docs a bit, `gravity app` is supposed to work with any helm registry or even without one:

  tele build helm-package ->> tarball
  gravity app install tarball

Re: Gravity: Upstream Kubernetes packaging tools

#10
post #2

Hey all, I'm part of the team at Gravitational - a company behind this effort. Will be happy to answer any questions about this project.

Would Gravitational ever think about creating a more generic layer on this, e.g.: to manage Mesos, Nomad, or something else entirely like Corosync via some kind of driver system?

I love Teleport but don't use k8s anywhere.

Post reply on HN