Closed deorbit closed 5 years ago
thanks for reporting this issue! it's a real bug. i tested it locally and discovered the problem:
we recently updated the version of Gloo (envoy config server) that sqoop is using without updating the version of Envoy itself.
the quick fix for this is to update the sqoop
deployment. the image for the envoy
container should be quay.io/solo-io/gloo-envoy-wrapper:0.13.25
.
you can quickly update this with the command
kubectl set image -n gloo-system deployment/sqoop envoy=quay.io/solo-io/gloo-envoy-wrapper:0.13.25
however we will definitely need to update our helm chart with the fix. thanks for reporting!
Following the steps at https://sqoop.solo.io/getting_started/ on a fresh minikube cluster, the query
gives the following error
Envoy logs (
kubectl logs -n gloo-system sqoop-cdf94f envoy
) reveal the following error repeated many times per second: