Naadir Jeewa

Kubeadm bug here: https://github.com/kubernetes/kubeadm/issues/3003

Discussion in [Slack](https://kubernetes.slack.com/archives/C0EN96KUY/p1706631553215049) suggests that we should provide options rather than change defaults, and encourage people to go to elliptic curve where possible.

If you end up doing something custom because library functions don't do the right thing, it'd be good to have a utility function in one of the externally exposed packages...

Yeah, that's probably best. There's also some very nice quality of life stuff in the CAPA one, especially the goroutines that captures logs on a ticker that you can run...

CPI should really be using a kubetest2 implementation so they can walk the latest recommended builds of everything, like https://github.com/kubernetes-sigs/provider-aws-test-infra/tree/main/kubetest2-ec2

Can confirm the reboot test would catch this

Do we really need to report cached memory? The vritual memory subsystem will reclaim cached pages as memory pressure increases, just as it does in Linux. For comparison, here's my...

I think we want the entire "Private Bytes" reported instead, rather than adding cached. What windows is saying here is that the application was swapped to virtual memory but immediately...

We discussed this in the call of 2023/07/23: * This will need to be marked as a breaking change, as there is a security implication of allowing users to create...