Jordan Liggitt
Jordan Liggitt
xref https://github.com/kubernetes/kubernetes/issues/103151 I agree with this scoped starting point. A confirmed bug that is marked important/critical should not be autoclosed.
I could actually see the stale/rotten labels being useful/interesting to indicate inactivity/neglect, but not auto-closing
for reference, here's a query of the closed `lifecycle/rotten` bugs with important or critical priority: https://github.com/kubernetes/kubernetes/issues?q=is%3Aissue+is%3Aclosed+label%3Alifecycle%2Frotten+label%3Akind%2Fbug+label%3Apriority%2Fimportant-longterm%2Cpriority%2Fimportant-soon%2Cpriority%2Fcritical-urgent+
that command is new in kubectl 1.6.0
I wouldn't recommend getting in the habit of using `-k` in actual checked-in manifests... skipping TLS verification at the same time you're sending a bearer token opens you to MITM...
https://github.com/kubernetes/kubernetes/pull/105030 is now merged and this is on the short-list of things in k/k that still use json-iterator
it looks like this uses really specialized serializing capabilities provided by json-iterator... not sure swapping will be easy
/reopen /lifecycle frozen