Lucas Severo Alves
Lucas is a Software Engineer at Red Hat and one of the developers involved in the Descheduler Framework effort. Lucas is passionate about Open Source and the community around it and is also involved as the maintainer of some other projects in the Cloud Native space. Lucas is also one of the creators of External Secrets Operator and worked as an Sys Admin and later SRE before getting his foot into OSS contribution.
Kubernetes clusters, managed or self hosted, are increasingly dynamic, with their properties changing to accommodate more/less compute power, or to just adhere to new generic requirements. The Kubernetes Scheduler evolved to give more granular options of scheduling decisions to users with specific requirements, however, after a pod is placed, those properties or requirements can change at scale.
Descheduler is a complementary sig-scheduling sponsored component. It provides the ability to evict pods which are no longer satisfying original scheduling decisions, allowing your Kube-Scheduler to reposition them in a more suitable place.
In this talk we are going to give an introduction to this project. What are the current strategies/plugins available for you to customize its behavior and how you can keep the pods in your clusters in the right place all the time, even with dynamic changes to it. In the second half of the talk we are going to show you a demo of it in action and provide you with the means of creating your own descheduling/balancing strategies, tailored to your own needs.
This talk will go over the hard obstacles we face when going through breaking API changes in ESO API. What are the available CRD versioning patterns? What are the tradeoffs we had to take? What are important aspects to consider when designing CRD versioning?
Kubernetes Operators are becoming the de facto way to create applications that need to interact with a Kubernetes Cluster. When it comes to the lifecycle of this operator, inevitably a breaking change in the API version for the CRDs will happen. Attendees will get an overview on how to design, test and deliver long-term maintainable operators.
External Secrets Operator is a community endeavor that emerged from different open source projects that all tried to solve one problem: pull secrets from a secret management API into Kubernetes. We joined our efforts in 2020 to find a common denominator across projects to build the best solution to that problem and even go beyond that.
Today, we've built a vendor-neutral community around the project and provide a consistent custom resource API across different cloud vendors and secret management APIs.