Repository navigation
[Feature] ArgoCD Integration #5207
Description
Search before asking
- I had searched in the issues and found no similar feature requirement.
Use case
Most of our CD are done with Kubernetes ArgoCD and we wanted to add this data connection to DevLake so we could leverage DORA for our deployment frequency.
Description
Add Kubernetes ArgoCD as new data connection to DevLake
Related issues
No response
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
Activity
mintsweet commentedon May 17, 2023
hi @1ddo, thank you for your report.
We have received your information and will consider your needs.
klesh commentedon May 18, 2023
@1ddo Hi, I see you checked the Yes I am willing to submit a PR!, would you like to work on it? If so, we could assign the issue to you and you can start working on it.
1ddo commentedon May 18, 2023
Hi @klesh , I'm currently working on it locally, I'm new to this stuff and I'm having difficulty in making devlake work locally in windows. Was able to run the components in Docker Windows however I'm getting API Down in the config UI (localhost:4000), the tutorial said just wait for a few minutes to let the API up and running but mines seems not working. Do you have any more docs on setting devlake locally using windows or any docs that could help me speed things up?
klesh commentedon May 18, 2023
@1ddo Hi, I'm using Windows too because of Feishu(Good collaborative software but lousy Linux support). Sadly, development in Native Windows is not supported, I am using WSL2, which is practically an Ubuntu Linux environment in conjunction with VSCode Remote WSL plugin, you may take a look, it is a far superior development experience than Native Windows.
1ddo commentedon May 18, 2023
Hi @klesh, thanks for the advice. Will try to set up a WSL2
1ddo commentedon May 18, 2023
Hi @klesh , do you know the reason why I don't have a Project menu in my config-ui:4000? I only see Data Connections, Blue Print, Disabled button for Connection and Dashboard menu options?
abeizn commentedon May 19, 2023
@1ddo It should be that your version is not the latest, you can use v0.17.0-beta5 version, the installation method can refer to here: https://devlake.apache.org/docs/next/GettingStarted/DockerComposeSetup
klesh commentedon May 19, 2023
How did you launch
devlakebackend andconfig-ui? Were you using the docker version for theconfig-ui?1ddo commentedon May 19, 2023
I've been working all day with the upgrade, by default the version value for the config-ui, grafana and devlake is set to "latest" then I replaced it with the version "v0.17.0-beta5" then ran docker-compose up -d but after that I encountered lots of issues one after another like token, certificate issue, installing grafana cli and others. Till now I'm working with those issues. Did you encounter this issue before? I'm using WSL Ubuntu by the way.
Here's one of the issue I'm getting:
failed to solve: failed to fetch anonymous token: Get "https://auth.docker.io/token?scope=repository%3Alibrary%2Fpython%3Apull&service=registry.docker.io": tls: failed to verify certificate: x509: certificate signed by unknown authority
For the Docker, I've connected my Docker Desktop to WSL Ubuntu and I have the latest Docker Desktop version and was able to run the 4 components (devlake, mysql, config-ui, grafana) but since I'm currently upgrading it to the latest version I haven't tried to run them again since I have a bunch of issues to work on.
BrookeKatalon commentedon May 19, 2023
I'm also interested in the ArgoCD connection
1ddo commentedon May 19, 2023
Hi @BrookeKatalon, are you willing to contribute with the ArgoCD development? If yes then we could collab with it.
klesh commentedon May 22, 2023
@1ddo I'm confused, are you trying to code for
devlakeor just use it to collect and observe data?For the former, you don't need the
docker-composefor bringing updevlakeandconfig-ui, please follow this guide to setup the Development Env https://devlake.apache.org/docs/next/DeveloperManuals/DeveloperSetupFor the latter, don't use the
docker-compose.ymlfrom the repo, download the one from the release page.The error message seems like a network problem
1ddo commentedon May 22, 2023
Hi @klesh , we need both since we need collect Data and observed data from ArgoCD but since it's not yet supported then we need to integrate it with DevLake. So don't we need to make DevLake work locally first before start coding, that way we could verify/test it later?
94 remaining items
vkovacik commentedon Apr 24, 2026
@rbstp
I’m working on accurately measuring Lead Time for Changes for a service delivered via Docker images.
As of DevLake v1.3.0, the ArgoCD plugin appears to rely solely on the deployment repository to infer what changes were released. Unless I’m overlooking something, it doesn’t currently establish a linkage between a Docker image tag and its corresponding source repository commits.
For example, if one deployment uses app-image:v1.0 and the subsequent deployment uses app-image:v1.1, we need a way to resolve the set of source commits between those two image versions. That mapping doesn’t seem to be available out of the box. I’m exploring potential approaches to bridge this gap and would greatly value any suggestions.
rbstp commentedon Apr 25, 2026
@vkovacik
You’ve identified the gap correctly. The ArgoCD plugin only sees the deployment repo, so source commit lineage between two image tags isn’t resolved automatically today.
Two paths worth considering:
deploymentCommitspayload (repoUrl+commitSha). This bypasses the ArgoCD plugin’s inference entirely and gives you exact commit-to-deployment mapping.antarasevich commentedon Apr 28, 2026
@rbstp
Could you please check fix #8861
in my response from ArgoCD API :
in history
{ "revision": "fc82b261274902c5db5764280a5e37fa205124d5", **"deployedAt": "2026-04-16T09:02:16Z",** "id": 30, "source": { "repoURL": "some repo", "path": "some path", "targetRevision": "master", "helm": { "valueFiles": [ "values.yaml", "../common-values.yaml", "../hal/app-of-apps/values.yaml" ] } }, "deployStartedAt": "2026-04-16T09:02:15Z" }while operational State is
"phase": "Succeeded", "revision": "fc82b261274902c5db5764280a5e37fa205124d5", **"startedAt": "2026-04-16T09:02:15Z",** "finishedAt": "2026-04-16T09:02:16Z"it produces 2 deployments with 1 sec difference . Items from History aare processed be deployedAt. while operationalState item is processed by startedAt
it is proposed in fix - to skip operationalState if it is Succeeded because it reflects info from the last sync
rbstp commentedon Apr 28, 2026
@antarasevich good fix, I just have a comment and there is a failing test to rectify.
antarasevich commentedon May 8, 2026
@klesh Could you please tell when the next beta release is planned?
klesh commentedon May 18, 2026
We are working on some bugfixes, it might take a while to finish them all.
Hopefully in 2 weeks.
github-actions commentedon Jul 18, 2026
This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.
avidspartan1 commentedon Jul 18, 2026
would hate to see this issue go stale. :)
github-actions commentedon Sep 18, 2026
This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.
avidspartan1 commentedon Sep 18, 2026
remove stale please