Tim Bannister

I agree, tweak the changelog entry accordingly. But it's still good to follow our house style (verbs in past tense, field names inside backticks).

/retitle Support `kubectl config get-contexts` JSON output

See https://github.com/kubernetes/kubernetes/issues/116447#issuecomment-2425150150 for (my) thinking on admission time restrictions to avoid the problem surfacing.

/priority awaiting-more-evidence Sounds great. Can you write out why this is useful @reylejano ?

BTW, I expect that this will be a pain to implement and manage unless k/k provides that source data.

~This is now more feasible as we have the data available.~ I was thinking of feature gates, sorry.

I wonder if some tool, maybe CLI compatible with `aws-nuke`, could borrow from OpenTofu, or Terraform, for details like: - plan file serialization - use of Terraform or OpenTofu plugins...

Being able to write an actual Terraform-compatible plan would allow using tools to visualise plans.

We could add a statement to our code of conduct that we expect people to recuse / abstain when there is a conflict of interest, and that not doing so...

/sig node