Tim Bannister

I recommend cracking on with early work on a docs update so that these are GA quality (or have PRs open to make them be) by the appropriate review deadline.

Following https://github.com/kubernetes/community/issues/5344#issuecomment-737751369, @makkes I agree and recommend opening an [issue](https://github.com/kubernetes/website/issues/new?labels[]=kind%2Ffeature&template=feature-request.md) in the website repo. (I can or you can).

I'd really like a bot to handle the case where something is mis-triaged as support, and the submitter wants to let us know. Once we have a bot to fix...

I recommend cracking on with early work on a docs update so that these are GA quality (or have PRs open to make them be) by the appropriate review deadline.

> Architecture diagram using AWS simple icons, labelling where user data is stored For my part I'd also be OK with using eg https://github.com/kubernetes/community/tree/master/icons

I'd see this as more of a feature request to add retries. (I don't think we ever documented that `kubectl` would retry in this situation).

This issue is heavily based on https://github.com/kubernetes/kubectl/issues/1301#issuecomment-1276427839

@seans3 FYI

/reopen

/transfer kubectl