Block a user
feat: K8sFlavour
That is a clear naming problem. Should be either k3d for real by detecting it another way or k3sFamily just like OpenshiftFamily
feat: K8sFlavour
This is more of a fallback to a default than a true way to detect that we're running vanilla k8s (made by kubeadm for example).
feat: K8sFlavour
Should be OpenshiftFamily(Version) as we want the same behavior between okd and openshift.
feat: Add openbao example, open-source fork of vault
WIP: configure-switch
I think it is fine for now, but that is vendor specific logic. So it should probably be entirely hidden inside the brocade crate's logic.
WIP: configure-switch
speed yes, maybe we will need something else but nothing comes to mind right now.
WIP: configure-switch
fix: added routes to domain name for prometheus, grafana, alertmanageradded argo cd to the reporting after successfull build