OpenShift CI/CD Concepts: Difference between revisions
| Line 33: | Line 33: | ||
Jenkins components need to access the OpenShift API exposed by the master for various operations: to access container images, to trigger a build, to check the status of a build, etc. so special security configuration needs to be applied to allow Jenkins to perform these operations. | Jenkins components need to access the OpenShift API exposed by the master for various operations: to access container images, to trigger a build, to check the status of a build, etc. so special security configuration needs to be applied to allow Jenkins to perform these operations. | ||
Jenkins authenticates to the API using the "system:serviceaccount:<''project-name''>:default service account, where <''project-name''> is the name of the project the Jenkins pod runs as part of. | Jenkins authenticates to the API using the "system:serviceaccount:<''project-name''>:default [[OpenShift_Security_Concepts#Service_Account|service account]], where <''project-name''> is the name of the project the Jenkins pod runs as part of. | ||
Revision as of 21:19, 21 November 2017
External
- https://blog.openshift.com/cicd-with-openshift/, youtu.be demos: 65BnTLcDAJI, wSFyg6Etwx8
- https://github.com/OpenShiftDemos/openshift-cd-demo, https://github.com/OpenShiftDemos/openshift-cd-demo/tree/ocp-3.5
- https://docs.openshift.com/container-platform/3.6/install_config/configuring_pipeline_execution.html
- https://github.com/openshift/jenkins
Internal
Overview
OpenShift provides a certified Jenkins container for building Continuous Delivery pipelines. When necessary, it scales the pipeline execution by on-demand provisioning of multiple Jenkins containers, allowing Jenkins to run many jobs in parallel.
Resources
This is the memory consumption based on a test installation:
- jenkins/jenkins-jnlp pod: 720 MB
- nexus pod: 610 MB
- gogs pod: 110 MB
Projects and Jenkins Pods
Does Jenkins needs its own project, or it can be spun off in an arbitrary project?
Security Considerations
Jenkins components need to access the OpenShift API exposed by the master for various operations: to access container images, to trigger a build, to check the status of a build, etc. so special security configuration needs to be applied to allow Jenkins to perform these operations.
Jenkins authenticates to the API using the "system:serviceaccount:<project-name>:default service account, where <project-name> is the name of the project the Jenkins pod runs as part of.
so they need to be granted sufficient privileges to invoke the OpenShift API for the projects requiring CI/CD pipeline services.
Example: Grant Jenkins Needed Privileges for the Projects that Require CI/CD Services