add required fields on kubernetes manifest generation
Open
Nobody has claimed this yet.
kind/bug
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
on community operator release, we generate manifests from https://github.com/tektoncd/operator/tree/v0.70.0/operatorhub/kubernetes
The following fields are mandatory, but those fields are missing on manifests/tektoncd-operator.clusterserviceversion.yaml
metadata.annotations.containerImage- operator imagespec.minKubeVersion- minimal kubernetes supported version
Add support for these fields
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 in operatorhub/kubernetes and inspect how manifests/tektoncd-operator.clusterserviceversion.yaml is generated. Add support for the operator image in metadata.annotations.containerImage and the minimum Kubernetes version in spec.minKubeVersion, then verify the generated manifest contains both required fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 42/100