“server could not find the requested resource (get pods)” error when deploying Helm chart using Jenkins

Question

I am trying to deploy my Kubernetes Helm chart for sample Kubernetes cluster deployment. I created a sample Helm chart and added Docker image reference and deployed the Helm chart using terminal command helm install <my-chartname>. And micro service is accessing successfully without any problem.

After that I created a Jenkins pipeline job and added only one stage that containing the step for deployment. I added like the following way,

pipeline 
{
    agent any
    stages 
        {
            stage ('helmchartinstall')
                {
                    steps
                    {
                        sh 'helm install spacestudychart'
                    }
                }
        }       
}

And I am getting the error like following ,

[Pipeline] { (helmchartinstall)
[Pipeline] sh
+ helm install spacestudychart
Error: the server could not find the requested resource (get pods)

The same command is working when I am running through terminal.

Update

To upgrade tiller to latest version, I run the helm init --upgrade command on terminal. But the error remains still.

Output of "helm version" is like the following,

Client: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.14.0", GitCommit:"05811b84a3f93603dd6c2fcfe57944dfa7ab7fd0", GitTreeState:"clean"}

Output of "kubectl version --short" is like the following,

Client Version: v1.14.1
Server Version: v1.13.5

When I run command "kubectl --v=5 get pods; helm install spacestudychart" , I am getting the console output like the following,

+ kubectl --v=5 get pods
I0604 07:44:46.035459    2620 cached_discovery.go:121] skipped caching discovery info due to yaml: line 10: mapping values are not allowed in this context
I0604 07:44:46.152770    2620 cached_discovery.go:121] skipped caching discovery info due to yaml: line 10: mapping values are not allowed in this context
I0604 07:44:46.152819    2620 shortcut.go:89] Error loading discovery information: yaml: line 10: mapping values are not allowed in this context
I0604 07:44:46.283598    2620 cached_discovery.go:121] skipped caching discovery info due to yaml: line 10: mapping values are not allowed in this context
I0604 07:44:46.374088    2620 cached_discovery.go:121] skipped caching discovery info due to yaml: line 10: mapping values are not allowed in this context
I0604 07:44:46.467938    2620 cached_discovery.go:121] skipped caching discovery info due to yaml: line 10: mapping values are not allowed in this context
F0604 07:44:46.468122    2620 helpers.go:114] error: yaml: line 10: mapping values are not allowed in this context
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 255
Finished: FAILURE

Do I need to upgrade the kubectl version? What is the exact problem when running with Jenkins?

It's very likely because your credentials are incorrect, or in the unlikely case that the credentials do not have a RoleBinding (or ClusterRoleBinding) that grants them access to the Pods resource; running kubectl get pods right before that helm command may help distinguish the two, optionally with --v 15 to surface the actual underlying error message — mdaniel
@MatthewLDaniel - But the same command is successfully working when I am running through terminal. And I accessed the out put end point also. Error is getting only when I added the command into jenkins pipeline script. And Thank you for your response sir. — Jacob
"running through terminal" as jenkins, or you mean that your kubeconfig is correct? That's why I offered to put a get pods in the jenkins script, so it would run under the same circumstances as does your helm command — mdaniel
Yes sir. From terminal it is running properly. And I am able to access my rest APIs also. — Jacob
@MatthewLDaniel - Error getting only when I am running through jenkins pipeline job. By using terminal I am able to deploy and successfully getting the end point also. — Jacob

yasin lachini yasin lachini · Accepted Answer · 2019-06-07T16:23:12

This is 100% working I have this problem before.

At first builts jenkins user next copy config to /home/jenkins/.kube/

cp $HOME/.kube/config /home/jenkins/.kube/ 
or 
cp ~/.kube/config /home/jenkins/.kube/

And after that use

 chmod 777 /home/jenkins/.kube/config

your kubernetes command need your kubernetes config file . it is like key or password for your kubernetes cluster so you should give the kubernetes config to your jenkins and after that it can run kubernetes commands

This is very good tutorial that help me to solve it .

tutorial

UPDATE1 you should have jenkins user for adding jenkins user you should add jenkins user to your ubuntu or centos or ..

adduser jenkins

This is good link to adduser Adding user

UPDATE 2 You should install kubectl in your server that you use it as jenkins so that kubectl command can work and after that please copy the config in ~/.kube/config in your kubernetes cluster to your jenkins server that previously you installed kubectl on it.

“server could not find the requested resource (get pods)” error when deploying Helm chart using Jenkins

4 Answers

kubectl version

helm issue