kubesphere / kubesphere/ks-devops
Request to upgrade Argo CD due the security issue
Open
Nobody has claimed this yet.
priority/high
security
- Dominant language
- Go
- Stars
- 164
- Forks
- 140
- PR merge metrics
- No merged PRs in 30d
Description
According to this report, wen night need to upgrade Argo CD from v2.3.3 to v2.3.5.
/priority high
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
Locate the repository configuration that pins Argo CD at v2.3.3, then compare it with the referenced argo-helm Chart.yaml and security advisory. Done means the project consistently uses Argo CD v2.3.5 and the relevant configuration or validation passes.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100