Tim Smith

Results 258 comments of Tim Smith

This will also need to be reproduced on a 17.x release since we've changed the client this 16.2

The cluster is getting in a bad state. Operator is working as expected

Having this issue occur again. ``` ~/dev  kubectl describe nodes Name: prod-k8s Roles: control-plane Labels: beta.kubernetes.io/arch=arm64 beta.kubernetes.io/os=linux kubernetes.io/arch=arm64 kubernetes.io/hostname=prod-k8s kubernetes.io/os=linux minikube.k8s.io/commit=dd5d320e41b5451cdf3c01891bc4e13d189586ed minikube.k8s.io/name=prod-k8s minikube.k8s.io/primary=true minikube.k8s.io/updated_at=2025_01_29T17_37_03_0700 minikube.k8s.io/version=v1.35.0 node-role.kubernetes.io/control-plane= node.kubernetes.io/exclude-from-external-load-balancers= Annotations: kubeadm.alpha.kubernetes.io/cri-socket:...

Is the long term goal here also to rename that field so we don't cause confusion about impact vs. risk rating?

This will be fixed in 8.1.5

@HRouhani Is there anything worth adding here now that we have the CIS benchmark?

Would we also want mondoo.workspaces?

@preslavgerchev Is this something we'd want to ship in v12?

Sure thing. I'll recreate this

If someone in engineering would like to pick this up feel free. Closing for now due to time constraints.