John McBride

Marking this draft until we're abit closer to the November timeline (when EKS support for k8s 1.20 will drop per the issue noted above)

Ready for review now and will target the `1.11.0` release

Force pushed to also remove `sources/models/src/aws-k8s-1.20` and `sources/models/src/vmware-k8s-1.20`. Updated `PUBLISHING-VMWARE.md` to indicate using 1.24 kubernetes

Force pushed to address Ben's comment: Added `aws-k8s-1.20` and `vmware-k8s-1.20` to the "The following variants are no longer supported" section. Will merge with passing tests.

Looks like the panic is coming out of: https://github.com/weaveworks/eksctl/blob/aaa82936e8a1a015bcf1063739e37a2d6dff0a78/pkg/nodebootstrap/bottlerocket.go#L82 and somehow, one of the members here is nil and being de-referenced

Diving into that chunk, I wonder if somehow the `Settings` for the bottlerocket member is empty and not getting filled with any kind of default: https://github.com/weaveworks/eksctl/blob/aaa82936e8a1a015bcf1063739e37a2d6dff0a78/pkg/apis/eksctl.io/v1alpha5/types.go#L1241-L1244

Cc @webern - maybe you have an idea of what's going on here?

Opened an issue in `kube` with investigation, small example, and quickfix: https://github.com/kube-rs/kube/issues/1047

@gthao313 and I have updated the `v0.2.2` tag [to point to the right images](https://github.com/bottlerocket-os/bottlerocket-update-operator/blob/b4f1994c10e8d6df2ffe9b2dd1a497ed6695d00f/yamlgen/deploy/bottlerocket-update-operator.yaml#L384) (sorry for the delay on this! Had to do abit of git surgery to update an...

``` error[B004]: found 2 duplicate entries for crate 'uuid' ┌─ /src/Cargo.lock:299:1 │ 299 │ ╭ uuid 0.8.2 registry+https://github.com/rust-lang/crates.io-index 300 │ │ uuid 1.2.1 registry+https://github.com/rust-lang/crates.io-index │ ╰────────────────────────────────────────────────────────────────^ lock entries │ =...