5 ms·

Is k8s still in trending?

by tapirl 5y ago

GiorgioG 5y ago
I wish it would go away completely. Most orgs could get away with docker-compose.
- latch 5y ago
  Most orgs could get away with systemd.
  - joconde 5y ago
    We use both, but I much prefer docker-compose, because systemd scatters deployment files in system directories, which makes them a bit of a pain to find and backup. Not sure if we're doing it wrong. docker-compose is just one folder per service, much more practical.
  - p_l 5y ago
    The equation gets a bit different the further away you get from spending bonanza of silly valley
- linkdd 5y ago
  Situation A: We've built our infrastructure on top of docker-compose on a single node server We've grown enough so that we need more servers and now k8s seems like a good fit Uh oh, we need to rewrite everything or not use k8s and reinvent the wheel Situation B: We've deployed a single node k8s cluster and built our infrastructure on top of it We've grown enough so that we need more servers Good, just need to migrate to the new cluster, no need to rewrite anything > I wish it would go away completely Ain't gonna happen, because Docker Compose is only about running containers, there is no: - secret management - network policies - container scheduling with node affinity etc... - storage management - extensibility with other k8s operators (hello cert-manager, kubedb, kubevault, tekton, kubirds, etc...) - ... I love how HN hates k8s for no valid reason.
  - jakupovic 5y ago
    >I love how HN hates k8s for no valid reason. Circlejerk from people who don't run things in production, for those that do there is nothing better than k8s currently. ( period . )
  - shatteredspace 5y ago
    Preface this with I don't hate K8s. I see it as a solution and something to be used when the situation calls for it. I've used it quite a bit from directly interacting with it using Go and it's Go modules, using it's REST API, via kubectl, and via those that provide front-ends for it (Rancher). I see it as all about use-case, staffing, and what kind of instance you are using. Cloud-based? A-lot more freedom in being able to just deploying a cluster and not worry about much, on-prem based? Well dang now you've opened up having to be the one to update those nodes yourself - hope that you are a systems admin as well and have the time to perform said updates. Situation A - I'd like to introduce you to Docker Swarm. Secret management - sure K8s can do it, but I'm almost certain your organization as well as mine has accepted a vault of some sort that is not in K8s for end users and services to use. Now you just have to write your applications to use this. Network policies - while K8s can do this, I don't know if this is the strongest argument to use K8s or just a nice cherry on top. It feels like just a shift in responsibility or adding more granularity from your network security team. When does the situation call for it (in my opinion)? Your company has embraced the methodology of work with staffing for it and you have more than a handful of apps on more than a handful of nodes.
  - thinkharderdev 5y ago
    I wouldn't go so far as "no valid reason", but yeah, it is always fun to come on HN and see how everyone using k8s is just doing "resume-driven development" and mindless automatons manipulated by "marketing." I always find it amusing because a lot of these takes seem like thy are at least 5 years out of date. If you are on any one of the major cloud vendors, setting up a k8s cluster is almost trivial at this point. And that comes with a fully-managed control plane and a vibrant ecosystem of drop-in solutions for common deployment patterns. Do you always need k8s? Of course not, but it really is getting to the point where all but the most trivial of deployments could benefit from running on k8s. Are there other ways to do it? Sure, but the complexity of using k8s has been sanded down through widespread adoption and really nice tooling.
otabdeveloper4 5y ago
I hope not. I'm trying to get rid of a legacy kubernetes cluster I've inherited and it's a nightmare. Is there some sort of "how to get rid of k8s" service or tutorial out there? P.S. The kicker is that this cluster is only used to deploy a couple three-page static websites, run a few simple cron jobs (using literally crontabs) and launch a couple docker images straight from Dockerhub.
- siva7 5y ago
  Someone got their resume pushed...
  - p_l 5y ago
    I once went with k8s for similarly simple setup, because ultimately the pages weren't exactly static, weren't compatible with running them on one server, and we had to also take care of certs and other stuff. K8s meant that we could push this into much smaller and simpler infrastructure than otherwise.
- ZeroCool2u 5y ago
  Using K8s for what you described is so overkill it's hilarious.

Is k8s still in trending?

by tapirl 5y ago

Is k8s still in trending?

GiorgioG 5y ago

I wish it would go away completely. Most orgs could get away with docker-compose.

latch 5y ago
Most orgs could get away with systemd.
- joconde 5y ago
  We use both, but I much prefer docker-compose, because systemd scatters deployment files in system directories, which makes them a bit of a pain to find and backup. Not sure if we're doing it wrong. docker-compose is just one folder per service, much more practical.
- p_l 5y ago
  The equation gets a bit different the further away you get from spending bonanza of silly valley
linkdd 5y ago
Situation A: We've built our infrastructure on top of docker-compose on a single node server We've grown enough so that we need more servers and now k8s seems like a good fit Uh oh, we need to rewrite everything or not use k8s and reinvent the wheel Situation B: We've deployed a single node k8s cluster and built our infrastructure on top of it We've grown enough so that we need more servers Good, just need to migrate to the new cluster, no need to rewrite anything > I wish it would go away completely Ain't gonna happen, because Docker Compose is only about running containers, there is no: - secret management - network policies - container scheduling with node affinity etc... - storage management - extensibility with other k8s operators (hello cert-manager, kubedb, kubevault, tekton, kubirds, etc...) - ... I love how HN hates k8s for no valid reason.
- jakupovic 5y ago
  >I love how HN hates k8s for no valid reason. Circlejerk from people who don't run things in production, for those that do there is nothing better than k8s currently. ( period . )
- shatteredspace 5y ago
  Preface this with I don't hate K8s. I see it as a solution and something to be used when the situation calls for it. I've used it quite a bit from directly interacting with it using Go and it's Go modules, using it's REST API, via kubectl, and via those that provide front-ends for it (Rancher). I see it as all about use-case, staffing, and what kind of instance you are using. Cloud-based? A-lot more freedom in being able to just deploying a cluster and not worry about much, on-prem based? Well dang now you've opened up having to be the one to update those nodes yourself - hope that you are a systems admin as well and have the time to perform said updates. Situation A - I'd like to introduce you to Docker Swarm. Secret management - sure K8s can do it, but I'm almost certain your organization as well as mine has accepted a vault of some sort that is not in K8s for end users and services to use. Now you just have to write your applications to use this. Network policies - while K8s can do this, I don't know if this is the strongest argument to use K8s or just a nice cherry on top. It feels like just a shift in responsibility or adding more granularity from your network security team. When does the situation call for it (in my opinion)? Your company has embraced the methodology of work with staffing for it and you have more than a handful of apps on more than a handful of nodes.
- thinkharderdev 5y ago
  I wouldn't go so far as "no valid reason", but yeah, it is always fun to come on HN and see how everyone using k8s is just doing "resume-driven development" and mindless automatons manipulated by "marketing." I always find it amusing because a lot of these takes seem like thy are at least 5 years out of date. If you are on any one of the major cloud vendors, setting up a k8s cluster is almost trivial at this point. And that comes with a fully-managed control plane and a vibrant ecosystem of drop-in solutions for common deployment patterns. Do you always need k8s? Of course not, but it really is getting to the point where all but the most trivial of deployments could benefit from running on k8s. Are there other ways to do it? Sure, but the complexity of using k8s has been sanded down through widespread adoption and really nice tooling.

otabdeveloper4 5y ago

I hope not. I'm trying to get rid of a legacy kubernetes cluster I've inherited and it's a nightmare. Is there some sort of "how to get rid of k8s" service or tutorial out there? P.S. The kicker is that this cluster is only used to deploy a couple three-page static websites, run a few simple cron jobs (using literally crontabs) and launch a couple docker images straight from Dockerhub.

siva7 5y ago
Someone got their resume pushed...
- p_l 5y ago
  I once went with k8s for similarly simple setup, because ultimately the pages weren't exactly static, weren't compatible with running them on one server, and we had to also take care of certs and other stuff. K8s meant that we could push this into much smaller and simpler infrastructure than otherwise.
ZeroCool2u 5y ago
Using K8s for what you described is so overkill it's hilarious.