Skip to content
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.

Error when trying to install with Helm. #102

Open
jonathanhatch opened this issue Mar 18, 2020 · 4 comments
Open

Error when trying to install with Helm. #102

jonathanhatch opened this issue Mar 18, 2020 · 4 comments
Assignees

Comments

@jonathanhatch
Copy link

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"

@muhlba91
Copy link

are you using Helm 3? if so, #100 should address this issue.

@avestuk avestuk self-assigned this Mar 27, 2020
@avestuk
Copy link
Contributor

avestuk commented Mar 27, 2020

@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.

If you have a hard requirement for helm3 then can I suggest you try a manual installation using the StorageOS operator instead? https://docs.storageos.com/docs/install/kubernetes/

@jonathanhatch
Copy link
Author

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.

@avestuk
Copy link
Contributor

avestuk commented Apr 3, 2020

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants