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
Ask HN: What do you think will come after Kubernetes?
11–20 of 176 posts
Re: Ask HN: What do you think will come after Kubernetes?
#12Frankly I think the serverless model will end up dominating in the long run. Whats really missing there isnt a better abstraction for k8s. Its the dx workflow and local development experience that still requires lots of work. Emulators for services, workflows, good ide integration, open service standard. That will all be where the next layer happens.
Re: Ask HN: What do you think will come after Kubernetes?
#13The pendulum swings back somehow and we'll have offline capable personal computers again.
Re: Ask HN: What do you think will come after Kubernetes?
#14I’m happy with compose. It works. I know swarm was supposed to solve this but is dead now (?).
Re: Ask HN: What do you think will come after Kubernetes?
#15Re: Ask HN: What do you think will come after Kubernetes?
#16One way to do it is you have semi-imperative code that runs, the output of the code is a description of the system to be deployed. Then you have some kind of diffing system that figures out how to take your existing cloud deployment and turn it into the new version described by the output of your code.
This is how Pulumi works for example.
Re: Ask HN: What do you think will come after Kubernetes?
#17An 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
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 k8s clusters but it is not going to be that everyone wants to spin up his own cluster. There is not enough market for higher infra abstraction, there is enough market for level where we are at.
Re: Ask HN: What do you think will come after Kubernetes?
#18For more simple workflows, e.g. a single API endpoint, there's serverless and other SaaS services out there which will let you build off from that, and lets you save a huge amount of time and money compared to building it traditionally with a Web framework.
Now that we've had a few years of experience with how people are actually using the platform , I could see a simplified version of Kubernetes taking hold for businesses still running complex sets of services, something that's easy to install, actually comes with batteries included and is secure by default.
Re: Ask HN: What do you think will come after Kubernetes?
#19The new thing thats going to “emerge” is already here. VMs and Containers were around for about a decade or more before they became really widespread. Frankly I think the serverless model will end up dominating in the long run. Whats really missing there isnt a better abstraction for k8s. Its the dx workflow and local development experience that still requires lots of work. Emulators for services, workflows, good ide…