* 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>
aedc2aff59