4 ms·
I don't understand all the negative comments here, K8S solves many problems regardless of scale. You get a single platform that can run namespaced applications
by manigandham 8y ago
I don't understand all the negative comments here, K8S solves many problems regardless of scale. You get a single platform that can run namespaced applications using simple declarative files with consolidated logging, monitoring, load-balancing, and failover built-in. What company would not want this?
- mirceal 8y agothis is too broad. i think that may actually be the problem: in theory it can do a lot of things, but in the real world it’s hard to get all those theoretical benefits. for me, if you’re in the cloud you don’t need k8s. your favorite cloud provider has already figured out logging and monitoring and the basic things you need to get going. (another story if you run on bare metal) if you’re not running a legacy app you don’t really need containers either. containers are great for legacy apps, for poorly written software or if you like overengineering. the abstraction you need is called a vm. use it. (again if you are in the cloud). your app/service/thing is not as complicated as you think it is (or at least it should not be). I see a lot of people feeling like they need to experiment with new technology, on the job, on whatever they are doing now. actually building something that works and is simple as fuck seems to take a backseat and these types of people will create a narrative around using the new flashy thing. this is how you end up with production systems leveraging tools in beta and you end up closing shop when you finally figure out that you don’t have the resources to understand and maintain what you’ve created. there is a time and place to experiment and learn. on small projects or on your own time. it takes experience to understand the hype cycle and to distinguish good tech from the hype. as for k8s? yes, it solves some problems but it also creates others. do you like basically spending the time you’ve saved on setup and deployment to maintain/troubleshoot/upgrade your cluster? knock yourself out.
- manigandham 8y agoThere is a very big gap between IaaS and PaaS. K8S is an abstraction on top of VMs so you can have a customizable PaaS that runs on YAML code. It has nothing to do with how complex your app is because K8S is about running it with less work in a declarative fashion. I'm currently in and have worked with dozens of startups that have saved lots of time by removing all the ops overhead with K8S because it runs the servers and we can just deploy our apps. It seems like most of the problems are actually about installing and running K8S software itself, but then 95% of companies won't be doing that and using the managed offerings instead. This is no different than companies using the cloud over running their own DCs.
- ukoki 8y ago"Every sufficiently large K8s deployment contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of a PaaS" K8s may well be the best foundation upon which to build a PaaS, but I think building a PaaS should be met with the same eye-rolls as writing your own crypto. Use Heroku or GAE or Elastic Beanstalk or IBM BlueMix or Azure PaaS or Cloud Foundry or Openshift.
- manigandham 8y agoIt's just YAML files, there's nothing to build.
- jacques_chester 8y agoYou can go entirely with YAML in a PaaS. Unless you feel you want it. Just push code. That's it. That's all you need to do.
- manigandham 8y agoHow is that different though? You have to setup the PaaS the first time, the same as you write the YAML file the first time. After that you push code regardless of destination.
- jacques_chester 8y agoI think we have different ideas of what a PaaS is.
- ukoki 8y agoIt's just YAML until you need: * multi-tenancy * auto-scaling * security auditing * automated os/container patching * multi-tenant self-service route/ingress management * multi-tenant self-service logging, monitoring and alerting * multi-tenant self-service databases and so on
- pgwhalen 8y agoI very much agree that kubernetes is useful in an environment that doesn’t need to scale, but do tell how it enables consolidated logging and monitoring, since my medium/small shop is spending quite some time setting up our own infrastructure for it.
- manigandham 8y agoAre you running it yourself? The K8S dashboard gives you logs and basic monitoring out of the box, or you can get logs directly from kubectl.
- pgwhalen 8y agoWe are. I guess I wouldn’t consider that enough for our purposes. Actually retaining and alerting on logs, or alerting on anything for that matter is not out of the box unless I’m missing something.
- AlexB138 8y agoThe typical approach is to setup Fluentd for logging. You set it up as a daemonset, and have it mount /var/docker from the host. That gives it access to all container logs, which you then stream to your desired store.
- pgwhalen 8y agoYeah - that’s far from batteries included though, and comes with many limitations, especially for non-12-factor apps. It also doesn’t begin to answer questions about what that log store is, or how to alert on the contents of logs.
- erulabs 8y agoI run a Filebeat container with privileges to read stdout/stderr of all other pods, which then forwards to ElasticSearch. (https://www.elastic.co/guide/en/beats/filebeat/master/running-on-kubernetes.html https://www.elastic.co/guide/en/beats/filebeat/master/runnin...). It's fairly straight forward, then Kibana + Watcher can ship alters to PagerDuty based on log patterns / queries / limits, etc. I think Watcher is open-source/free now? I also have Prometheus + grafana, which similarly collects lots of stats from around the cluster, but I'm fairly sure I'm the only person who uses that dashboard, since the only things hooked up to Prometheus are databases and such, no internal applications (yet!). Being able to aggregate stdout/stderr across dozens of machines previously would have cost either a lot of Chef setup time or a contract with some provider. Now I get a fairly straight forward open-source stack that can be refined over time, and the yaml re-used very easily in any cluster. Plus, the metadata collected from Kubernetes about each log line is extremely useful (For example, out of the box you can query by Kubernetes labels for your graphs etc)
- JeremyNT 8y agoFrom a developers' perspective, k8s feels like a holy Grail. Having fully embraced it with my latest rails app, I can say confidently that I've never had a more straightforward and enjoyable experience than K8s. It's absolutely the correct abstraction layer for me; it gives me all the power I could ask for in as concise a definition as I could possibly expect. I think a lot of the complaints against K8s are from the ops side of things. In my org, I don't actually run or upgrade the K8s cluster myself, so those pain points aren't mine to bear. When you're running your own k8s, the operational complexity of managing the cluster itself is not trivial and the change in mindset for traditional sysadmin types is a substantial hurdle. My own take: K8s (or something very much like it) is absolutely the future, but the operational challenges of migrating to it at this time should not be ignored if you want to run it yourself and have existing ops experience. This will only get easier over time as tooling improves and sysadmins start seeing that this is the future they have to embrace.
- manigandham 8y agoAgree, although I don't think the Ops portion is that hard either, at least certainly not that different from all the other complex software that used to be installed and maintained. I feel it's just the usual pushback against change and general commoditization of IT that's leading to most of the complaints.
- JeremyNT 8y agoI think I agree with this also, but my experience is limited enough to allow for the likelihood of additional complexity and gotchas that will become evident over time. I'm sympathetic to concerns of ops, having worked in that space before working as a developer. It's tough to dive into a new approach and discard existing, well understood solutions. It's an especially hard sell when the benefits of the new tech are opaque and/or don't solve problems you personally have (until I actually used k8s for my own project, I really didn't understand the hype either). I'd suggest though that the "usual pushback" is a powerful force on its own that may make k8s a poor fit for an org (right now). If some portion of the staff - especially those responsible for reliably maintaining the infrastructure - is resistant to the approach, rushing adoption is highly likely to lead to failure (if for entirely non-technical reasons). The benefits of k8s will only become more apparent and more easily realized over time, and the opportunity cost of waiting until there are fewer "Kubernetes Failure Stories" on HN might not be all that great.
- bogomipz 8y agoLogging and monitoring are not built in to K8S, at least not something you would rely on for operational purposes. I believe most people use an EFK/ELK stack for centralized logging and Prometheus for Monitoring.