joedayz
February 12, 2023, 8:26am
1
I installed my jenkins using this guide:
And also I created the service account according to the article:
kubectl apply -f jenkins-sa.yaml
My pipelines is in it github repo:
podTemplate(label: 'mypod', serviceAccount: 'jenkins', containers: [
containerTemplate(
name: 'docker',
image: 'docker',
command: 'cat',
resourceRequestCpu: '100m',
resourceLimitCpu: '300m',
resourceRequestMemory: '300Mi',
resourceLimitMemory: '500Mi',
ttyEnabled: true
),
containerTemplate(
name: 'kubectl',
image: 'amaceog/kubectl',
resourceRequestCpu: '100m',
resourceLimitCpu: '300m',
resourceRequestMemory: '300Mi',
resourceLimitMemory: '500Mi',
ttyEnabled: true,
command: 'cat'
show original
But When I execute my pipeline I got it error:
helm upgrade --install --wait --set ‘image.tag=22’ node-app-chart ./k8s/node-app-chart
Release “node-app-chart” does not exist. Installing it now.
Error: rendered manifests contain a resource that already exists. Unable to continue with install: could not get information about the resource ServiceAccount “node-app-chart” in namespace “jenkins”: serviceaccounts “node-app-chart” is forbidden: User “system:serviceaccount:jenkins:jenkins” cannot get resource “serviceaccounts” in API group “” in the namespace “jenkins”
script returned exit code 1
I am using minikube, helm v3, docker hub, github. The repo is public.
Any idea?
Thanks in advance.
Jose
halkeye
February 13, 2023, 12:08am
2
The jenkins service account doesn’t have access to deploy.
Update the account in kubernetes or use a different account.
joedayz
February 13, 2023, 12:24am
3
Hi @halkeye , I used it configuration suggested in the same article: https://raw.githubusercontent.com/jenkins-infra/jenkins.io/master/content/doc/tutorials/kubernetes/installing-jenkins-on-kubernetes/jenkins-sa.yaml .
kubectl create rolebinding jenkins-admin --clusterrole=admin --serviceaccount=jenkins:jenkins --namespace=jenkins -o yaml
But the command failed with other error:
helm upgrade --install --wait --set ‘image.tag=26’ node-app-chart ./k8s/node-app-chart
Error: UPGRADE FAILED: timed out waiting for the condition
script returned exit code 1
The result is now:
❯ kubectl get po -n jenkins
What is missing?
Joe
joedayz
February 13, 2023, 12:25am
4
I observed that created a new service account using the name of my chart:
❯ kubectl get serviceaccount -n jenkins
Joe
halkeye
February 13, 2023, 3:00am
5
This is more kubernetes knowledge than I have sorry. It sounds like you followed a tutorial on how to install jenkins, then using it to install an entirely different helm chart, and having issues.
I don’t think the service account that jenkins uses has access to deploy other things, but I have no idea what you’ve done.
joedayz
February 13, 2023, 6:08am
6
I could do that works!!
In values.yamls
serviceAccount: # Specifies whether a service account should be created create: false
No create service account. Because it’s trying to create a service account with the name of the chart.
In jenkinsfile change the command to:
sh “helm upgrade --install --namespace jenkins {HELM_APP_NAME} --set image.tag= {BUILD_NUMBER} ./${HELM_CHART_DIRECTORY}”
Thanks for your time.
