21–30 of 176 posts
Does anyone make anything that just takes your docker compose file and run it really easily with a lot more features? I’m happy with compose. It works. I know swarm was supposed to solve this but is dead now (?).
Does anyone make anything that just takes your docker compose file and run it really easily with a lot more features? I’m happy with compose. It works. I know swarm was supposed to solve this but is dead now (?).
I think Kubernetes will be a part of things (as Docker still is) but it'll be the next level of abstraction -- the thing that turns Kubernetes into Heroku. There's been a few popping up recently, time will tell who wins
For the next 10 years, I don’t see kubernetes going away but rather evolving into something that’s dead simple for anyone to setup and use easily. It’s flexibility in being a platform capable of easily running whatever you want to is somewhat unmatched.
Honestly the only way I see k8s being replaced is by a fork if there is some Governance dispute. I don’t see the platform changing for at least 10-20 years.
I know there are great terraform modules out there already, but i wonder if many of Hashicorp's products soon will be available as "managed" services as well, allowing people to try something new with less maintenance cost.
An abstract layer to automate the creation of k8s which is an abstract layer to automate application deployment and application management What we need is an abstract layer to automate the systems underneath so we can leverage that abstraction and create more complexity There are still some folks who understand the abstraction all the way up and down. We cant have that
I don't really see any value in automation of creating k8s clusters. From my point of view 80-90% of software people doesn't need k8s really. There is strong trend to have "low code-no code" at some point we want abstraction of CI/CD and having small apps that can be built by specialists without need for developers. With k8s managed by cloud vendors we are in the middle of "no infra", cloud vendors will be managing k…
An abstract layer to automate the creation of k8s which is an abstract layer to automate application deployment and application management What we need is an abstract layer to automate the systems underneath so we can leverage that abstraction and create more complexity There are still some folks who understand the abstraction all the way up and down. We cant have that
The big win of kubernetes is not that it lets you get access to computational resources easier (yaml rather than systemd scripts) but that it is a temporary escape on the "file a ticket to get new compute resources" (temporary because just like picking up hardware for the data center goes from just buy it to get it approved; VM creation goes from just click a button to what's your cost center and VP signoff; new namespace creation hasn't had time to get put into service now, but it will be). Like Docker let developers bypass restrictive OS imaging, k8s lets developers spin up more resources with less constraint. It's not really about the technical abstractions, running a go binary on bare metal is not different (only faster) than running it in a k8s cluster except I have no way to get permission to run it on bare metal.
And my skills are shifting from "maximizing the product value delivered by this heap of hardware" to "minimizing the cost of the MVP in this cloud billing environment." Before if we had unused compute, we'd stick a cache in or precompute something that will reduce latency for customers down the line. Now, we are like, don't do that computation, it mightn't be needed.
if the lesson from k8s is that after containers we needed container orchestration - the business logic analog is that services will need service orchestration.
(disclaimer: i work here so i'm both biased and have skin in the game)
And perhaps geographical regulations will become so demanding that you need something like durable objects to store & process data in country of origin.