Eyar Zilberman

How do you ensure the stability of your Kubernetes (K8s) clusters? Are you sure you don't have any invalid data types? Are any mandatory fields missing? Specialized tools and a "shift-left" approach make it possible to verify a Kubernetes schema before it’s applied to a cluster.

This talk will go over basic git commands and how GitHub can help you and your teammates collaborate to get a project up and running. We also will review basic workflows for working together and go over some best practices to aid you in your journey!

Over 100 popular Kubernetes CRDs (CustomResourceDefinition) in JSON schema format

Most open source projects are not “taking-off”, although they are really good! This is because developers (which are usually the creators of open source projects) think that writing the code is the hard part and “neglect” the other parts of publishing a good open source project. In this talk, I used my experience as a contributor to open source and product head of a startup, to go beyond writing the code itself and cover the other central aspects of creating an open source project, like MVP, product/market fit, marketing and more.

During this event (entire day), we are meeting with people from the community for 1:1 sessions to help them with different challenges (e.g. how to contribute code for the first time, career advice, GitHub tips, etc.)

With great power comes great responsibility. While GitOps empowers your engineering organization with greater ownership - it can also have the downsides of being dangerous, if not properly managed and configured, as ultimately every engineer can impact production. In this talk, we will go over some best practices when applying GitOps in your engineering organization, and ways to automate the validation of Infrastructure as Code config files, in order to build stability inherently into your GitOps practices.

Github actions are mostly known as Github's CI/CD solution. But actually, they are capable of much more than that. In this talk, we'll explore the world of possibilities enabled by Github Actions by following the journey of an open-source developer, who uses them to solve some common problems, among some unexpected but yet fascinating use cases.

Running schema validation tests is important, and the sooner the better. If all machines (e.g., local developer environments, continuous integration [CI], etc.) have access to your Kubernetes cluster, run kubectl --dry-run in server mode on every code change. If this isn't possible and you want to perform schema validation tests offline, use kubeconform together with a policy-enforcement tool to have optimal validation coverage.