VMware
Tiffany is a senior developer advocate at VMware and is focused on Kubernetes. She previously worked as a software developer and developer advocate (nerd whisperer) for containers at Amazon. She also formerly worked at Docker and Intel. Prior to that, she graduated from Georgia Tech with a degree in electrical engineering. In her free time she likes to travel and as well as dabble in photography. You can find her on Twitter @tiffanyfayj.
Twitter : @tiffanyfayj
La journée de confs se termine et vous en voulez encore ? Alors on remets le couvert : rejoignez les meetups Docker et Kubernetes pour une soirée commune placée sous le signe des conteneurs ;)
Deux talks vous seront proposés à cette occasion :
1/ Beyond cluster-admin: Getting Started with Kubernetes Users and Permission, par Tiffany Jernigan
2/ Machine learning + GPU + Docker = ♥, par Jérôme Petazzoni
Après ces présentations, nous poursuivrons ensuite la soirée lors du meet & greet partagé avec les autres meetups de la soirée ;)
We've all done it: working on our Kubernetes clusters with "cluster-admin" access, the infamous equivalent of "root". It makes sense when we're just getting started and learning about Pods, Deployments, and Services and we're the only one accessing the clusters anyway; but soon enough, we have entire teams of devs and ops and CI/CD pipelines that require access to our precious clusters and namespaces. Are we going to YOLO and give them our admin certificate, token, or whatever else we use to authenticate? Hopefully not!
In this talk, we're going to look at how to implement users and permissions on a new Kubernetes cluster. First, we'll review various ways to provision users, including certificates and tokens. We'll see examples showing how to provision users in both managed and self-hosted clusters, since the strategies tend to differ significantly. Then, we'll see how to leverage RBAC to give fine-grained permissions to these users.
We'll put emphasis on repeatability, showing each time how to script and/or generate YAML manifests to automate these tasks.
Your mission is to secure the vast tracts of land of the Cloud Native security landscape. Where do you even start?!? It would be preposterous to cover that whole topic in a single session, but we can at least map it out. Our plan is to break it down into three key areas and review each in turn. Platform - securing and upgrading our control planes and nodes; isolating compute, storage, and network resources; managing privileges and secrets. User management and permissions - various ways to authenticate and authorize user access; leveraging tools like RBAC and Namespaces, and some common "gotchas". Software supply chain - what that means; some actual threat models are; how to mitigate them.
You will leave this session with a stronger understanding of the breadth and depth of Cloud Native security and resources to further develop your knowledge.
Adrien BLIND
Jérôme PETAZZONI
Laurent GRANGEAU