Tobias Dörfler comments

Results 8 comments of


                                            Tobias Dörfler

Run container as a non-privileged user

Is there anything new to this? We definitely want to run this container as nonRoot, especially in combination with Kyverno-Policies in k8s. As @chiqui3d mentioned, it would be a good...

the image has many vulnerabilities scanned by trivy

Is there anything new to this? I saw there is a new helm release `4.0.17` but the image version is still on `v4.0.2`.

k8s_drain "Failed to delete pod" "Too many requests"

I also can confirm this behavior. It would be nice if the kubernetes.core module can support the pod-selector configuration. The usage of the shell module is just a "dirty workaround".

the image has many vulnerabilities scanned by trivy

/remove-lifecycle rotten

No network traffic between pods

Can also confirm with wsl version: ```powershell WSL-Version: 2.0.14.0 Kernelversion: 5.15.133.1-1 WSLg-Version: 1.0.59 MSRDC-Version: 1.2.4677 Direct3D-Version: 1.611.1-81528511 DXCore-Version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows-Version: 10.0.22621.819 ``` and Rancher-Desktop version 1.12.3

Tobias Dörfler

Run container as a non-privileged user

the image has many vulnerabilities scanned by trivy

k8s_drain "Failed to delete pod" "Too many requests"

the image has many vulnerabilities scanned by trivy

No network traffic between pods

Getting HTTP 404, "Manifest Unknown" when pushing an image to Harbor

Harbor UI does not show helm value file and throws error "unknown: gzip: invalid header"

The custom integration midea_ac_lan implements the is_aux_heat