Closed sokuyucu closed 3 years ago
Probably we can just ignore the cp command errors. See also ks-installer/devops/jenkins.
Probably we can just ignore the cp command errors. See also ks-installer/devops/jenkins.
that fixed the problem. thanks!
Actually, this is a potential issue. I'll keep it open until it is confirmed.
Fixed
I have enabled the devops plugin for my kubesphere cluster with 3 master 3 worker nodes, after the installation I have tried to create a DevOps project. Although the project was created, I was not able to access the pipelines tab inside the DevOps project but i could access the Project Management tab.
After a few tries I decided to check the DevOps plugin and I saw that both the ks-jenkins and ks-jenkins-agent components were in warning status, so i proceeded to observe the workloads of kubesphere-devops-system namespace and ks-jenkins workload was in updating status with MinimumReplicasUnavaiable warning.
There was only one pod that had 2 containers with waiting status.
Init container's log: cp: cannot stat '/var/jenkins_config/*.groovy': No such file or directory
kubernetes varsion: 1.18.6 kubesphere platform version: 3.0.0 clusterRole: host 3 master 3 worker each has 4 CPU and 16GB ram storage: ceph 30GB/150GB avaiable
enabled plugins: -service mesh -openpitrix -notification -networkpolicy -logging -events -devops -alerting -auditing
ks-jenkins workload's YAML
PS: sorry for so many edits, it is my first issue