60b8ee56de
* fix(seed): fix #742, workaround #698 Original fix proposal: https://github.com/jenkinsci/kubernetes-operator/issues/742#issuecomment-1304398590 * fix(install-plugin.sh): fix #758, #739 * the fix was original attempted here: https://github.com/jenkinsci/kubernetes-operator/pull/764 but was not working correctly due to 2-3 additional changes which needed to be done * removed the openshift check because the env is not mention anywhere and also the new jenkins-plugin-cli does not a specific command for openshift. Finally this does not make any sense in general, the only problem in ocp will be the user id that will be mapped to a random uid but that's another story. The command to install the plugins should remain the same across different k8s flavours. * fix(doc/test): fix /usr/bin/tini in any doc and validation * fix(jenkins): remove AdminWhitelistRule to avoid jvm stack trace, see: https://www.jenkins.io/doc/book/security/controller-isolation/jep-235/#api-compatibility * fix(seed): fix seed img built on a previous jvm, fix #761 * fix(plugin): update the base plugin to work with the newest version of jenkins:lts * fix(run): fix #778 * fix(backup): add a trap to remove the tmp dir if the tar fail, also fix: #770 * test(chart): update chart values for testing, will revert before merge * fix(configmap): leftover * fix(tests): fix seed job test * fix(e2e) * fix(e2e): helm * fix(operator): update the temporary img to reflect latests changes * Fix Helm e2e tests * add trap in case of unwanted exit and make shellcheck happy * chore(plugin): update git ver to 5.0.0 * fix(backup): always force delete the backup directory * chore(operator): update the temporary img to reflect latest changes * chore(jenkins): upgrade jenkins latest lts |
||
|---|---|---|
| .devbots | ||
| .github | ||
| api/v1alpha2 | ||
| assets | ||
| backup/pvc | ||
| chart | ||
| cicd | ||
| config | ||
| controllers | ||
| deploy | ||
| docs | ||
| hack | ||
| internal | ||
| pkg | ||
| test | ||
| version | ||
| website | ||
| .dockerignore | ||
| .gitignore | ||
| .golangci.yml | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| LICENSE.md | ||
| Makefile | ||
| PROJECT | ||
| README.md | ||
| ROADMAP.md | ||
| SECURITY.md | ||
| SUPPORT.md | ||
| VERSION.txt | ||
| checkmake.ini | ||
| config.base.env | ||
| config.crc.env | ||
| config.docker-desktop.env | ||
| config.minikube.env | ||
| config.openshift.env | ||
| gen-crd-api-config.json | ||
| go.mod | ||
| go.sum | ||
| main.go | ||
| variables.mk | ||
README.md
Jenkins Operator
What's the Jenkins Operator?
The Jenkins Operator is a Kubernetes Native Operator which manages operations for Jenkins on Kubernetes. It has been built with Immutability and declarative Configuration as Code in mind.
Preliminaries
Considering that this Operator is created for managing instances for Jenkins, it is important to understand what
- Jenkins Pipelines and
- CasC (Configuration as Code) are.
Jenkins Pipelines use Scripts written in Groovy which aid in the CasC aspect of Jenkins.
Jenkins uses plugins like CasC to extend it's solution space by carrying out Jobs of different kinds and providing a composable infrastructure for your CI/CD.
Out of the box it provides:
- Integration with Kubernetes (Jenkins kubernetes-plugin)
- Pipelines as Code (Jenkins pipelines)
- Extensibility via Groovy Scripts (similar to Jenkins script console) or (configuration as code plugin)
- Secure Defaults and Hardening (see the security section of the documentation)
Problem statement and goals
The main reason why we decided to implement the Jenkins Operator is the fact that we faced a lot of problems with standard Jenkins deployment. We want to make Jenkins more robust, suitable for dynamic and multi-tenant environments.
Some of the problems we want to solve:
- installing plugins with incompatible versions or security vulnerabilities
- better configuration as code
- security and hardening out of the box
- make errors more visible for end users
- orphaned jobs with no JNLP connection
- handle graceful shutdown properly
- proper end to end tests for Jenkins lifecycle
Documentation
Go to our documentation website for more information.
Selected content:
- How it works
- Getting Started
- Security
- Troubleshooting
- Developer Guide
- FAQ
- Jenkins Custom Resource Definition Schema
Common Issues and Workarounds
- Multibranch Pipelines and Backup Issues: https://github.com/jenkinsci/kubernetes-operator/issues/104#issuecomment-554289768
Community
Main channel of communication on topics related to Jenkins Operator is Jenkins Operator Category on Jenkins Community Discourse.
Here you can ask questions about the project, discuss best practices on using it, and talk to other users of the Operator, contributors and project's maintainers.
We also have a dedicated channel called #jenkins-operator on virtuslab-oss.slack.com.
Fill out (Invite form) and come say hi!
Snapshots between releases
We are trying our best to resolve issues quickly, but they have to wait to be released. If you can't wait for an official docker image release and acknowledge the risk, you can use our unofficial images, which are built nightly.
You can find the project's Docker Hub repository here.
Look for the images with tag "{git-hash}", where {git-hash} is the hash of the master commit that interests you.
Contribution
Feel free to file issues or pull requests, but please consult CONTRIBUTING document beforehand.
Before any big pull request please consult the maintainers to ensure a common direction.
Presentations
About the authors
This project was originally developed by VirtusLab and the following CONTRIBUTORS.