tree eedfaaf7dbd58424a52fe9ef7b86c2dfc1464519
parent e0903c633c90c93aaa33a60c3b742b1bdc1423a4
author Jean Helou <jhe@codamens.fr> 1615880678 +0100
committer GitHub <noreply@github.com> 1615880678 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgUGHmCRBK7hj4Ov3rIwAAdHIIAFu+epb/pqBQRbX8zGOwy60X
 q7Z21EfNJyYH0R5y26s8MNIQSS8Z1Kcr8366acsSCs1Ci4IdsqsinJCUDg3BF0kB
 osUAa+pJwbndCOeBRzbnureKTsqM1LzcmGL1VUyOep697bWLaKFLAqv3TYaTqLGf
 CrN340cq5uJ1oKkyJ4caymTwlRSvM1UQE7uzW7DeBEY/p6WMAcACm13IUPJG0ROx
 ScenKbqGa/eeti+brNr60+ioQrC+cJDH1UfXxikKt3T42N2mq52au/u2JYVAsITS
 Wap8Ziq15A4k14j1GzOpvNQQvEvwtCwszSBk8GRlz3vRZrUs2kA0orL//lu9uDs=
 =Cs5t
 -----END PGP SIGNATURE-----
 

makes cert-manager apiVersion configurable (#107)

This commit let's users override the apiVersion referenced in this
chart so that the chart can be used with newer cert-manager releases.
(script/cert-manager/install-cert-manager.sh installs 0.13.0 when
current version is 1.2.0...)

Fixes #68

### Motivation

cert-manager apiVersion changed after cert-manager 1.0.0 was released, which prevents the chart from provisionning certificates with newer cert-manager installation because of an incompatible apiVersion.

I have a cluster with cert-manager >1.0.0 installed, making `apiVersion` overridable makes it easy for me to install pulsar on that cluster

### Modifications

I introduced the value `certs.internal_issuer.apiVersion`, which by default uses the apiVersion that was previously hardcoded (`cert-manager.io/v1alpha2`) 
I replaced all occurrences of that apiVersion by a reference to the value so that users can override it to `cert-manager.io/v1` if they have a newer version of cert-manager installed.

### Verifying this change

- [x] Make sure that the change passes the CI checks.