Tim Bannister
Tim Bannister
How about making it an annotation, not a label? That way, the annotation could store a JSON blob that uniquely identifies the group, kind and name of the node class....
Karpenter always meets at least one Pod security standard (_privileged_) because this is the loosest standard and all Pods that you can define today meet this standard no matter what...
Should karpenter run in `kube-system`? I typically deploy it into a namespace named `karpenter`. :thought_balloon: we could define a namespace for SIG Autoscaling use, to cluster-level components like node autoscaling....
A detail: kops stabilized (1.4 release) at around the same time that guidance originally appeared; it could have been covered as part of the stabilization work, but got missed -...
I'll count this one as accepted, then. /triage accepted
/hold As drafted this mentions changes from v1.31; we shouldn't publish this before v1.31 is released. It's possible we'll agree an exception to the usual policy.
/retitle Add blog article about cgroup v2
/hold cancel
No need to hold for v1.31 but does need a publication date. How about the 1st of October - does that work? /hold
@pacoxu, what's your intention with this PR? There's feedback pending.