No available release name found for Seldon-Core-Operator

[kenhglee]

Hello!

I remember the helm install command,

helm install seldon-core-operator --namespace kubeflow --repo https://storage.googleapis.com/seldon-charts --set usageMetrics.enabled=true

, seen in https://github.com/SeldonIO/seldon-core/blob/master/examples/kubeflow/kubeflow_seldon_e2e_pipeline.ipynb

used to work well several months ago, but now it gives

"No available release name found" error.

Could there be any pointers?

Here is my kubectl version:
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-07-11T23:29:19Z", GoVersion:"go1.12.7", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12+", GitVersion:"v1.12.10-gke.15", GitCommit:"7b5157a7c600aa8ee6e2b36b56c478e030d5bfe2", GitTreeState:"clean", BuildDate:"2019-10-07T20:39:12Z", GoVersion:"go1.11.13b4", Compiler:"gc", Platform:"linux/amd64"}

And the helm version:
Client: &version.Version{SemVer:"v2.14.1", GitCommit:"5270352a09c7e8b6e8c9593002a73535276507c0", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.1", GitCommit:"5270352a09c7e8b6e8c9593002a73535276507c0", GitTreeState:"clean"}

Thanks!

[ukclivecox]

Could the solution be: https://scriptcrunch.com/helm-error-no-available-release/

[axsaucedo]

Closing due to inactivity

[kenhglee]

I am sorry for being late to come back with the outcome as I was busy doing other tasks. Deleting the tiller-deploy deployment did not really help. But, the following commands did help taken from, helm/helm#3055:

kubectl create serviceaccount --namespace kube-system tiller
kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller
kubectl patch deploy --namespace kube-system tiller-deploy -p '{"spec":{"template":{"spec":{"serviceAccount":"tiller"}}}}'

Thanks!

[ukclivecox]

OK that's useful to know. So the Helm running in the kubeflow namespace needed more permissions?

[kenhglee]

I lack the insight to say yes/no, but it is likely post Helm 2.7 there has been some incompatibility issues with Kubernetes. And in fact, I am still trying to find out which kfctl version I need to download after a crash that we had in our environment though this is out-of-scope from the thread.