Yinan Li
Yinan Li
Image `gcr.io/spark-operator/spark-operator:v1beta2-1.3.0-3.1.1` that contains the change in the PR has been built and pushed.
One potential solution is to treat `driver.podName` as a prefix that the `ScheduledSparkApplication` controller will use to construct the actual driver pod name, with a suffix that differs it between...
@suryadutta Thanks for the PR. I have not been able to do much for this repo in the past couple of years. We are trying to figure out what to...
I have not been able to allocate enough time to actively maintain this repo, so any help updating the go modules from the community will be highly appreciated. I'm happy...
@orfeas0 could you please bump up the chart version in this PR? Thanks!
Can you resolve the conflict?
Looks like the chart integration test failed with the following message: ``` Error: failed to install CRD crds/sparkoperator.k8s.io_scheduledsparkapplications.yaml: CustomResourceDefinition.apiextensions.k8s.io "scheduledsparkapplications.sparkoperator.k8s.io" is invalid: [spec.versions[0].schema.openAPIV3Schema: Required value: schemas are required, metadata.annotations[api-approved.kubernetes.io]: Required...
That can be an option.
Do you have access to the api server logs?
Typically it's in a path (sorry I don't remember exactly where) in the master node. Depending on the k8s environment, it may or may not be possible to access that.