Bgd 5296 marge latest kubeflow spark operator

.dockerignore

@@ -1 +1,31 @@
-vendor
+.github/
+.idea/
+.vscode/
+bin/
+charts/
+docs/
+config/
+examples/
+hack/
+manifest/
+spark-docker/
+sparkctl/
+test/
+vendor/
+.dockerignore
+.DS_Store
+.gitignore
+.gitlab-ci.yaml
+.golangci.yaml
+.pre-commit-config.yaml
+ADOPTERS.md
+CODE_OF_CONDUCT.md
+codecov.ymal
+CONTRIBUTING.md
+cover.out
+Dockerfile
+LICENSE
+OWNERS
+PROJECT
+README.md
+test.sh

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,46 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: '[BUG] Brief description of the issue'
+labels: bug
+---
+
+## Description
+Please provide a clear and concise description of the issue you are encountering, and a reproduction of your configuration.
+
+If your request is for a new feature, please use the `Feature request` template.
+
+- [ ] ✋ I have searched the open/closed issues and my issue is not listed.
+
+## Reproduction Code [Required]
+
+<!-- REQUIRED -->
+
+Steps to reproduce the behavior:
+
+
+## Expected behavior
+
+<!-- A clear and concise description of what you expected to happen -->
+
+## Actual behavior
+
+<!-- A clear and concise description of what actually happened -->
+
+### Terminal Output Screenshot(s)
+
+<!-- Optional but helpful -->
+
+
+## Environment & Versions
+
+- Spark Operator App version:
+- Helm Chart Version: 
+- Kubernetes Version:
+- Apache Spark version: 
+
+## Additional context
+
+<!-- Add any other context about the problem here -->
+
+

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,32 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: '[FEATURE] Brief description of the feature'
+labels: enhancement
+---
+
+<!--- Please keep this note for the community --->
+
+### Community Note
+
+* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
+* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
+* If you are interested in working on this issue or have submitted a pull request, please leave a comment
+
+<!--- Thank you for keeping this note for the community --->
+
+#### What is the outcome that you are trying to reach?
+
+<!-- A clear and concise description of what the problem is. -->
+
+#### Describe the solution you would like
+
+<!-- A clear and concise description of what you want to happen. -->
+
+#### Describe alternatives you have considered
+
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
+
+#### Additional context
+
+<!-- Add any other context or screenshots about the feature request here. -->

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,20 @@
+---
+name: Question
+about: I have a Question
+title: '[QUESTION] Brief description of the Question'
+labels: question
+---
+
+- [ ] ✋ I have searched the open/closed issues and my issue is not listed.
+
+#### Please describe your question here
+
+<!-- Provide as much information as possible to explain your question -->
+
+#### Provide a link to the example/module related to the question
+
+<!-- Please provide the link to the example related to this question from this repo -->
+
+#### Additional context
+
+<!-- Add any other context or screenshots about the question here -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,38 @@
+### 🛑 Important:
+Please open an issue to discuss significant work before you start. We appreciate your contributions and don't want your efforts to go to waste!
+
+For guidelines on how to contribute, please review the [CONTRIBUTING.md](CONTRIBUTING.md) document.
+
+## Purpose of this PR
+Provide a clear and concise description of the changes. Explain the motivation behind these changes and link to relevant issues or discussions.
+
+**Proposed changes:**
+- <Change 1>
+- <Change 2>
+- <Change 3>
+
+## Change Category
+Indicate the type of change by marking the applicable boxes:
+
+- [ ] Bugfix (non-breaking change which fixes an issue)
+- [ ] Feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that could affect existing functionality)
+- [ ] Documentation update
+
+### Rationale
+
+<!-- Provide reasoning for the changes if not already covered in the description above. -->
+
+
+## Checklist
+Before submitting your PR, please review the following:
+
+- [ ] I have conducted a self-review of my own code.
+- [ ] I have updated documentation accordingly.
+- [ ] I have added tests that prove my changes are effective or that my feature works.
+- [ ] Existing unit tests pass locally with my changes.
+
+### Additional Notes
+
+<!-- Include any additional notes or context that could be helpful for the reviewers here. -->
+