Update README.md
This commit is contained in:
parent
0f0ea1d422
commit
b3828c10e2
|
|
@ -26,15 +26,14 @@ The main reason why we decided to implement the **Jenkins Operator** is the fact
|
|||
We want to make Jenkins more robust, suitable for dynamic and multi-tenant environments.
|
||||
|
||||
Some of the problems we want to solve:
|
||||
- volumes handling (AWS EBS volume attach/detach issue when using PVC)
|
||||
- [installing plugins with incompatible versions or security vulnerabilities](https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/customization/#install-plugins)
|
||||
- [better configuration as code](https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/customization/)
|
||||
- lack of end to end tests
|
||||
- handle graceful shutdown properly
|
||||
- [security and hardening out of the box](https://jenkinsci.github.io/kubernetes-operator/docs/security/)
|
||||
- orphaned jobs with no jnlp connection
|
||||
- [make errors more visible for end users](https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/diagnostics/)
|
||||
- [backup and restore for jobs history](https://jenkinsci.github.io/kubernetes-operator/docs/getting-started/latest/configure-backup-and-restore/)
|
||||
- orphaned jobs with no JNLP connection
|
||||
- handle graceful shutdown properly
|
||||
- proper end to end tests for Jenkins lifecycle
|
||||
|
||||
## Documentation
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue