43 lines
1.7 KiB
HTML
43 lines
1.7 KiB
HTML
---
|
|
title: What's the Jenkins Operator?
|
|
linkTitle: What's the Jenkins Operator?
|
|
menu:
|
|
main:
|
|
weight: 10
|
|
|
|
---
|
|
|
|
{{% blocks/lead color="primary" %}}
|
|
<div style="font-size: 110%;" class="col-12">
|
|
jenkins-operator is a Kubernetes native operator which fully manages Jenkins on Kubernetes. <br />It was built with immutability and declarative configuration as code in mind.
|
|
</div>
|
|
{{% /blocks/lead %}}
|
|
|
|
|
|
{{< blocks/section >}}
|
|
|
|
<div class="col-md-1 order-md-1 hidden-xs hidden-sm hidden-md"></div>
|
|
<div class="col-md-3 col-lg-1 order-xs-first order-sm-first order-md-last text-center ">
|
|
<img src="/img/logo.svg" style="height: 75%; margin-left: -75%; margin-top: 50%;" alt="Logo"/>
|
|
</div>
|
|
<div class="col-md-4 col-lg-8 order-xs-2 order-sm-2 order-md-2">
|
|
<h1>The main reason why we decided to write the <b>jenkins-operator</b> 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.</h1>
|
|
<p class="lead mt-2">
|
|
<br />
|
|
Some of the problems we want to solve:
|
|
<ul>
|
|
<li>Volumes handling (AWS EBS volume attach/detach issue when using PVC)</li>
|
|
<li>Installing plugins with incompatible versions or security vulnerabilities</li>
|
|
<li>Better configuration as code</li>
|
|
<li>Lack of end to end tests</li>
|
|
<li>Handle graceful shutdown properly</li>
|
|
<li>Security and hardening out of the box</li>
|
|
<li>Orphaned jobs with no jnlp connection</li>
|
|
<li>Make errors more visible for end users</li>
|
|
<li>Backup and restore for jobs history</li>
|
|
</ul>
|
|
</p>
|
|
|
|
</div>
|
|
|
|
{{< /blocks/section >}} |