stackabletech / stackabletech/issues
Retire the standalone spark operator
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Acceptance criteria:
- Remove
spark-operatorfrom the documentation repo. - Remove
spark-operatorfromoperator-templating - Remove the operator from the integration test Python script.
- Remove from
docker-imagesrepo - Remove the tests from Jenkins
- Remove the Operator from T2 cluster templates (https://github.com/stackabletech/t2/pull/323)
- (optional?) Remove Helm artifacts
- Archive the
spark-operatorrepo
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the unchecked acceptance criteria across the integration test Python script, docker-images repo, Helm artifacts, and spark-operator repo. Check the already completed removals in the documentation repo, operator-templating, Jenkins tests, and T2 cluster templates for context. Done means resolving the remaining removals and deciding whether the optional Helm cleanup and repository archival are in scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, helm, kubernetes, python
- Domain
- devops, infrastructure, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100