- My Kubernetes Cloud configuration does not work.
- I am having issues with spining up an agent by using a Kubernetes Pod Template.
Please, notice that many issues are related to the selected image for the Pod Template, so before continuing please verify if your Pod Template can spin up an agent using the
jenkins/jnlp-slave image as you can read on the description of the plugin:
Tested with jenkins/jnlp-slave, see the Docker image source code.
This article describes how to collect the minimum required information for Kubernetes Cloud on a Client/Managed Master so that it can be efficiently troubleshooted.
If the required data is bigger than 20 MB you will not be able to use ZenDesk to upload all the information. On this case we would like to encourage you to use our upload service in order to attach all the required information.
- CloudBees Jenkins Enterprise - Managed Master (CJE-MM)
- CloudBees Jenkins Team (CJT)
- CloudBees Jenkins Platform - Client Master (CJP-CM)
- Kubernetes Cloud plugin
[ ] Jenkins Kubernetes Cloud description
[ ] Jenkins Kubernetes Pod Template description
[ ] Kubernetes Cluster Description
[ ] Kubernetes description of the Agent pod
[ ] Jenkins log recorder for Kubernetes Cloud Plugin
[ ] Support bundle from CM
The Jenkins Kubernetes Cloud configuration is saved under
$JENKINS_HOME/config.xml you have 2 options here:
- When you generate the support bundle ensure to select the
Jenkins Global Configuration File (Encrypted secrets are redacted)option.
The Jenkins Kubernetes Cloud description including:
- In the case, the Pod Template has been defining in a Pipeline, attach the
- Dockerfile, in the case you are not using
Jenkins Kubernetes Cloud description including:
- The Cloud provider where the cluster is hosted (Openshift, AWS, etc)
Jenkins Kubernetes Cloud Pod description and events:
$> kubectl describe pod $my-jenkins-agent > $my-jenkins-agent-describe.txt
Configure a couple of new Jenkins log recorder
When you generate the support bundle ensure to select
All loggers currently enabled
- Reproduce the issue in order to populate those logs before producing the support bundle.
- After you verified that those logs have been populated, do not leave those logs enabled in a production environment. This is just for troubleshooting. Then they should be removed.
A support bundle from the Master where the Kubernetes Cloud has been configured.