I already have gloo running, so I just want to add sqoop. After running sqoobctl install kube -d and saving the yaml file, I extracted just the sqoob parts and kubectl apply that part. The sqoob pod has been created but keeps getting crashloopbackoff.
My kube-fu is too low to understand the error. Is there a separate helm chart just for sqoob without gloo somewhere?
I don't want to reinstall both gloo and sqoob because I have a lot of customized virtual services / upstreams already configured.
Also I am using Kubernetes 1.17 and the kind: Deployment API name has to be updated as well.
I already have gloo running, so I just want to add sqoop. After running sqoobctl install kube -d and saving the yaml file, I extracted just the sqoob parts and kubectl apply that part. The sqoob pod has been created but keeps getting crashloopbackoff.
$ kubectl logs -n gloo-system deploy/sqoop -c sqoop | jq { "level": "info", "ts": "2020-07-08T03:34:11.029Z", "logger": "sqoop.v1.event_loop", "caller": "v1/setup_event_loop.sk.go:51", "msg": "event loop started" } { "level": "fatal", "ts": "2020-07-08T03:34:11.131Z", "logger": "sqoop", "caller": "setuputils/main_setup.go:66", "msg": "error in setup: v1.emitter errors: gloo-system-settings: converting output crd: reading crd spec into v1Settings: unknown field \"discovery\" in v1.Settings", "stacktrace": "github.com/solo-io/sqoop/vendor/github.com/solo-io/gloo/pkg/utils/setuputils.Main\n\t/workspace/gopath/src/github.com/solo-io/sqoop/vendor/github.com/solo-io/gloo/pkg/utils/setuputils/main_setup.go:66\ngithub.com/solo-io/sqoop/pkg/setup.Main\n\t/workspace/gopath/src/github.com/solo-io/sqoop/pkg/setup/setup.go:17\nmain.main\n\t/workspace/gopath/src/github.com/solo-io/sqoop/cmd/main.go:19\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:201" }
My kube-fu is too low to understand the error. Is there a separate helm chart just for sqoob without gloo somewhere? I don't want to reinstall both gloo and sqoob because I have a lot of customized virtual services / upstreams already configured. Also I am using Kubernetes 1.17 and the kind: Deployment API name has to be updated as well.