According to the description, I checked the yaml of devops-controller, devops-jenkins, and all of them were consistent with the article description except devops-controller args. The default devops-controller args is --enabled-controllers argocd=true --argocd-namespace=argocd --pipelinerun-data-store=configmap. Then I used kubectl to create the following PodTemplate, but jenkins-casc-config has not been updated. Changing devops-controller args to be consistent with the content of the article (--enabled-controllers all=false,jenkinsagent=true,jenkinsconfig=true) or --enabled-controllers all=true still doesn’t work. Is my understanding wrong?
In https://github.com/kubesphere/devops-agent/issues/75 and https://github.com/kubesphere/ks-devops/pull/764 it is mentioned to use new method to manage jenkins agent, but no documentation is provided. Then I searched in Google and found the following article published by Rick.
According to the description, I checked the yaml of devops-controller, devops-jenkins, and all of them were consistent with the article description except devops-controller args. The default devops-controller args is
--enabled-controllers argocd=true --argocd-namespace=argocd --pipelinerun-data-store=configmap
. Then I used kubectl to create the following PodTemplate, but jenkins-casc-config has not been updated. Changing devops-controller args to be consistent with the content of the article (--enabled-controllers all=false,jenkinsagent=true,jenkinsconfig=true
) or--enabled-controllers all=true
still doesn’t work. Is my understanding wrong?kubesphere: v3.3.2 k8s: v1.24.9