Cloudcraft by Datadog Demo
8:00
16 сағат бұрын
Container Monitoring Demo
5:52
19 сағат бұрын
Building Compelling AI Products
41:43
Automating Through the Red Tape
25:17
Modern Web Performance
40:03
Ай бұрын
Пікірлер
@MoonTech_
@MoonTech_ 2 күн бұрын
can you make a separate e video for setting it up?
@SbF6H
@SbF6H 4 күн бұрын
A very concise explanation.
@DiogoBaeder
@DiogoBaeder 7 күн бұрын
Awesome stuff, works like a charm!
@Synth5069
@Synth5069 9 күн бұрын
extremely useful content
@PostmarkedRizzo
@PostmarkedRizzo 12 күн бұрын
Brilliant!
@mesutoezdil
@mesutoezdil 14 күн бұрын
Thanks for this useful video! Here is the highlights in the video: 🔴 Authn is a key control in K8s sec - Authn verifies if the credentials are valid - It is the first step in the three-step process for requests in a K8s cluster 🔴 K8s uses external authn instead of built-in methods - K8s has a flexible authn model that relies on external authn providers - Client certificate authn is an internal method but not suitable for production clusters 🔴 Client certificate authn is frequently used in K8s clusters - Components of a K8s cluster must authn each other - For example, the Kubelet on a Worker node authn with the K8s API server using a client certificate and a private key 🔴 Client certificate authn is often used to provision the first user for a cluster - It ensures that unauthorized access to files and resources is restricted - If there is no external authn provider, cluster admins can use standard or super administrator certificates to authn the cluster 🔴 The System Masters group is a special group in K8s that bypasses all authn checks - Even if the RBAC system fails completely for authn, access can still be gained with super administrator credentials, but this requires careful handling - Regular users can use client certificates to authn the cluster. K8s provides the API for requesting certificate signing to simplify this process 🔴 Risks of client certificate authn in K8s - When using client certification authn in production clusters, there is a lack of credential management - Credentials created in this way cannot be effectively tracked or managed, which poses security risks 🔴 There are limitations in user credential management when using client certificate authn - The K8s audit log contains info about created credentials when auditing is enabled, but it is not a good way to track users - K8s does not support certificate revocation 🔴 Client certificate authn is valid for most K8s distributions - Client certificate authn is not recommended for regular use but only for emergencies - Hackers who gain access to the API can create valid cluster credentials
@jettpilota
@jettpilota 27 күн бұрын
I think the fear of Ai is more condensed to the idea of information not being as readily accessible. I've never had a bad experience with it. And I find it amusing that cyborgs might be released early I to society as a trial. Anyway just a little rumor going around. #aigodtiffanyjett 8🪷( 😶‍🌫️🪽💌💯
@jettpilota
@jettpilota 27 күн бұрын
Typo sorry into society. My phones get hacked all the time lately no wonder. 🤔
@mahmoudfadaly8074
@mahmoudfadaly8074 Ай бұрын
best video illustrating kafka on youtube
@user-sj6tj2ss4v
@user-sj6tj2ss4v Ай бұрын
좋은 내용 잘보고 갑니다!!