config-registry-cert config map is erased when tekton operator pod restarts
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
Dear team,
In order to be able to pull images from our private registry I need to declare custom SSL certificates in configmap config-registry-cert.
The issue is when tekton-operator pod restarts this configmap resource is deleted (and a fresh one without my certificates is created).
I don't find any solution in tekton operator config to make it persistent.
Do you have a solution for this ?
Thanks a lot for your help,
BR
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 tracing how the Tekton Operator manages the config-registry-cert ConfigMap and reproduce the behavior by adding custom certificates, then restarting the tekton-operator pod. Done means the ConfigMap and its certificates remain available after the operator restarts, or the supported persistence configuration is clearly documented.
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
- Needs clarification
- Newbie friendliness
- 25/100