Live data from Hacker News

Show HN: Deploy to K8s without YAML using ShuttleOps

go.shuttleops.io

11–20 of 57 posts

Re: Show HN: Deploy to K8s without YAML using ShuttleOps

#11
We've gone full circle:

1. Pre-kub: orchestration is manual through AWS EC2 ui

2. Kub: orchestration is automated and configuration is treated as code (YAML, JSON, proto, whatever) and kept in revision control just like source code

3. Post-kub: orchestration is manual through a ui

In all seriousness I'm sure this is useful in limited cases, but for most the right answer isn't some fancy UI, its middleware or some layer on top of kubernetes that allows you to automate away the toil-y parts of YAML, but keep the flexibility.

EDIT: line breaks.

Re: Show HN: Deploy to K8s without YAML using ShuttleOps

#13

Is this like a visual/gui Terraform or Ansible?

Hi! ShuttleOps allows you to create workflows for deploying to Kubernetes without writing YAML manifest files. In that way you could consider it a visual/gui for the terraform kubernetes provider, sure!

Re: Show HN: Deploy to K8s without YAML using ShuttleOps

#15
post #11

We've gone full circle: 1. Pre-kub: orchestration is manual through AWS EC2 ui 2. Kub: orchestration is automated and configuration is treated as code (YAML, JSON, proto, whatever) and kept in revision control just like source code 3. Post-kub: orchestration is manual through a ui In all seriousness I'm sure this is useful in limited cases, but for most the right answer isn't some fancy UI, its middleware or some lay…

What I like about Kubernetes is that it’s a platform you get things like exponential backoff, replication, liveness and health checking and so forth as part of the platform, and plugins for metric collection and monitoring are fairly standard. These are things I don’t even feel most PaaS have done a great job on across the board, so I can certainly see the appeal of having Kubernetes under the hood.

Re: Show HN: Deploy to K8s without YAML using ShuttleOps

#17
Be careful: with Github auth, the redirection directs you to a non-HTTPS version of their app. The Github token might leak at that point...

EDIT: I don't even know how it is possible, this is an Oauth2 Flow and should never redirect to a non HTTP URL from Github.

Also: the fact that shuttleio doesn't have hsts or at least a 301 to HTTPS from HTTP is not brilliant either.

Re: Show HN: Deploy to K8s without YAML using ShuttleOps

#19
post #15
post #11

We've gone full circle: 1. Pre-kub: orchestration is manual through AWS EC2 ui 2. Kub: orchestration is automated and configuration is treated as code (YAML, JSON, proto, whatever) and kept in revision control just like source code 3. Post-kub: orchestration is manual through a ui In all seriousness I'm sure this is useful in limited cases, but for most the right answer isn't some fancy UI, its middleware or some lay…

What I like about Kubernetes is that it’s a platform you get things like exponential backoff, replication, liveness and health checking and so forth as part of the platform, and plugins for metric collection and monitoring are fairly standard. These are things I don’t even feel most PaaS have done a great job on across the board, so I can certainly see the appeal of having Kubernetes under the hood.

Yeah, there's a whole category of apps that run on heroku with maybe 10 dynos tops that could definitely be deployed on kubernetes with manual / web ui-based configuration.

Re: Show HN: Deploy to K8s without YAML using ShuttleOps

#20
post #15
post #11

We've gone full circle: 1. Pre-kub: orchestration is manual through AWS EC2 ui 2. Kub: orchestration is automated and configuration is treated as code (YAML, JSON, proto, whatever) and kept in revision control just like source code 3. Post-kub: orchestration is manual through a ui In all seriousness I'm sure this is useful in limited cases, but for most the right answer isn't some fancy UI, its middleware or some lay…

What I like about Kubernetes is that it’s a platform you get things like exponential backoff, replication, liveness and health checking and so forth as part of the platform, and plugins for metric collection and monitoring are fairly standard. These are things I don’t even feel most PaaS have done a great job on across the board, so I can certainly see the appeal of having Kubernetes under the hood.

PaaS came before K8s, it's the minimum that K8s is better than PaaS.
Post reply on HN