resources on the cluster not fully managed by installersets
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
In the cluster all the pipeline resources are managed by installersets. however few of the resources are not fully managed.
Example:
Update a ConfigMap data via kubectl command, which is managed by installerset.
But the changes are not reverted by installerset.
Two things needs to be fixed:
- always compute hash value from deployed(in cluster) resources [1]
- add informers to installersets for configMap and other resources, if required. [2]
[1] - https://github.com/tektoncd/operator/blob/a9aac2d8fd408d1cba6fa125d403475257698b83/pkg/reconciler/kubernetes/tektoninstallerset/install.go#L144-L150
[2] - https://github.com/tektoncd/operator/blob/a9aac2d8fd408d1cba6fa125d403475257698b83/pkg/reconciler/kubernetes/tektoninstallerset/controller.go#L64-L85
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 pkg/reconciler/kubernetes/tektoninstallerset/install.go around lines 144-150 and controller.go around lines 64-85. Trace how deployed resource hashes are computed and how ConfigMap and other resources are watched. Done means installer-managed resources changed with kubectl are detected and reconciled back to the installer state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100