
Kubernetes @Google. Opinions are my own. He / him. #BlackLivesMatter
Sunnyvale, CA
Joined November 2011
- Tweets262
- Following478
- Followers2.8K
- Likes486
Tim Allclair retweeted
Are you struggling with migrating off PSP? Come to this #kubecon talk to learn about the PodSecurityPolicy migration tool from @tallclair & Sam Stoelinga sched.co/182Jx
I've been helping my wife (child psychologist) build a site for mental health children's books recommendations, and I'm proud of the work she's done. If you're a parent or read books with kids, I hope you find it useful!
dranniesbookshelf.com/?ref=t…
I'm really excited that Pod Security Admission is stable in #Kubernetes v1.25. It provides super-simple out-of-the-box pod security, and I'm optimistic that it will raise the bar for baseline Kubernetes hardening.
kubernetes.io/blog/2022/08/2…
I'm looking forward to presenting some strategies for migrating off of Pod Security Policy with @samosx at the next #kubecon
sched.co/182Jx
Something happened to my twitter feed, and it’s now 90% viral content. Anyone else notice this or did I just click on one too many viral tweets?
I recently rewrote the #kubernetes Pod Security migration guide. If you're thinking of moving from PSP to Pod Secruity, check it out!
kubernetes.io/docs/tasks/con…
It was fun talking with @pablokbs about Kubernetes and container security. The interview is in English, if you want to check it out.
En el podcast de hoy, charlo con un ingeniero de Google y grosso en seguridad de Kubernetes. No se la pierdan
youtu.be/g9MAcBZQXjM
PD: El 31/03 hay un evento gratuito donde van a hablar de la deprecación de Dockershim en Kubernetes 1.24! goo.gle/LKL22 anótenseeeee
Tim Allclair retweeted
🤔 Want to learn why Dockershim is being deprecated on Kubernetes 1.24 from industry experts?
Register for the panel "After the storm: Dockershim deprecation demystified" here 👉 goo.gle/35FoESd starting at 9:00 AM PDT on March 31st.
Tim Allclair retweeted
Some notes on a new Linux kernel CVE that dropped last week and could allow for container breakout in Kubernetes environments blog.aquasec.com/cve-2022-01… . Interesting to note that using a seccomp filter (as in default Docker) can help mitigate this issue.
Today is my first day back at Google after a 1.5 year hiatus. I'm excited to be rejoining the GKE team, focusing more on Kubernetes upstream, and branching out from security.
PodSecurity will be enabled by default with #Kubernetes v1.23!
But you don't need to wait for v1.23 to try it out - the webhook version can be installed on an older cluster: git.k8s.io/pod-security-admi…
Please share feedback! More details here: groups.google.com/g/kubernet…
Tim Allclair retweeted
This is exciting: Soon all the major CRI will support privileged ports with no capabilities 😁
github.com/containerd/contai…
Tim Allclair retweeted
The slides from @tallclair and my #KubeCon NA 2021 talk, “PodSecurityPolicy Replacement: Past, Present, and Future”, are now available.
We’re so proud of how the Kubernetes community came together to replace PSP, and grateful to share the story!
kccncna2021.sched.com/event/…
Tim Allclair retweeted
Were you taken by surprise with the deprecation of PSPs? Want to know more about the replacement for them? Go check out @TabbySable and @tallclair's session on them!
sched.co/lV9A
This is a great illustration of the pitfalls of node isolation, and why I advise against it.
This quoted post is unavailable.
If you need strong multi tenant isolation, focus on hardening the Pod. I recommend @katacontainers
To learn more about other types off attacks on nodes, check out tim.allclair.org/talks/20191…







