Live data from Hacker News

Show HN: Deploy to K8s without YAML using ShuttleOps

go.shuttleops.io

31–40 of 57 posts

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

#31
post #22
post #20

Earlier quoted context omitted.

PaaS came before K8s, it's the minimum that K8s is better than PaaS.

I actually don’t see why a PaaS couldn’t do all of this better. Especially at larger companies, where containers and monitoring have been the norm internally forever, it is unclear why PaaS offerings still feel primitive... maybe there is some technology limitation here. Edit: disclaimer, I have not used a PaaS service in a couple years.

I think PaaS, autodeployed from a branch, is the best system for most orgs.

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

#32
post #22
post #20

Earlier quoted context omitted.

PaaS came before K8s, it's the minimum that K8s is better than PaaS.

I actually don’t see why a PaaS couldn’t do all of this better. Especially at larger companies, where containers and monitoring have been the norm internally forever, it is unclear why PaaS offerings still feel primitive... maybe there is some technology limitation here. Edit: disclaimer, I have not used a PaaS service in a couple years.

What I was getting at was, maybe K8s folks should look ahead (serverless) and not back (PaaS).

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

#33
post #30
post #21

Earlier quoted context omitted.

This should be the top comment until remedied. This is super dangerous.

I created a report for Github, this is a leak on their side. And contacted ShuttleIO by mail. This could be ugly, Shuttle asks for broad permissions on Github.

Thank you for catching this. We are resolving this now

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

#34
post #25
post #15

Earlier quoted context omitted.

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 that is understandable, k8s is a platform with a plethora of capabilities. On the other hand, the vast majority of organizations using k8s have multiple users that have multiple work streams and multiple applications (not true by definition, but close). This lends itself to a code as configuration approach, and makes managing orchestration through a UI risky and error prone. We review code, not clicks. Further,…

I've been experimenting on a personal project with https://www.pulumi.com/ where you can do the configuration and deployment in Python or JavasScript and I think I can recommend it.

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

#36

No offense intended, but a generic marketing elevator pitch for a technical product makes me grumpy. I want to see the technical details, but I'm not signing up for your website just to dig for them. So this creates a missed opportunity where people like me will now not share it with their team.

None taken! This is great feedback.

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

#37
post #32
post #22

Earlier quoted context omitted.

I actually don’t see why a PaaS couldn’t do all of this better. Especially at larger companies, where containers and monitoring have been the norm internally forever, it is unclear why PaaS offerings still feel primitive... maybe there is some technology limitation here. Edit: disclaimer, I have not used a PaaS service in a couple years.

What I was getting at was, maybe K8s folks should look ahead (serverless) and not back (PaaS).

Serverless is not a strict upgrade to containerized service deploys in any sense.

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

#38
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…

> 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.

I think Dhall is in the right category of solutions for this problem. YAML needs to be reusable and text templates a la Helm are an amusingly bad solution. Moreover, I think static typing is a very nice feature for things that generate YAML since it’s so easy to make mistakes with these kinds of tools. I’ve used Starlark for these kinds of tasks in the past and the lack of static typing has been a sore point.

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

#39
post #18

YAML is the best part about deploying stuff to K8s, hardly a problem waiting to be solved IMO.

I'm not a k8s expert. Just touched it a bit here and there. And IMO yaml is fine but the problem is you often need yaml templates. I feel like projects like helm are in the templating html with php days. But instead of html+php you get yaml+go. Something better must be right around the corner because people have been solving similar problems for years.

https://cuelang.org is where I am going.

There is also https://dhall-lang.org of similar philosophy and more mature

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

#40
post #33
post #30

Earlier quoted context omitted.

I created a report for Github, this is a leak on their side. And contacted ShuttleIO by mail. This could be ugly, Shuttle asks for broad permissions on Github.

Thank you for catching this. We are resolving this now

Just a quick update. We have disabled oAuth2 logins (Github, GitLab and BitBucket) temporarily while we update our configuration settings.
Post reply on HN