public_git
/
kubernetes-operator
mirror of https://github.com/jenkinsci/kubernetes-operator.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Update docs

This commit is contained in:
Jakub Mikusek 2019-01-17 11:17:00 +01:00
parent cdbf79e98f
commit fc7c75a8ca
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -7,10 +7,10 @@
## What's Jenkins Operator? ## What's Jenkins Operator?
Jenkins operator it's a Kubernetes native operator which fully manages Jenkins on Kubernetes. Jenkins operator is a Kubernetes native operator which fully manages Jenkins on Kubernetes.
It was built with immutability and declarative configuration as code in mind. It was built with immutability and declarative configuration as code in mind.
It provides out of the box: Out of the box it provides:
- integration with Kubernetes - integration with Kubernetes
- pipelines as code - pipelines as code
- extensibility via groovy scripts or configuration as code plugin - extensibility via groovy scripts or configuration as code plugin

4
docs/how-it-works.md
View File

@ -48,5 +48,5 @@ Main assumptions are:
## Jenkins Docker Images ## Jenkins Docker Images
**jenkins-operator** is fully compatible with **jenkins:lts** docker image and does not introduce and hidden changes there. **jenkins-operator** is fully compatible with **jenkins:lts** docker image and does not introduce any hidden changes there.
In case of need docker image can be easily changed in custom resource manifest as long as it supports standard Jenkins file system structure. If needed, the docker image can easily be changed in custom resource manifest as long as it supports standard Jenkins file system structure.

4
docs/security.md
View File

@ -5,7 +5,7 @@ By default **jenkins-operator** performs an initial security hardening of Jenkin
## Jenkins Access Control ## Jenkins Access Control
Currently **jenkins-operator** generates a username and random password and stores them in a Kubernetes Secret. Currently **jenkins-operator** generates a username and random password and stores them in a Kubernetes Secret.
However any other authorization mechanisms are possible an can be done via groovy scripts or configuration as code plugin. However any other authorization mechanisms are possible and can be done via groovy scripts or configuration as code plugin.
For more information take a look at [getting-started#jenkins-customization](getting-started.md#jenkins-customisation). For more information take a look at [getting-started#jenkins-customization](getting-started.md#jenkins-customisation).
## Jenkins Hardening ## Jenkins Hardening
@ -27,7 +27,7 @@ The **jenkins-operator** generates and configures Basic Authentication token for
## Kubernetes ## Kubernetes
Kubernetes API permissions are limited by the following RBAC roles: Kubernetes API permissions are limited by the following roles:
- [jenkins-operator role](../deploy/role.yaml) - [jenkins-operator role](../deploy/role.yaml)
- [Jenkins Master role](../pkg/controller/jenkins/configuration/base/resources/rbac.go) - [Jenkins Master role](../pkg/controller/jenkins/configuration/base/resources/rbac.go)