feat: introduce KubeSAN codepath for shared volume groups

[jakobmoellerdev]

TODO:

• Setup RBAC for KubeSAN
• Setup Driver Registration via internal node registration of vgmanager
• Setup Health Check in vgmanager to use correct driver
• Allow setting up multiple StorageClasses and drivers based on deviceClasses
• Allow configuration of sidecar container for the kubeSAN driver
• Find a easy way to add lvmlockd and sanlock to test clusters before introducing it in OpenShift CoreOS builds - CoreOS layering and a hack script works good enough
• Integrate the controller of kubesan directly into either vgmanager (unoptimized), lvm-operator (more complex) or as a separate deployment
• Create a first demo case
• Run CNV on a cluster with LVMS as base

Optional for POC:

• Find a sophisticated way to add lvmlockd and sanlock to default os builds OR
• Find a way to create dynamic machine configurations that patch kubesan into the OS (not preferred)
• Make Unit & E2E tests run (needs multi attach disk setup for testing)
• Integrate Controllers for performance optimization
• Have a smarter ValidNodes detection that can use smart nodeselectors to create 2 daemonsets, one for shared and one for not shared volume groups
• Refactor the logic paths to not have so much code duplication

Related KubeSAN branch can be found here

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jakobmoellerdev

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jakobmoellerdev]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-merge-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.