Testing Operators Built With The Operator SDK and Deployed Through OLM
Open
Nobody has claimed this yet.
lifecycle/rotten
- Dominant language
- TeX
- Stars
- 7
- Forks
- 79
- Avg merge
- 11h 20m
- Merged PRs (30d)
- 6
Description
https://docs.ci.openshift.org/how-tos/testing-operator-sdk-operators/
The documentation here is no longer recommended by the Operator Framework team because we are moving off of olmv0 to olmv1. The Operator SDK CLI is also in a state that could be considered deprecated and inactive.
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
Start with the linked testing-operator-sdk-operators documentation page and review the current Operator Framework guidance for olmv0, olmv1, and the Operator SDK CLI. The work is done when the page no longer recommends the obsolete workflow and accurately reflects the supported direction.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100