You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
+ [[ -z root:x:0:0:root:/root:/bin/bash ]]
+ exec /usr/bin/tini -s -- /usr/bin/spark-operator controller start --zap-log-level=info --namespaces=default --controller-threads=10 --enable-ui-service=true --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-controller-lock --leader-election-lock-namespace=so350 --workqueue-ratelimiter-bucket-qps=50 --workqueue-ratelimiter-bucket-size=500 --workqueue-ratelimiter-max-delay=6h
Error: unknown flag: --workqueue-ratelimiter-bucket-qps
Usage:
spark-operator controller start [flags]
Flags:
--cache-sync-timeout duration Informer cache sync timeout. (default 30s)
--controller-threads int Number of worker threads used by the SparkApplication controller. (default 10)
--enable-batch-scheduler Enable batch schedulers.
--enable-http2 If set, HTTP/2 will be enabled for the metrics and webhook servers
--enable-metrics Enable metrics.
--enable-ui-service Enable Spark Web UI service. (default true)
--health-probe-bind-address string The address the probe endpoint binds to. (default ":8081")
-h, --help help for start
--ingress-class-name string Set ingressClassName for ingress resources created.
--ingress-url-format string Ingress URL format.
--kubeconfig string Paths to a kubeconfig. Only required if out-of-cluster.
--leader-election Enable leader election for controller manager. Enabling this will ensure there is only one active controller manager.
--leader-election-lease-duration duration Leader election lease duration. (default 15s)
--leader-election-lock-name string Name of the ConfigMap for leader election. (default "spark-operator-lock")
--leader-election-lock-namespace string Namespace in which to create the ConfigMap for leader election. (default "spark-operator")
--leader-election-renew-deadline duration Leader election renew deadline. (default 14s)
--leader-election-retry-period duration Leader election retry period. (default 4s)
--metrics-bind-address string The address the metric endpoint binds to. Use the port :8080. If not set, it will be 0 in order to disable the metrics server (default "0")
--metrics-endpoint string Metrics endpoint. (default "/metrics")
--metrics-job-start-latency-buckets float64Slice Buckets for the job start latency histogram. (default [30.000000,60.000000,90.000000,120.000000,150.000000,180.000000,210.000000,240.000000,270.000000,300.000000])
--metrics-labels strings Labels to be added to the metrics.
--metrics-prefix string Prefix for the metrics.
--namespaces strings The Kubernetes namespace to manage. Will manage custom resource objects of the managed CRD types for the whole cluster if unset.
--secure-metrics If set the metrics endpoint is served securely
--zap-devel Development Mode defaults(encoder=consoleEncoder,logLevel=Debug,stackTraceLevel=Warn). Production Mode defaults(encoder=jsonEncoder,logLevel=Info,stackTraceLevel=Error)
--zap-encoder encoder Zap log encoding (one of 'json' or 'console')
--zap-log-level level Zap Level to configure the verbosity of logging. Can be one of 'debug', 'info', 'error', or any integer value > 0 which corresponds to custom debug levels of increasing verbosity (default )
--zap-stacktrace-level level Zap Level at and above which stacktraces are captured (one of 'info', 'error', 'panic').
--zap-time-encoding time-encoding Zap time encoding (one of 'epoch', 'millis', 'nano', 'iso8601', 'rfc3339' or 'rfc3339nano'). Defaults to 'epoch'.
unknown flag: --workqueue-ratelimiter-bucket-qps
What happened?
I've kubeflow/spark-operator:2.0.0-rc.0 installed on GKE, and it is working fine
When i create a new helm install with the same version, it is giving me error:
Here is the Helm install command :
Error in controller pod logs :
describing the Deployment -
seems version 2.0.2 is being installed, and that has the parameters -
If i remove these manually from the deployment, the controller pod is starting up.
Can you pls take a look, and let me know why this is happenning.
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: