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
In the Configure Kubernetes Plugins documentation, it says that when configuring the Spark plugin, we need to create 4 yaml files and apply them manually. These steps are tedious when we try to develop Spark-related features locally.
Goal: What should the final outcome look like, ideally?
Instead of creating 4 yaml files and executing kubectl apply for each of them, create a helm chart for these four files so we can simply execute helm install when we want to develop Spark-related features locally.
Describe alternatives you've considered
N/A
Propose: Link/Inline OR Additional context
No response
Are you sure this issue hasn't been raised already?
Yes
Have you read the Code of Conduct?
Yes
The text was updated successfully, but these errors were encountered:
It's great to see your interest in improving the development experience for Spark-related features. Creating a helm chart for the service account files sounds like a valuable addition. Your contribution would definitely make it easier for developers to work with Spark locally. Thank you for considering this enhancement!
About Dosu
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
If you want to continue the conversation, start your reply with @dosu-bot.
@MortalHappiness Thanks for surfacing this.
I don't think we need another chart for it tho. This week I was able to fold those settings (and found some errors in that page) into the cluster_resource_templates section on flyte-core, and it works.
I'll be sending a PR adding you as reviewer
Motivation: Why do you think this is important?
In the Configure Kubernetes Plugins documentation, it says that when configuring the Spark plugin, we need to create 4 yaml files and apply them manually. These steps are tedious when we try to develop Spark-related features locally.
Goal: What should the final outcome look like, ideally?
Instead of creating 4 yaml files and executing
kubectl apply
for each of them, create a helm chart for these four files so we can simply executehelm install
when we want to develop Spark-related features locally.Describe alternatives you've considered
N/A
Propose: Link/Inline OR Additional context
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: