Open kehao95 opened 3 years ago
Removing the argument -enable-ui-service
from the deployment, results to the same error message but this time for the argument -label-selector-filter=
. After removing both, the older versions of spark-operator start properly.
Not sure but I see helm chart release had operator changes which break deployment for HelmChart Version >= 1.1.1 and image tag= v1beta2-1.2.3-3.1.1
Removing the argument
-enable-ui-service
from the deployment, results to the same error message but this time for the argument-label-selector-filter=
. After removing both, the older versions of spark-operator start properly.
@theofpa How did you remove these arguments?
@sshah90 @port3000 see my coment in #1157
Removing the argument
-enable-ui-service
from the deployment, results to the same error message but this time for the argument-label-selector-filter=
. After removing both, the older versions of spark-operator start properly.@theofpa How did you remove these arguments?
In the container spec of the spark-operator deployment, I just removed the lines:
- -enable-ui-service=true
- -label-selector-filter=
so it now looks like this:
spec:
containers:
- args:
- -v=2
- -logtostderr
- -namespace=
- -ingress-url-format=
- -controller-threads=10
- -resync-interval=30
- -enable-batch-scheduler=false
- -enable-metrics=true
- -metrics-labels=app_type
- -metrics-port=10254
- -metrics-endpoint=/metrics
- -metrics-prefix=
- -enable-resource-quota-enforcement=false
image: gcr.io/spark-operator/spark-operator:v1beta2-1.1.2-2.4.5
...
It seems that
enable-ui-service
was added recently. Which result in passing-enable-ui-service=true/false
onspark-operator
deployment even with old versionspark-operator
who doesn't accept this flag.my case:
Error:
deployment.yaml