Это видео недоступно.
Сожалеем об этом.
Kelsey, Kubernetes, and GitOps - GitHub Universe 2020
HTML-код
- Опубликовано: 9 дек 2020
- Presented by Kelsey Hightower, Principal Engineer, Google
This session will dive into Kelsey's journey into Kubernetes as a contributor and a member of the cloud native community. This session will also take a look at the current state of managing Kubernetes based infrastructure through collaboration and how GitOps fits into the big picture.
For more from GitHub Universe 2020, visit githubuniverse...
As always, feel free to leave us a comment below and don't forget to subscribe: bit.ly/subgithub
Thanks!
Connect with us.
Facebook:
Twitter: / github
LinkedIn: / github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to github.com
Great presentation. I've been a bit overwhelmed by GitOps but seeing it broken down like this into its core components helps. I've been using the approach of keeping source code and config in the same directory, but I see the value in breaking it apart into separate repos and using the pull model, especially if I have more than one Kubernetes cluster to deploy to.
“If you restarted enough, it will eventually work”! Priceless 😀!
Beautiful intro, it demonstrates perfectly the need for the product you're teaching.
Thank you for sharing. I appreciate what you did, focusing on concepts and principles instead of tools. My everyday challenge at the office is convincing people about that approach.
This is what matured growth does to you.
Kelsey Hightower motivates me.
Such an amazing and clear explanation.
This is just Awesome Presentation!!! Thanks
Nice presentation, thank you
Awesome presentation! Thanks
I find the part where you manually updated the Canary cluster to 2.0.0 a little bit confusing. Shouldn't this update be done via a commit to the config repo, and then the GitHub Actions then automatically do the apply to the cluster? Otherwise, it seems that there's no automation through git. At the end of the day you still manually ran a kubectl apply.
Where are the example repos and how was the cluster provisioned?
Sometimes GitOps is more about the perspective of the developers, not the ops team. So the developers are using pull requests to merge their code changes and merge their image tag and config changes, with a k8s cluster that's already set up for them (already wired up to the Git repos for them). That's why how the cluster was provisioned isn't relevant to this way of doing GitOps. If the devs are responsible for all the ops stuff too, then that matters more.
awesome presentation!
I want to hear more stories
#TIL: Ask How can you make make your team successful.
Nice
Take me, Kelsey.
Ewe hadde Anne Eye ,kemey ke
Kemey me ziarikey
Good bye