91–100 of 106 posts
the problem I have with k8s or whole concept of "cloud native" is it almost ONLY focus on web based application, if your application is not HTTP based or "stateless", it is very hard to run or design to be "cloud native" , specially in a managed k8s service(like eks/aks).
Earlier quoted context omitted.
if you're at the size of needing K8S, you can afford a devops/cloud engineering team. To OP's point, this seems to be a trend among corporate blogs. Targeting devs with irrelevant content. A few weeks back I remember seeing a "SOC 2 for devs" blog article and was really scratching my head. That's not the level that devs work at, at all. If you're paying six figure salaries to devs to sit around all day worrying about…
No. Kubernetes is extremely valuable to small orgs. Google Kubernetes Engine is pretty much fire & forget. You turn it on, set the maintenance window and it just works. It also saves you from having to reinvent health checks, ingresses, etc. It's actually less work than maintaining plain old servers when you factor in maintenance, and since state is immutable you don't run into issues where some developer fixed an is…
Is there a platform for small companies to ease deployment and maintenance? Something like order vps, apt install that, go to ip:4321, login, enter a master ip, and now it’s part of a farm to which you can drag and drop containers (or repositories, or even just init scripts with tarballs) and edit configs/secrets accordingly, and see logs. I understand docker and what k8s does, but in our situation setting them up an…
You might be best served by some platform-as-a-service (Heroku, platform.sh, Netlify, ...) than by a cluster offering. PaaS are pretty much turnkey for many apps, and cost mostly scales with the actual usage which tends to fit well small companies. They completely hide infra management from you, deployment can be entirely automated through Git with no SSH or Docker registry management, and they provide access to what…
So if you are looking for the easy solution, use a SaaS / PaaS that really is turnkey and, for example is not just another peaky abstraction of kubernetes. You are choosing an easy solution so you should not need to invest a lot of your energy. Likewise recognize that when you need more customization that you might need to jump ship instead of investing in ducktaping your SaaS/PaaS.
Earlier quoted context omitted.
My biggest issue with Kubernetes is huge costs of running it. It's 3 servers with 4 GB RAM. It's almost $100/month just for Kubernetes alone. And you need one load balancer for control nodes which is another $25 for my hoster. And you need second load balancer for production workloads which is another $25. So you have to pay $150/month for the privilege of using Kubernetes. And they double your costs for your applica…
k3s will run on a $5 droplet happily. If you want k8s for the yaml and not for the heavy-duty hyperscale redundancy, k3s works great
Is there a platform for small companies to ease deployment and maintenance? Something like order vps, apt install that, go to ip:4321, login, enter a master ip, and now it’s part of a farm to which you can drag and drop containers (or repositories, or even just init scripts with tarballs) and edit configs/secrets accordingly, and see logs. I understand docker and what k8s does, but in our situation setting them up an…
You might be best served by some platform-as-a-service (Heroku, platform.sh, Netlify, ...) than by a cluster offering. PaaS are pretty much turnkey for many apps, and cost mostly scales with the actual usage which tends to fit well small companies. They completely hide infra management from you, deployment can be entirely automated through Git with no SSH or Docker registry management, and they provide access to what…
Earlier quoted context omitted.
Can you tell me what specific challenges you've had with deploying non-HTTP services using Kubernetes? Many features are http-centric, but others seem fairly agnostic to me. What kind of non-http services are we talking about anyway?
Not OP and I don't do K8 in production, but I understand their complaint. You couldn't eg. deploy a game server easily. They typical "web app" flow is Client -> ReverseProxy -> StatelessApp -> DatabaseWithState and back. The typically expectation is HTTP requests that aren't "long lived". Even running a database would be harder since you need to consider where the storage of the content is going (you'd want backups a…
Earlier quoted context omitted.
No. Kubernetes is extremely valuable to small orgs. Google Kubernetes Engine is pretty much fire & forget. You turn it on, set the maintenance window and it just works. It also saves you from having to reinvent health checks, ingresses, etc. It's actually less work than maintaining plain old servers when you factor in maintenance, and since state is immutable you don't run into issues where some developer fixed an is…
At a small org, what is the advantage of Kubernetes over the vendor provided application runners i.e. AWS AppRunner or Google's App Engine?
Earlier quoted context omitted.
Can you tell me what specific challenges you've had with deploying non-HTTP services using Kubernetes? Many features are http-centric, but others seem fairly agnostic to me. What kind of non-http services are we talking about anyway?
Deploying them is easy. Figuring out the correct incantations to bind a load balancer or ingress port to redis/kafka/mysql/whatever and/or expose them in some way other than "let the ingress figure out the host from headers/SNI and map to some thing in the Service" is somewhat less than intuitive. Sure, you could argue that you shouldn't expose backend services like that without an API endpoint at all, because one ap…
I don't think that would cause issues with long lived connections. It is about as direct as you can get while actually load balancing.
https://cloud.google.com/kubernetes-engine/docs/how-to/servi...
Kubernetes was a clever ploy to trick cloud providers into abstracting themselves into irrelevance, but otherwise a dead end. Can we please hurry up and replace it with an open-source Nomad clone?
IMO Kubernetes is not going anywhere. People are jumping to it in huge numbers. It's very hot. It has sane architecture in my opinion. I'd say it has awesome architecture and I have great respects to the ones responsible for it. They've got very quality foundations. Kubernetes is new Linux. You expected to know Linux and Git, now you'll be expected to know Kubernetes if you're developer.
~HN, circa 2010
Kubernetes was a clever ploy to trick cloud providers into abstracting themselves into irrelevance, but otherwise a dead end. Can we please hurry up and replace it with an open-source Nomad clone?
> replace it with an open-source Nomad clone? Nomad is open source; why clone it?