operator-framework / operator-framework/operator-sdk
Allow external plugins be used with SDK ( plugin phase 2 )
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7.7k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
Feature Request
Describe the problem you need a feature to resolve.
The implementation was introduced in Kubebuilder
- It still missing the samples, docs, and e2e tests on the Kubebuilder side, see: https://github.com/kubernetes-sigs/kubebuilder/issues/2600#issuecomment-1199073677
However, we can also begin to provide the option on the SDK project
Describe the solution you'd like.
SDK CLI allows external plugins. That means we need to address the same changes/implemenation into the cmd/main.go using the KB implementation/imporrt, see: https://github.com/kubernetes-sigs/kubebuilder/pull/2338/files
Contributor guide
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 by reading cmd/main.go and the linked Kubebuilder implementation and pull request to understand how external plugins are handled. Check the SDK CLI entry points, then determine the corresponding samples, documentation, and end-to-end coverage needed; done means the SDK CLI supports external plugins with those supporting materials and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100