-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
spark-operator v2.0.2 - listen tcp :443: bind: permission denied #2331
Comments
@karanalang Please use a non-privileged webhook port (default to 9443) if possible, or you will need to run as root or modify the security context for that we have removed all the capabilities to enhance the container security. |
Worth noting I think you want |
Hi @jacobsalway, -
However - i see one more issue .. I'm running my spark jobs in namespace (spark-apps), Spark Operator is not recognizing the jobs running on ns - spark-apps, instead it seems to be monitoring namesapce - default here is the log of spark controller :
How to fix this ? |
Hi @ChenYi015 - would running the webhook on non-privileged port on production have any security impact ? btw, it does work if i set the webhook port to 9443 or 8443 Also, pls check my response to @jacobsalway .. i'm facing another issue wrt spark-operator not recognizing jobs in namespace spark-apps |
Pls note - the sparkJobNamespaces was working v2.0.0 .. @jacobsalway - per your comment in slack, how to get the helm chart version for v2.0.0 .. ideally, IMO - we should not have the helm chart & the image versions tied together |
|
thanks, @jacobsalway .. let me check this |
What happened?
I'm trying to install spark-operator on k8s (v1.28), and running in to issues 👍
Command -
spark-controller pod is started but webhook pod is failing -
Logs from webhook pod -
Pls note - I'd installed v2.0.0-rc.0, it was working fine .. however. running into issues with v2.0.2
Pls help with this.
thanks!
Reproduction Code
No response
Expected behavior
No response
Actual behavior
No response
Environment & Versions
Additional context
No response
Impacted by this bug?
Give it a 👍 We prioritize the issues with most 👍
The text was updated successfully, but these errors were encountered: