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

Context: https://twitter.com/bwplotka/status/1334404169432788992

Help wanted 🤗

We want to have consistent and structured logs to improve the ability to filter and analyse longhorn-manager logs.
Currently the controller uses the global logrus package logger, the task here would be to switch the log calls to the instance logger that was implemented in longhorn/longhorn-manager#661

While doing this also improve the log messages, where possible.
For an example of a successf

currently "option forwardfor" cant't be unset, so there is no way to enable it in the default section and disable it in a particular frontend

https://github.com/google/starlark-go/blob/master/doc/spec.md

It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.

Like in #137 we should provide build context information.

Code like the following is found in many place in our test suite:

    ssn = '*'
    eq_(node2.get_synchronous_standby_names_local(), ssn)
    eq_(node2.get_synchronous_standby_names(), ssn)

Could be simplified to something like this instead:

    node2.check_synchronous_standby_names("*")

See citusdata/pg_auto_failover#521