Quick question: if you use yaml do you also use some kind of templating? My main use cases end up creating some yaml that get applied to a lot of apps with some tweaks.
It's really excellent approach to infra automation solution. I personally love crossplan composition. This encapsulation helps non infra/SRE/devops guys work with simple yamls.
Tbh it isn't the real question for most of the folks whether which tech can get the job done. The MOST IMP of all is which one can get them a job to start with and then explore and learn things along the way.
Title should be: Complexity in! Good luck having a team that creates thoose custom kubernetes operators… and good luck keeping in maintenance after employees leaving
Although I always LOVE your videos and I agree with a lot of things, I can't say I agree with this one for a few reasons: 1. Bringing tools such as Pulumi and Terraform (and Ansible) into this mix, IMO, is a bit misleading; those tools can manage EVERYTHING not just a k8s cluster, so their abstractions are way more generic 2. I haven't used Crossplane, but I'm a bit familiar with it (thanks to your amazing videos), and I love its concept, but unfortunately, I somehow see this video as a sales pitch for Crossplane rather than a fair and unbiosed comparison between different tools 3. Even if we move "complexity" to the server side, someone has to take care of that complexity, and if we want to do that, I personally can argue that we can move the same complexity to Terraform modules or Pulumi classes/objects
Viktor speaking... 1. I am not saying not to use terraform/Pulumi/etc but to use them to create server-side definitions and convert the complexity into CRDs. Also, crossplane is not only for managing k8s. It is for managing anything. 2. I do my best not to be biased. I did think that crossplane is a better choice before I joined upbound. As a matter of choice, I that is the reasons I joined. So, I was biased before I had any commercial interest to be biased. 3. Complexity cannot disappear. The point I'm trying to make is that experts in some field should work on it and create services that others can consume. Heroku is a good example. It is complex, but not for end users. I believe that we should be doing something similar when creating internal services.. P.S. Since I joined upbound, I intentionally publish all crossplane videos on this channel instead of DevOps Toolkit. I hope that helps avoid confusion about my potential bias.
I just commented on your 3yrs old video on the above this 1yr yonger. awesome video and viewpoint.
Thanks for this interesting viewpoint. I now want to see, how Crossplane might fit into my plans. Looking forward to keep track of your postings.
Quick question: if you use yaml do you also use some kind of templating? My main use cases end up creating some yaml that get applied to a lot of apps with some tweaks.
It's really excellent approach to infra automation solution. I personally love crossplan composition. This encapsulation helps non infra/SRE/devops guys work with simple yamls.
Great video!
Tbh it isn't the real question for most of the folks whether which tech can get the job done. The MOST IMP of all is which one can get them a job to start with and then explore and learn things along the way.
Is there any update in this topic?
Title should be: Complexity in!
Good luck having a team that creates thoose custom kubernetes operators… and good luck keeping in maintenance after employees leaving
Although I always LOVE your videos and I agree with a lot of things, I can't say I agree with this one for a few reasons:
1. Bringing tools such as Pulumi and Terraform (and Ansible) into this mix, IMO, is a bit misleading; those tools can manage EVERYTHING not just a k8s cluster, so their abstractions are way more generic
2. I haven't used Crossplane, but I'm a bit familiar with it (thanks to your amazing videos), and I love its concept, but unfortunately, I somehow see this video as a sales pitch for Crossplane rather than a fair and unbiosed comparison between different tools
3. Even if we move "complexity" to the server side, someone has to take care of that complexity, and if we want to do that, I personally can argue that we can move the same complexity to Terraform modules or Pulumi classes/objects
Viktor speaking...
1. I am not saying not to use terraform/Pulumi/etc but to use them to create server-side definitions and convert the complexity into CRDs. Also, crossplane is not only for managing k8s. It is for managing anything.
2. I do my best not to be biased. I did think that crossplane is a better choice before I joined upbound. As a matter of choice, I that is the reasons I joined. So, I was biased before I had any commercial interest to be biased.
3. Complexity cannot disappear. The point I'm trying to make is that experts in some field should work on it and create services that others can consume. Heroku is a good example. It is complex, but not for end users. I believe that we should be doing something similar when creating internal services..
P.S. Since I joined upbound, I intentionally publish all crossplane videos on this channel instead of DevOps Toolkit. I hope that helps avoid confusion about my potential bias.
Very well put Viktor. As I said, I love your videos and I watch every single one of them, but I agree, and the the points you made are complete valid
Not Helm ... Tanka.
It's Pulumi because she BL-EW me 😵😫😩