KubeCon is coming to San Diego! We've taken the liberty to invite some speakers who are in town for KubeCon to present at our meetup to talk about the work they're doing. Join us!
1. Mateusz Szostok - The journey from the Aggregated API Server to the CRD
Time: 35 min
Extending Kubernetes quickly has become a common practice. You can do that in two different ways, either using the API aggregation server or the CRD approach. This talk takes you on a Service Catalog journey on the process of moving from the initial API server implementation to the Custom Resource Definition (CRD) and the admission webhook approach. The talk will be given by external users of the Service Catalog who first became contributors to the project and then its active members.
You will learn:
- Why it's worth to move to CRDs in your project.
- What technical implications of the two approaches are.
- How to do a migration from the API server to the CRD approach.
2. Piotr Kopczynski - Complete Service Management in Your K8s Cluster
Time: 10 min
Helm is a great way to install and manage the life cycle of complex Kubernetes applications. Combined with the OSB API specification, it enables really loosely-coupled Service Management in a K8s cluster. Together, Helm and the OSB API specification make a solution called the Helm Broker.
Using that guy, you can automate credentials injection and prepare many helm chart configurations upfront. Additionally, you gain an extra security layer which prevents your instance from being removed when it is still in use by external applications.
3. Pawel Kosiec - Building GraphQL API for Kubernetes Resources
Time: 35 min
Imagine that you want to create a UI for your Kubernetes custom resources. You could use Kubernetes API directly, but in most cases it’s better to write your own service which will implement the custom logic and expose a convenient API for the front-end.
Based on our experience in building such a production-grade solution, you will learn:
- Why we chose GraphQL.
- How we minimized load on the kube-apiserver.
- How we went beyond filtering by labels and created more powerful queries for Kubernetes resources.
- How we secured the GraphQL API.
4. Lukasz Gornicki - Deploy and document at the same time with CRD only
Time: 10 min
Deploying a service to production should not only make a service available but also its documentation. Many companies work on content in a totally different environment. They make a service available immediately but docs follow later, not only because nobody wrote them but also because the tools and processes are separated for your infrastructure. Changing this approach was one of the goals for Kyma project. The plan was to make sure code and content can be deployed at the same time. Sounds crazy? content as code? It is possible by extending Kubernetes with a Custom Resource that enables deployment of a service with its documentation with just one "kubectl apply". Kyma's Headless CMS, built natively on Kubernetes, enables this functionality and makes it possible to treat content as code.