I think this video is great. There should be more content like this on youtube. Its really hard to evaluate what to learn and what to use if all you see is people drinking the kool aid :D
Maybe this is unconnected, but do you have any experience with Hashicorp Nomad? From time to time questions arise for us if we need K8s always or if there are easier solutions out there that work well enough up to a certain scale. K3s would of course also be an option in that context. I played around with it and I think I´ve got my opinion, but would be interesting to hear a second one. :)
I used Nomad long time ago and never went sufficiently deep into it to judge it. From my perspective, investment into learning Nomad is a waste. It is almost certain that it has no future. It does not matter whether it is good or bad because Kubernetes took over. Almost all the innovation happening in the industry is built on top of Kubernetes. It is like a black hole that swallows everything and trying to get out of its gravitational pull is close to impossible. Now, if you're looking for something easier, the solution is not to move away from Kubernetes, but to adopt a layer on top of Kubernetes that will provide that simplification. Google Cloud Run is simple. Devtron simplifies some things. Azure Container Apps are also simple (video coming tomorrow). And so on and so forth. What I'm trying to say is that Kubernetes is the base for (almost) everything we do today and if simplicity is the goal, it can be found in services running on top of Kubernetes rather than on something completely different (e.g., Nomad).
@@DevOpsToolkit Thanks Viktor, that kind of sums up my impression, too. It´s also claimed that it´s somehow easier to use and maintain, but I think workload orchestration just carries a bit of inherent complexity - and also Nomad has that. The only big difference then would be the 'we´ve only got 1 binary'-claim, which could also be solved by using K3s. 👍
@@sticksen You mentioning k3s kind of proves the point that Kubernetes is advancing with the speed that Nomad cannot match. Even if there is a use-case for which Nomad is a better choice today, that will likely change tomorrow though the k8s-ecosystem evolving and new projects coming in every day.
I stopped following it a while ago. Right now, I'm much more interested in using kubernetes to manage resources no matter whether they are in or out of kubernetes itself.
You can, but not through the `kubernetes` provider (at least not a few weeks ago when I used it the last time). You'd need to use a custom provider for that. The `kubernetes` provider does not have an option to use your own manifests.
![[Gegagedigedagedago] NEW Help Gegagedigedagedago Nugget escape from Nikocado Avocado Challenge](http://i.ytimg.com/vi/hJWnwRC2Fz8/mqdefault.jpg)
I think this video is great. There should be more content like this on youtube. Its really hard to evaluate what to learn and what to use if all you see is people drinking the kool aid :D
Since this video is 2+ years old, can you please make another video highlighting some if the improvements that might have been introduced
I haven't used it much since then so I'm not up to date with it any more. I'll do my best to dive into it again.
Maybe this is unconnected, but do you have any experience with Hashicorp Nomad? From time to time questions arise for us if we need K8s always or if there are easier solutions out there that work well enough up to a certain scale. K3s would of course also be an option in that context. I played around with it and I think I´ve got my opinion, but would be interesting to hear a second one. :)
I used Nomad long time ago and never went sufficiently deep into it to judge it. From my perspective, investment into learning Nomad is a waste. It is almost certain that it has no future. It does not matter whether it is good or bad because Kubernetes took over. Almost all the innovation happening in the industry is built on top of Kubernetes. It is like a black hole that swallows everything and trying to get out of its gravitational pull is close to impossible.
Now, if you're looking for something easier, the solution is not to move away from Kubernetes, but to adopt a layer on top of Kubernetes that will provide that simplification. Google Cloud Run is simple. Devtron simplifies some things. Azure Container Apps are also simple (video coming tomorrow). And so on and so forth.
What I'm trying to say is that Kubernetes is the base for (almost) everything we do today and if simplicity is the goal, it can be found in services running on top of Kubernetes rather than on something completely different (e.g., Nomad).
@@DevOpsToolkit Thanks Viktor, that kind of sums up my impression, too. It´s also claimed that it´s somehow easier to use and maintain, but I think workload orchestration just carries a bit of inherent complexity - and also Nomad has that. The only big difference then would be the 'we´ve only got 1 binary'-claim, which could also be solved by using K3s. 👍
@@sticksen You mentioning k3s kind of proves the point that Kubernetes is advancing with the speed that Nomad cannot match. Even if there is a use-case for which Nomad is a better choice today, that will likely change tomorrow though the k8s-ecosystem evolving and new projects coming in every day.
What is your conclusion today, two years after the launch of the waypoint?
I stopped following it a while ago. Right now, I'm much more interested in using kubernetes to manage resources no matter whether they are in or out of kubernetes itself.
i mot impressed as well, you're not the only one ;)
You can deploy ingress and all that in the waypoint manifest I thought?
You can, but not through the `kubernetes` provider (at least not a few weeks ago when I used it the last time). You'd need to use a custom provider for that. The `kubernetes` provider does not have an option to use your own manifests.