Skip to content
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

Failed to call webhook from API server with AWS EKS 1.19 #1224

Closed
felixng-umh opened this issue Apr 12, 2021 · 6 comments
Closed

Failed to call webhook from API server with AWS EKS 1.19 #1224

felixng-umh opened this issue Apr 12, 2021 · 6 comments

Comments

@felixng-umh
Copy link

Failed to call webhook from API server with AWS EKS 1.19

E0412 13:50:38.660172 1 dispatcher.go:171] failed calling webhook "webhook.sparkoperator.k8s.io": Post "https://spark-operator-webhook.spark-operator.svc:443/webhook?timeout=30s": x509: certificate relies on legacy Common Name field, use SANs or temporarily enable Common Name matching with GODEBUG=x509ignoreCN=0

@puneetloya
Copy link

I see a webhook problem as well, my spark configmap is not getting attached to the driver.

@jdonnelly-apixio
Copy link

I'm getting this as well after upgrading to EKS 1.19.

@jdonnelly-apixio
Copy link

I upgraded to the latest version of the spark operator and the issue was resolved.

@indranilr
Copy link

indranilr commented Nov 1, 2021

not sure if this issue is addressed already , getting the below error with AWS EKS (K8s version 1.19 and Helm v3.6.3, Operator Tag Image v1beta2-1.2.3-3.1.1 and chart version 1.1.8) , all spark applications fail to load volume, config maps,

Please note all configurations work as expected in in-premise K8 deployment.

E1101 09:25:03.552938 1 dispatcher.go:171] failed calling webhook "webhook.sparkoperator.k8s.io": Post "https://myapp-spark-operator-webhook.myapp.svc:443/webhook?timeout=30s": Address is not allowed

The webhook service on describing looks like below :
image

Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Copy link

github-actions bot commented Nov 2, 2024

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants