filmov
tv
Binding to Low Ports as a Non-root User with Docker and Kubernetes
![preview_player](https://i.ytimg.com/vi/QZhhoboJuds/maxresdefault.jpg)
Показать описание
A low port is anything less than 1024. We'll cover 3 different ways to solve this problem.
Hit the subscribe button to receive more videos like this!
REFERENCE LINKS
---------------------------------------------------
COURSES
---------------------------------------------------
Courses I've created that focus on web dev and deployment topics.
THE TOOLS I USE / GEAR
---------------------------------------------------
FOLLOW ME ELSEWHERE
---------------------------------------------------
TIMESTAMPS
---------------------------------------------------
0:00 -- Intro
0:35 -- What is a low port?
1:57 -- At least 3 ways to solve this
2:40 -- Are low ports more secure?
3:57 -- Why do we have low and high ports?
6:25 -- Solution 1: Use a high port
8:34 -- Solution 2: Tweaking a Linux kernel param
10:00 -- Docker 20.10+ sets this by default
12:13 -- With K8s 1.24+ you need to tweak it
15:33 -- Solution 3: Linux capabilities
18:21 -- Demoing the issue in Kubernetes
22:30 -- Solving it with solution 2
24:28 -- What led me down this rabbit hole?
Hit the subscribe button to receive more videos like this!
REFERENCE LINKS
---------------------------------------------------
COURSES
---------------------------------------------------
Courses I've created that focus on web dev and deployment topics.
THE TOOLS I USE / GEAR
---------------------------------------------------
FOLLOW ME ELSEWHERE
---------------------------------------------------
TIMESTAMPS
---------------------------------------------------
0:00 -- Intro
0:35 -- What is a low port?
1:57 -- At least 3 ways to solve this
2:40 -- Are low ports more secure?
3:57 -- Why do we have low and high ports?
6:25 -- Solution 1: Use a high port
8:34 -- Solution 2: Tweaking a Linux kernel param
10:00 -- Docker 20.10+ sets this by default
12:13 -- With K8s 1.24+ you need to tweak it
15:33 -- Solution 3: Linux capabilities
18:21 -- Demoing the issue in Kubernetes
22:30 -- Solving it with solution 2
24:28 -- What led me down this rabbit hole?