What would you like to be added:
Support for deploying vSphere storage Container Storage Interface (CSI).
It' GA already.

https://github.com/kubernetes-sigs/vsphere-csi-driver
https://cloud-provider-vsphere.sigs.k8s.io/

It requires vSphere 6.7u3+

Why is this needed:

• The in-tree cloud provider for vSphere is deprecated.
• The CSI is the standard way to implement the Storage

Why do you want this feature?
I want to be able to use eksctl to set labels on clusters/nodegroups that were not created by eksctl

What feature/behavior/change do you want?
eksctl set/unset label support for non-eksctl created clusters/nodegroup

Related issue weaveworks/eksctl#2174 (comment)

Task

Convert CI to GitHub Actions

Context

Travis is removing its free tier for OSS projects, so this should be built with GitHub Actions instead, which is not going to add additional cost.

I would expect this to be one of the easier projects to convert given that Docker isn't used in the build.

See also:

https://github.com/mvdan/github-actions-golang
https://github.com/ac

Describe the solution you'd like
It would be neat to see the start time of plugins when looking at sonobuoy status. For example, when E2E are running, they may take a while, but when did they start?

$ sonobuoy status                                                                                                            
PLUGIN		STATUS		COUNT
e2e		running		1
systemd_logs	comple

We use kind for integration tests against a kubernetes cluster. We now have a dirty hack to load the built images into the kind docker daemon since when we started using it kind was at a very early stage and didn't have the load command. Now the load command is available so we can just replace the hack with it!

Docs here
https://kind.sigs.k8s.io/docs/user/quick-start/#loading-an-image-into-y

Users that download the windows EXE will be prompted (by browser and OS) that it is not safe because the EXE isn't signed.

There is a GitHub Action for signing: https://github.com/marketplace/actions/code-sign-a-file-with-pfx-certificate

This would provide additional confidence for

What is schema.yaml? The configuration reference!

schema.yaml is a JSONSchema specification of the values that the Helm chart accepts, we currently use it to generate documentation as can be seen in Configuration reference se