Marko is a Software Engineer at Loodse and a Computer Science student. He is an active Kubernetes contributor, currently serving as a Release Manager Associate. Before that, Marko served as a Bug Triage Lead on the 1.16 Release Team and as a Bug Triage shadow on the 1.15 and 1.14 Release Teams. Marko actively works on problems related to the cluster lifecycle. As part of his daily job, he works on tools such as KubeOne, trying to make getting started with Kubernetes and cluster operations easier. In 2018, Marko was a Google Summer of Code student under the CNCF and Kubernetes.
Building and Maintaining Secure and Highly-Available Clusters
Building highly-available (HA) Kubernetes clusters is still a hard task that takes a lot of time. Besides building clusters, you also have to maintain and upgrade them to stay secure and have all the new features.
Kubeadm is a Kubernetes community-supported tool capable of managing the full lifecycle of a cluster; making tasks such as creating or upgrading clusters dramatically simpler.
However, kubeadm has many configuration options.
Finding the right combination is key to configuring a more secure cluster. In this talk, we’ll take a look at how to use kubeadm to create and manage HA clusters. In addition, we’ll demonstrate some configuration options used to create a cluster that is both secure AND passes Kubernetes conformance tests. Finally, we’ll see which options an operator needs to tune in order to use various cloud provider capabilities.
A Five-Minute Tour of the Kubernetes Release Cycle
Understanding the release cadence and support policy of a project is an important step before adopting it in your workflow. Everyone running Kubernetes in production wants to ensure that their clusters are secure and the first step in the journey is making sure your clusters are up-to-date. But when is the next release coming?
In this talk, we’ll take a brief look at the Kubernetes release cycle and how the upstream Kubernetes project models the support policy.