-
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
[QUESTION] how do you actually use envFrom
with a secret?
#2134
Comments
@jesumyip Could you provide detailed information about how to install the helm chart? |
You can try out the latest version if you'd like, as this new version has fixed many problems related to webhook. |
Hi @ChenYi015 I have tried the latest version you provided.
And I waited about 1minute but still no pod created in the namespace
|
Is there some permissions that is incorrectly set? But I don't see any errors logged in the 2 pods in the
webhook pod
|
I also tried this values file where I modified the spark job namespaces
I notice in the webhook pod the startup parameter is still shown as
Is this the reason no |
I have just tried to set helm install spark-operator spark-operator/spark-operator \
--version 2.0.0-rc.0 \
--create-namespace \
--namespace spark-operator \
--set 'spark.jobNamespaces={test}' and the webhook pods logs shown that namespaces were correctly set: + exec /usr/bin/tini -s -- /usr/bin/spark-operator webhook start --zap-log-level=info --namespaces=test --webhook-secret-name=spark-operator-webhook-certs --webhook-secret-namespace=spark-operator --webhook-svc-name=spark-operator-webhook-svc --webhook-svc-namespace=spark-operator --webhook-port=9443 --mutating-webhook-name=spark-operator-webhook --validating-webhook-name=spark-operator-webhook --enable-metrics=true --metrics-bind-address=:8080 --metrics-endpoint=/metrics --metrics-prefix= --metrics-labels=app_type --leader-election=true --leader-election-lock-name=spark-operator-webhook-lock --leader-election-lock-namespace=spark-operator |
@jesumyip There is an issue related to cache settings when setting |
looks like the helm chart isn't compatible with kustomize. i used kustomize to install it and the namespace for the
shows this: interestingly enough when i modify the helm chart @ line 54 of
and i set my values file to:
then the output is correct. i actually see
The value of |
@ChenYi015 Now when I try installing it with
I can see the startup parameter for the webhook becomes But when I apply the
Now if I then reinstall the helm chart with
and I have to change the service account in my |
@jesumyip Thanks for reporting the issue, the spark rolebinding template did not render properly when setting |
@ChenYi015 also have a look at that strangeness with |
@ChenYi015 Nevermind. I found out the problem with the |
/kind bug |
I've tried
and when I run a
kubectl describe pod
on the driver, i don't see those env vars being picked up.mysecrets
is an opaque type secret.To test whether the spark operator webhook is working, I tried switching the YAML config to:
and that works just fine.
Am I doing this wrongly? I am using version 1.4.6 of the Helm Chart.
The text was updated successfully, but these errors were encountered: