[OpenShift] disabling addon takes longer time
Open
Nobody has claimed this yet.
kind/bug
lifecycle/frozen
- Dominant language
- Go
- Stars
- 608
- Forks
- 263
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 125
Description
version 1.10.0 (v0.65.x)
Expected Behavior
disabling addon should complete the action in a reasonable time
Actual Behavior
but takes longer time: approx 20 minutes
Steps to Reproduce the Problem
Update TektonConfig cr addon vlaues as follows and watch the addon status and reconcile status
spec:
addon:
params:
- name: clusterTasks
value: false
- name: pipelineTemplates
value: false
- name: communityClusterTasks
value: false
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 reproducing the delay with the TektonConfig CR addon parameters clusterTasks, pipelineTemplates, and communityClusterTasks set to false. Watch the addon status and reconcile status to locate where disabling takes approximately 20 minutes; done means the addon disable action completes in a reasonable time.
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