All of the above. I’d like to know why when you delete a CRD, k8s also deletes all child CRs and resources that depend/reference that CRD?
@DevOpsToolkit Жыл бұрын
@@Luther_LuffeighKubernetes does not allow CRs that do not have a registered schema (CRD). So, when you delete a CRD, all CRs are deleted as well. Think of it as CRD being a DB table and CRs being data in that table. Once the table is gone, there is no place for that data so data is gone as well. Now, whether a child CR will be deleted when the parent CR (not CRD) is deleted depends on the relation between the two. For example, if you delete a Deployment, ReplicaSets it manages are deleted as well. That is not necessarily true for all CRs (or KRs). Crossplane, for example, allows you to select a strategy that keeps child resources intact when parents are deleted.
@LuckieLordie Жыл бұрын
At work we run all of our workloads on kubernetes. Our team specifically has developed our own CRDs and Controllers to provision our AWS resources!
@Luther_Luffeigh Жыл бұрын
@@DevOpsToolkit thank you for the explanation, yeah thinking of CRDs as DB tables helps grasping the concept!
@DevOpsToolkit Жыл бұрын
That sounds great@@LuckieLordie
@fenarRH Жыл бұрын
Imho; helm is a good start point for day0 ops , when your appstack gets more complex and you want some of the appstack ops have autonomous abilities on cluster-side you shall invest in crd & operators.
@tyronefrielinghaus346710 ай бұрын
That was VERY GOOD..well explained, and in a clear, unambigous way...anticipating confusion points. And is a really engaging way too. Subscribed now!
@MuthaNagavamsi11 ай бұрын
Just wow. You are such a great teacher. Thank you for this wonderful video. I now understand a bit about CRDs. I will dig deep and explore more.
@IvanRizzante Жыл бұрын
Thanks for another great explaination video! We use Kubernetes to deploy our applications throughout their journey from development to production, in our case not using operators/CRDs for the application itself but for infrastructure using Crossplane
@ashseth7885 Жыл бұрын
Very useful video. Please make video soon with an example to use crd, controller etc. I want to really thank you for all the videos. It had really helped me learning kubernetes.
@MarkTellier11 ай бұрын
Thank you for this excellent explanation Victor!
@franssjostrom719 Жыл бұрын
I am starting my career as an operations engineer with Kubernetes clusters, your videos are the torch that is guiding me through the Kubernetes jungle 🦋🦁 Would love to see a breakdown of your monitoring stack 🎉
@DevOpsToolkit Жыл бұрын
We'll go through the whole CNCF observability stack in "You Choose!" (kzbin.info/aero/PLyicRj904Z9-FzCPvGpVHgRQVYJpVmx3Z). The next chapter is about security and the one after that is about observability. In the mean time, while preparing for that, I'll probably release a few videos around that area. The bad news is that all that will likely start no earlier than January 2024.
@franssjostrom719 Жыл бұрын
@@DevOpsToolkit Take your time! Your videos are gold, do not want you to burn out. Looking forward to see both the security and observability videos :)
@taoaleixandre20892 ай бұрын
im grateful for the video. Very interesting
@walk_with_anshuman10 ай бұрын
You rock!! Thanks for putting out quality stuff!!
@VladimirVyazmin Жыл бұрын
Respect and reverence (in Russian uvazuha) to you for this informative video!
@rodoherty1 Жыл бұрын
Fantastic explanation, Victor!
@selfimprovements2398Ай бұрын
Thanks for explaining. I have doubt regarding how to convert existing helm chart to crds and deploy it using go based operator SDK
@DevOpsToolkitАй бұрын
I tend to use Crossplane to create CRDs abd controllers but you can do that with many others as well.
@MrGenbu10 ай бұрын
genius with your explanation as always
@gauravpande7746 Жыл бұрын
So based on your explanation of this video next thing is how do we create These CRD's , operators etc... ? Where should we start with?
@DevOpsToolkit Жыл бұрын
You can write them from scratch. That's great for vendors, but not necessarily for end users. Whenever possible, i prefer simpler approach with Crossplane, KubeVela, Metacontroller, etc. Those tools might not say explicitly that they are creating CRDs and controllers, but that's what they really do. P.S. I am heavily vested in crossplane, but I'm trying to be objective on this channel. I often use crossplane in examples, but there are many others you can use.
@gauravpande7746 Жыл бұрын
@@DevOpsToolkit okay so how to write them from scratch?
@DevOpsToolkit Жыл бұрын
@gauravpande7746 kubernetes.io/docs/concepts/extend-kubernetes/operator/ is probably a good starting point.
@denisbaryshev-ho8ub Жыл бұрын
Brliant and very motivating to work in a kubernetes native way. Thank you! I really admire how Victor is able to explain difficult things the way that they look very simple. Are they these indeed difficult things, aren't they;) @DevOpsToolkit Victor, you've already revealed that operators are awesome. I just wonder, maybe you've got plans to show some practice. Personally, I'm interested in how to search and deploy oss operators, maybe using olm operator lifecycle manger and things that are available as oss. Could this be a topic?
@DevOpsToolkit Жыл бұрын
Adding it to my TODO list... :)
@denisbaryshev-ho8ub Жыл бұрын
❤
@microst99 Жыл бұрын
dat thumbnail, bruhh 😂
@robertkerr229 Жыл бұрын
Terrific explanation. I don't use Kubernetes yet. Instead have monoliths in traditional infrastructure: vSphere, VMs, AVI. Would like to remodel my IAC (Packer Terraform Ansible InSpec) and potentially manage VMs with Kubernetes.
@davidgold594 Жыл бұрын
Fantastic explanation! Thank you.
@madhurahappy8587 ай бұрын
You made these concepts much easier to understand. Thank you!
@martinpetersson6979 Жыл бұрын
please create a video about the new api gateway feature :)
@DevOpsToolkit Жыл бұрын
Something like Gateway API - Ingress And Service Mesh Spec Replacement? kzbin.info/www/bejne/j3LXiYd_aLN-qqs
@rikschaaf Жыл бұрын
Couldn't you technically create helm chart-like CRs with a controller that processes these charts? helm charts are mostly yaml after all.
@DevOpsToolkit Жыл бұрын
You can. A controller can be anything you want it to be. It listens to events related to specific CRs, uses those CRs are input, and does whatever it should do. That can be a conversion of that CR to the Helm values file and then `helm update --install` as long as it has permission to perform those actions against the API.
@zenobikraweznick Жыл бұрын
So... you're saying I don't need docker compose now ? Never !!!
@DevOpsToolkit Жыл бұрын
If you moved your workloads to kubernetes, that was the moment you stopped needing Compose.
@zenobikraweznick Жыл бұрын
@@DevOpsToolkit Hey, I'm just fooling around :)
@DevOpsToolkit Жыл бұрын
It's hard to tell since many do ask that question seriously.