New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WatchConnectionManager:185 - Exec Failure: HTTP 403, Status: 403 - #591
Comments
This issue is also being discussed in the Slack channel. Will get back to this once we have a solution. |
See this thread on Slack: https://kubernetes.slack.com/archives/CALBDHMTL/p1567109649027000?thread_ts=1567027800.012500&cid=CALBDHMTL. |
Looks like there's a workaround by upgrading the version of the fabric8 k8s client used. You can add the following to your Spark Dockerfile:
|
Cool, works for me, I remove
Thanks |
Great to know it works. |
Should it be closed, before upgrading all the defaults from examples and stuff? |
Yes please create new base images to address this issue, thanks. |
I have built and pushed |
@liyinan926 I used the gcr. io/spark operator/spark r: v2.4.0 image, but the problem still exists |
I had deployed the spark operator un a platform with Kubernetes v1.14.5 with GoVersion go1.12.5 all was working well, but by a vulnerability on the go version I did an upgrade to Kubernetes v1.14.6 with GoVersion go1.12.9 without another change in the platform, now the driver return the following error:
Here the event log:
Actually I'm trying to run a basic example spark-pi.yaml to discard another changes of configuration in my yaml files
Can you please help me to resolve it?
The text was updated successfully, but these errors were encountered: