Do not regenerate the WOPI Server Secrets on 'helm upgrade'

[SamuAlfageme]

When no config.{wopisecret,iopsecret} value is provided when installing the wopiserver chart, a pair of random secrets is generated for convenience.

However, this does also happen across upgrades:

staging, iop-wopiserver-secrets, Secret (v1) has changed:
  # Source: iop/charts/wopiserver/templates/secrets.yaml
  apiVersion: v1
  kind: Secret
  metadata:
    labels:
      app.kubernetes.io/instance: iop
      app.kubernetes.io/managed-by: Helm
      app.kubernetes.io/name: wopiserver
      app.kubernetes.io/version: v5.4
      helm.sh/chart: wopiserver-0.2.0
    name: iop-wopiserver-secrets
  data:
-   iopsecret: '-------- # (24 bytes)'
-   wopisecret: '-------- # (24 bytes)'
+   iopsecret: '++++++++ # (24 bytes)'
+   wopisecret: '++++++++ # (24 bytes)'
  type: Opaque

This behavior is not intended, as might require updating the IOP ConfigMap or reloading the IOP Deployment when using REVA_APPPROVIDER_IOPSECRET.

[SamuAlfageme]

linking https://github.com/helm/charts/issues/5167 for later ref.

[wkloucek]

As of now, Helm has no proper way to generate secrets ONCE (see also owncloud/ocis-charts#50).

Therefore I would recommend to always use secretsRef for production deployments:

charts/wopiserver/values.yaml

Lines 19 to 23 in f4c41b1

	# secretRef allows one to use an already existing secret instead of configuring the secrets below
	secretsRef:
	# secrets are only used if "secretRef" is not set or empty
	secrets:
	wopiSecret: