Hi Jagdeep Currently, we have a tutorial of running Spark with spark-submit http://yunikorn.apache.org/docs/next/user_guide/workloads/run_spark Since ultimately spark-k8s-operator also runs spark-submit to launch spark jobs, I don't think it requires any extra step. We have a spark app-mgmt plugin that provides deeper integration with spark-k8s-operator, which gives better app lifecycle management by working more closely with spark CRDs. However, this feature is still in the alpha phase, we need some more help from the community to stabilize it before running on production.
Thanks Weiwei On Sun, Oct 25, 2020 at 3:56 PM Sandhu, Jagdeep < [email protected]> wrote: > I need to schedule a job using spark-on-k8s operator. I could not find > any examples on how to accomplish this task using Yunikorn. > > Please help. > > Thanks in advance. > > > > Regards > > Jag > > > > > > *Jagdeep Sandhu* > > Emerging Data Technology > [image: GM Financial] > (w) 1-817.525.7490 > [email protected] > > *Notice to all users The information contained in this email, including > any attachment(s) is confidential and intended solely for the addressee and > may contain privileged, confidential or restricted information. If you are > not the intended recipient or responsible to deliver to the intended > recipient, you are hereby notified that any dissemination, distribution or > copying of this communication is strictly prohibited. If you received this > message in error please notify the originator and then delete. Neither, the > sender or GMF’s network will be liable for direct, indirect or > consequential infection by viruses associated with this email.* > > > > > > ------------------------------ > > Notice to all users The information contained in this email, including any > attachment(s) is confidential and intended solely for the addressee and may > contain privileged, confidential or restricted information. If you are not > the intended recipient or responsible to deliver to the intended recipient, > you are hereby notified that any dissemination, distribution or copying of > this communication is strictly prohibited. If you received this message in > error please notify the originator and then delete. Neither, the sender or > GMF's network will be liable for direct, indirect or consequential > infection by viruses associated with this email. >
