kubesphere
Another copy of Jenkins CasC "jenkins_user.yaml" will hinder the upgrade of "jenkins.yaml"
If we make some upgrades into jenkins.yaml, like bumping builders' image version, people who have already installed KubeSphere 3.2.0 won't obtain those upgrades after KubeSphere upgrade. Because the jenkins_user.yaml has been fixed after the first installation.
After I upgrade helm chart of ks-devops, the new jenkins-casc-config ConfigMap won't be applied. Please see:
How to upgrade?
- Enter shell of ks-installer Pod
- Clone https://github.com/kubesphere-sigs/ks-devops-helm-chart.git from master branch and get in
- Execute the following command
helm -n kubesphere-devops-system upgrade devops charts/ks-devops/ --install --reuse-values - See the result
I don't have a solution right now, just let the problem emerge again.
I don't think this is a bug. Because this is expected according to our design. I prefer to have an enhancement. Considering the team's capacity, I'm going to lower the priority of this issue.
/remove-kind bug /remove-priority high /kind feature
