operator-framework / operator-framework/operator-sdk
Enable testing a bundle from a private registry with operator-sdk scorecard
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.
I'm attempting to run operator-sdk scorecard with a bundle that exists in a private registry and the tooling returns an error indicating it cannot pull the bundle. Logging into the registry with container tools (skopeo, podman) has not helped.
Describe the solution you'd like.
Point operator-sdk scorecard to an image in a private registry and have it successfully run tests.
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 with the operator-sdk scorecard command and the bundle-pull path, then compare its private-registry behavior with the skopeo and podman authentication flow mentioned in the issue. Done means scorecard can receive a bundle image from a private registry and successfully run its tests after registry login.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, devops, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100