mysql-operator
mysql-operator copied to clipboard
Published
20 hours ago •
oracle
oracle
mysql-operator failed when installing to kubernetes 1.16.x
Is this a BUG REPORT or FEATURE REQUEST?
BUG REPORT
When installing mysql-operator into Kubernetes 1.16 using helm, (following instructions from https://github.com/oracle/mysql-operator/blob/master/docs/tutorial.md) the installation failed with following error
helm install mysql-operator mysql-operator --debug
install.go:148: [debug] Original chart version: ""
install.go:165: [debug] CHART PATH: C:\Users\abc\code\digitalocean\mysql\mysql-operator\mysql-operator
Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Deployment" in version "apps/v1beta1"
helm.go:76: [debug] unable to recognize "": no matches for kind "Deployment" in version "apps/v1beta1"
unable to build kubernetes objects from release manifest
helm.sh/helm/v3/pkg/action.(*Install).Run
/home/circleci/helm.sh/helm/pkg/action/install.go:231
main.runInstall
/home/circleci/helm.sh/helm/cmd/helm/install.go:209
main.newInstallCmd.func1
/home/circleci/helm.sh/helm/cmd/helm/install.go:115
github.com/spf13/cobra.(*Command).execute
/go/pkg/mod/github.com/spf13/[email protected]/command.go:826
github.com/spf13/cobra.(*Command).ExecuteC
/go/pkg/mod/github.com/spf13/[email protected]/command.go:914
github.com/spf13/cobra.(*Command).Execute
/go/pkg/mod/github.com/spf13/[email protected]/command.go:864
main.main
/home/circleci/helm.sh/helm/cmd/helm/helm.go:75
runtime.main
/usr/local/go/src/runtime/proc.go:203
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1357
Versions
MySQL Operator Version: based on github master branch, commit 9aebcc3 on May 15, 2019
Environment:
-
Kubernetes version (use
kubectl version): 1.16.2 - Cloud provider or hardware configuration: Digital Ocean Managed Kubernetes
- OS (e.g. from /etc/os-release): Windows 10 Professional
-
Kernel (e.g.
uname -a): - Others: Helm 3.0.1
What happened?
Helm install resulted in an error.
What you expected to happen?
Helm install chart into Kubernetes cluster.
How to reproduce it (as minimally and precisely as possible)?
Follow https://github.com/oracle/mysql-operator/blob/master/docs/tutorial.md
Anything else we need to know?
Wondering if this is related to following 2 bugs
https://github.com/helm/helm/issues/7073 and https://github.com/oracle/mysql-operator/issues/304
I have the same problem, so I modified the code, you can refer to this PR #308
