I've found the code in git from this presentation to be helpful but what makes me really happy is finally having an example of EnqueueRequestsFromMapFunc. I wish there were more examples of that. Thanks for putting this together.
Kudos for making the life easier for K8s Operator developers! There seems to be some issue @ 29:58. Actual Invalid Value of servingPort should be -1 in the output while it shows 0
He's not big on diagrams/figures. As a visual learner, I found this hard to follow ... could not grok the relationships between various components ... Code was also hard to grok with all those small fonts.
Wonderfully explained Solly!! Had a doubt though, why is it that a controller is for just one kind? We can go around that by having the reconcile logic in place for CRs that the reconciler "watches", why might that be a faulty approach?
@@filipstojiljkovic4711 , thanks for the reply.. I was just learning writing k8s controllers back then. You are right :) Although you can have a cascade of controllers to take care of different aspects of a custom resource. In such a case the first order controller can watch/own multiple CRs.
I've found the code in git from this presentation to be helpful but what makes me really happy is finally having an example of EnqueueRequestsFromMapFunc. I wish there were more examples of that. Thanks for putting this together.
Thanks for such a great demo. Though i don't have idea on golang currently but now i know where to start for custom operators and controllers.
Kudos for making the life easier for K8s Operator developers!
There seems to be some issue @ 29:58. Actual Invalid Value of servingPort should be -1 in the output while it shows 0
He's not big on diagrams/figures. As a visual learner, I found this hard to follow ... could not grok the relationships between various components ... Code was also hard to grok with all those small fonts.
repo: pres.metamagical.dev/kubecon-us-2019/code --> github.com/directxman12/kubebuilder-workshops
slices: pres.metamagical.dev/kubecon-us-2019/ (swipe left for pages)
@@seriyanto thanks, the importance is "swipe left for pages".
35:46 you've got to be fucking kidding me LOL......
such variety of people.
Thank you for the great presentation.
thanks for the great share.. .just at right time when needed :-)
Thanks a lot! It was amazing.
Wonderfully explained Solly!!
Had a doubt though, why is it that a controller is for just one kind?
We can go around that by having the reconcile logic in place for CRs that the reconciler "watches", why might that be a faulty approach?
Single responsibility principle ?
@@filipstojiljkovic4711 , thanks for the reply.. I was just learning writing k8s controllers back then. You are right :)
Although you can have a cascade of controllers to take care of different aspects of a custom resource. In such a case the first order controller can watch/own multiple CRs.
Thanks
In the video, he used 'kubectl create -f`, but we can use `kubectl apply -f` instead. right ?
yeah you can