Open kron4eg opened 1 year ago
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale
We still need documentation for known issues.
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale
From https://github.com/kubermatic/docs/pull/1637, we should fix: 1.1.9, 4.1.1, 4.1.9, 4.2.12, for the upcoming 1.8 release
Those can also be fixed in a patch release (e.g. 1.8.1)
What happened?
Running CIS benchmark results to failures:
How to reproduce the issue?
kubectl apply -f https://raw.githubusercontent.com/aquasecurity/kube-bench/v0.6.14/job-node.yaml
What KubeOne version are you using?
Provide your KubeOneCluster manifest here (if applicable)
What cloud provider are you running on?
AWS
What operating system are you running in your cluster?
Ubuntu 22.04