K8s App kind with only ConfigMap can only trigger QUICK_SYNC
Open
Nobody has claimed this yet.
kind/bug
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
What happened:
Kubernetes application with only ConfigMap can only trigger QUICK_SYNC even if we set pipeline in app.pipecd.yaml.
What you expected to happen:
How to reproduce it:
Environment:
pipedversion:control-planeversion:- Others:
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 Kubernetes application handling for a ConfigMap-only app and how the pipeline in app.pipecd.yaml is selected. Reproduce the reported case and compare it with an application containing other resource kinds. Done means the configured pipeline is honored instead of forcing QUICK_SYNC, with the behavior verified for ConfigMap-only applications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100