Hi team! Question about disabling GitOps and switching to Helm-based deployments.
We're running Devtron OSS (Helm install) with ArgoCD as the GitOps backend, and we have ~40+ applications already deployed using GitOps mode (DeploymentAppType: argo_cd).
We need to move away from GitOps because Devtron is committing ConfigSecrets as base64 values into the Git repos, which is a security concern for us.
After digging into the source code, we understand that:
The FEATURE_USER_DEFINED_GITOPS_REPO_ENABLE flag only controls whether users can define custom GitOps repos in the dashboard — it doesn't actually disable GitOps itself.
The real switch is DeploymentAppType per app/CD pipeline ("argo_cd" vs "helm"), and the deployment flow in deployApp() routes to either deployArgoCdApp() (writes to Git → ArgoCD syncs) or createHelmAppForCdPipeline() (direct Helm install, no Git).
Our questions:
What's the correct way to switch existing running apps from GitOps (argo_cd) to Helm? Is there a bulk migration path, or do we need to recreate each CD pipeline individually?
If we remove the GitOps configuration in Global Configurations → GitOps, what happens to apps that are currently deployed via ArgoCD? Do the ArgoCD Application CRDs get cleaned up automatically?
Is there anything we should watch out for during the transition? (e.g., downtime, orphaned ArgoCD resources, state loss)
Any guidance on the proper migration steps would be really appreciated. Thanks!
Hi team! Question about disabling GitOps and switching to Helm-based deployments.
We're running Devtron OSS (Helm install) with ArgoCD as the GitOps backend, and we have ~40+ applications already deployed using GitOps mode (DeploymentAppType: argo_cd).
We need to move away from GitOps because Devtron is committing ConfigSecrets as base64 values into the Git repos, which is a security concern for us.
After digging into the source code, we understand that:
The FEATURE_USER_DEFINED_GITOPS_REPO_ENABLE flag only controls whether users can define custom GitOps repos in the dashboard — it doesn't actually disable GitOps itself.
The real switch is DeploymentAppType per app/CD pipeline ("argo_cd" vs "helm"), and the deployment flow in deployApp() routes to either deployArgoCdApp() (writes to Git → ArgoCD syncs) or createHelmAppForCdPipeline() (direct Helm install, no Git).
Our questions:
What's the correct way to switch existing running apps from GitOps (argo_cd) to Helm? Is there a bulk migration path, or do we need to recreate each CD pipeline individually?
If we remove the GitOps configuration in Global Configurations → GitOps, what happens to apps that are currently deployed via ArgoCD? Do the ArgoCD Application CRDs get cleaned up automatically?
Is there anything we should watch out for during the transition? (e.g., downtime, orphaned ArgoCD resources, state loss)
Any guidance on the proper migration steps would be really appreciated. Thanks!