You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2022. It is now read-only.
This repository is currently being migrated. It's locked while the migration is in progress.
@jonathanhatch Currently helm3 is not supported and as @muhlba91 pointed out #100 will address this. Unfortunately as helm3 charts are not backwards compatible with helm2 we are still discussing how to handle this.
Yeah, that kind of defeats the purpose of using Helm as a package manager. It's problematic for me because the manual installation of StorageOS doesn't work. I just stood up a containerd cluster with two nodes to test manual installation and the final CRD trigger isn't triggering any kind of installation.
A two node installation will not work if you are using embedded etcd as etcd cannot establish quorum between two nodes. Can you try and use a node selector to limit the installation to a single node, add a third node, or use external etcd?
It may also be helpful if you can show the output of a kubectl describe StorageOSCluster
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
helm install storageos/storageos-operator --namespace storageos-operator --generate-name
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
manifest_sorter.go:192: info: skipping unknown hook: "crd-install"
Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "StorageOSCluster" in version "storageos.com/v1"
The text was updated successfully, but these errors were encountered: