Matti Paksula
Matti Paksula
Currently c5.metal instances just crash - there is no way to prevent this without deny support when requesting 96cores which gives metal and non-metal instances https://github.com/aws/amazon-vpc-cni-k8s/issues/1929#issuecomment-1067993183
here's my workaround: https://github.com/matti/k8s-node-watchdog/blob/cd8733d3a82f8b917685c9d906f74595a7bae97b/app/entrypoint.sh#L56-L71 it makes listing nodes much more usable for example in Lens:
yes, but I like to live dangerously and get things done.
no news, rogue pod can still destroy the entire ceph cluster
but bandwidth limit ensures that performance is always limited, eg. always bad. This issue is about Quality of Service where pods would be allowed to burst to maximum while still...
@SD007CSE most definitely! and based on the history it will be available until 2029!
is there some reward on sitespeed issue fixing somewhere? just looking at the history of this issue and it seems so
actually ios limits to something like 10
Also interested