Главная
Study mode:
on
1
Intro
2
Where are we headed?
3
I have a bias!
4
What's GitHub Actions?
5
Why self-hosted?
6
Unique security challenges
7
types of Actions
8
3 types of security concerns
9
2- Do you trust your neighbors?
10
Docker-in-Docker is risky, but...
11
Rootless?
12
Firecracker
13
Runner with Kubernetes jobs
14
3- Right-sizing your runners
15
Controller authorizations
16
Multi-tenant in practice
17
Recommendations
18
Secure runner images
19
Examples to get started!
20
You may have forgotten
21
Logging is easy to overlook
22
Sharing (mounts) isn't caring!
23
Building and deploying
24
Sharing is caring!
25
in)conclusions
26
Questions!
Description:
Explore the intricacies of securing self-hosted GitHub Actions using Kubernetes and Actions-Runner-Controller in this comprehensive conference talk. Delve into the challenges and best practices for integrating these technologies securely, with a focus on regulated environments. Learn about typical deployment architectures and discover three critical areas where security risks intersect with usability. Examine cluster settings to limit potential security breaches, review controller settings for proper runner deployment and permission management, and dissect the runner pod to implement supply chain security. Gain valuable insights on topics such as Docker-in-Docker risks, rootless configurations, multi-tenant practices, and secure runner images. Benefit from practical recommendations, examples, and often-overlooked considerations like logging and mount sharing to enhance your GitHub Actions security posture within a Kubernetes environment.

Securing Self-Hosted GitHub Actions with Kubernetes and Actions-Runner-Controller

CNCF [Cloud Native Computing Foundation]
Add to list