|
|
|
Developers do not need Kubernetes (Viktor Farcic, Shipa) Since the emergence of Kubernetes, we hoped that developers will adopt it. That did not happen, and it will likely never happen. Developers do not need Kubernetes. They need to write code, and they need an easy way to build, test, and deploy their applications. It is unrealistic to expect developers to spend years learning Kubernetes. On the other hand, operators and sysadmins need Kubernetes. It gives them all they need to run systems at scale. Nevertheless, operators also need to empower developers to deploy their own applications. They need to enable developers by providing services rather than doing actual deployments. So, we have conflicting needs. Kubernetes is necessary to some and a burden to others. Can we satisfy all? Can we have a system that is based on Kubernetes yet easy to operate? Can we make Kubernetes disappear and become an implementation detail running in the background?
Software License and DevOps (Hubert Bosiacki, Suade Labs) Take deep dive into problem of Software License and how to protect your project from legal actions. Long term sysadmin coming to DevOps world from datacenter.
Kubestr: Identify, Validate and Evaluate your Kubernetes Storage (Michael Cade, Kasten by Veeam) As the adoption of Kubernetes grows, so has the persistent storage offerings that are available to users. The introduction of CSI (Container Storage Interface) has enabled storage providers to develop drivers with ease. There are around 100 different CSI drivers available today. Along with the existing in-tree providers, these options can make choosing the right storage overwhelming. Kubestr is a collection of tools to identify, validate, and evaluate your Kubernetes storage options. Kubestr can assist in the following ways: identify the various storage options present in a cluster, validate if the storage options are configured correctly, and evaluate the storage using common benchmarking tools like FIO.
|