Kubernauts! Our next meetup will center around the theme of RBAC in 1.6 and best practices at AWS. It will be May 1, 2017 at Avi Networks in Santa Clara.
RSVPs are required for attending!
Location/Instructions:
Avi Networks
5155 Old Ironsides Dr #100
Santa Clara, CA 95054
Parking at the building is not restricted.
Live Stream: https://www.youtube.com/watch?v=ts-ebTzE4ZI
Agenda:
6:00 - 6:15 - Intro
6:15 - 6:25 - Introduction by Host
6:30 - 7:00 - Scalable and reliable Kubernetes on AWS
AWS provides a feature-rich and battle-hardened infrastructure to run Kubernetes. However, getting the architecture right for running a production grade, reliable and scalable Kubernetes cluster is not straight forward.In this talk, we’ll present our experiences in running Kubernetes on AWS to achieve that. We’ll talk about the problems and limitations we ran into so that you may think about those upfront.
Speaker: Shri Javadekar
Shri Javadekar is a "cloud aficionado" at Applatix where his primary focus is running Kubernetes on AWS. Prior to that he worked on a wide variety of projects at VMware and Dell/EMC which included cloud storage systems, distributed data caching, virtual machine fault tolerance, etc.
Twitter: @shrinandj
7:05 - 7:35 - RBAC Features in 1.6
With Kubernetes 1.6, Role Based Access Control (RBAC) has graduated to Beta, and fills an important role in a secure Kubernetes deployment. In this talk, Tim will introduce authorization in Kubernetes, what RBAC is, and why it is important. He will also cover how to use RBAC, and wrap up with a demo.
Speaker: Tim St. Clair
Tim St. Clair is a software engineer at Google and has been working on Kubernetes Node features and security for the past 2 years. Prior to that he worked on computational photography and full stack engineering for Google Photos. (Note that there are 2 Kubernetes maintainers named Tim St. Clair)
GitHub: @timstclair
7:40 - 8:10 - OpenShift Container Platform: What You Were Going to Build on top of Kubernetes Anyway
While developers like containers, they don't like to build, test, and manage container images. Developers work in term of source code, not images. Producing a container image from source code, pushing the image to a registry, testing the image, and promotion of that image into production should be a standardized and automated process. OpenShift extends Kubernetes to allow for source code level interaction with the platform. And much more!
Speaker: Seth Jennings
Seth Jennings is a software developer at Red Hat working on the upstream Kubernetes and OpenShift projects. Before that he worked on the Linux kernel on projects including kernel hot patching (kpatch) and transparent memory compression (zswap).
Twitter: @sjenninglinux
8:10 - 8:45 - Q&A / Social / Wrap-up
