* Add note that jenkins.namespace also affects jenkins-operator resources
* Add handling of empty WATCH_NAMESPACE value of jenkins.namespace
If jenkins.namespace is set to "", it leads to WATCH_NAMESPACE
environment value of Jenkins Operator itself to be set to "", which
leads that operator watches all namespaces (see
https://github.com/jenkinsci/kubernetes-operator/issues/77#issuecomment-523727092).
This case requires custom handling: instead of creating role and
role_binding we need to create clusterrole and clusterrolebinding with
the required permissions.
* Bump chart version
* Fix grammar as suggested by @Sig00rd
Co-authored-by: Sig00rd <sz.fugas@gmail.com>
* Link to project's DockerHub in README's section on nightly builds, add paragraph about nightly builds in installation docs
* Fix repositoryURL in sample seedJob configuration with SSH auth
* Slightly expand on #348
* Fix formatting in docs on Jenkins' customization, update plugin versions
* Add notes on Jenkins home Volume in Helm chart values.yaml and docs (#589)
* Fix WATCH_NAMESPACE in helm chart
When applying the chart, the operator will now watch the correct
namespace. This required changes in roles and role bindings so that
the operator has access to both namespaces.
* Use Role instead of ClusterRole
Mitigates the risk of restrictions in creating ClusterRole in
multitenant k8s clusters.
* Update configuration-as-code version to 1.47
Fixed helm not creating role permissions #424
Added ability to use custom k8s cluster domain #461
Fixed propagation of JENKINS_OPTS to seed-job agent #462
Fixed updating last backup #421
Added configuration option for the user to specify annotations and labels for Jenkins pod via helm. Updated installation guide with information about this feature.
The chart is already in the format of a Helm 3 chart, however the `apiVersion` of the chart is set to `v1`, which is used for Helm 2 charts. Helm 3 charts should use `apiVersion: v2`.
This makes tools such as ArgoCD mistake the chart for a Helm 2 chart, and therefore template the chart using the wrong helm version. In ArgoCDs case, that means that the CRDs aren't deployed.
reference: https://helm.sh/docs/faq/#chartyaml-apiversion-bump