Andrei Neagoe

You'll want to cross-reference the following between 2.4.5 operator and the newer one: ``` I0204 13:30:43.220952 10 submission.go:65] spark-submit arguments: [/opt/spark/bin/spark-submit --class my.package.my.classApp --master k8s://https://10.96.0.1:443 --deploy-mode cluster --conf spark.kubernetes.namespace=ns --conf...

Observing the same:  It would be great to have this addressed with a higher priority... The moment we stopped kubed/kube-config-syncer, everything returned to normal. Deployed via helm using chart...

I was able to somewhat mitigate the problem by restricting the source namespace scope via `config.configSourceNamespace`. But depending on one's use-case, it's really just a workaround.

I'm not sure what's the best way to approach this and I'm not very familiar with keepalived. However, the difficulty seems to be in how to manage/mount the keepalived configmap...

I'm already looking at options. Regardless of the bootstrap mechanism, if one goes through maintenance and does a rolling reboot of nodes, you'd end up with a situation where all...

Any news on this? We're now blocked in upgrading to latest 1.22 due to this. I can imagine we're not the only ones...

@sairamankumar2 wow, thanks a lot for updating the issue with the PR link and of course for your efforts! Looking forward to seeing this merged.

@sairamankumar2 @liyinan926 it seems there are some issues with the webhook creation and the pod fails to start with chart version `1.1.14` and image `gcr.io/spark-operator/spark-operator:v1beta2-1.3.0-3.1.1`: ``` ++ id -u +...

It looks like there's a different behavior for `sideEffects` and `admissionReviewVersions` in `v1`. Basically, in `v1beta1` they used to have defaults and now they do not. Code needs to be...

Thanks, I see the PR is merged now. However, the chart seems to reference an inexistent image: ``` 34s Warning Failed pod/spark-operator-webhook-cleanup-vjfdw Failed to pull image "gcr.io/spark-operator/spark-operator:v1beta2-1.3.1-3.1.1": rpc error: code...