feat: deploy secrets as secretRef in chart values

[ElderMatt]

📌 Summary

Replaces secrets withs secretRefs for Harbor and Oauth2-Proxy.

Uses environment Variables for Loki.

[merll]

Requested changes as current implementation does not seem to work well when moving on to sealed secrets.

PTO

[j-zimnowoda]

core.existingSecretKey does not exist in the Harbor helm chart. Did you mean core.secretName?

We have not set it before because we are relying on istio mTLS. What is the reason you decided to se it now?

[ElderMatt]

I mixed some things together in my notes, should now be fixed.

[j-zimnowoda]

I left one inline comment.

While running bin/compare.sh script I noticed that few Loki secretRefs are set to null which does not seem to be right.

spec.template.spec.containers.compactor
  + one map entry added:
    envFrom:
    - name: loki-s3-linode-credentials
    │ secretRef: null


data.config.yaml
  ± value change in multiline text (one insert, one deletion)
    -     s3: https://someaccessKeyId:somesecretvalue@nl-ams-1.linodeobjects.com/my-clusterid-loki
    +     s3: https://${S3_ACCESS_KEY_ID}:${S3_ACCESS_KEY_SECRET}@nl-ams-1.linodeobjects.com/my-clusterid-loki



spec.template.spec.containers.distributor
  + one map entry added:
    envFrom:
    - name: loki-s3-linode-credentials
    │ secretRef: null


spec.template.spec.containers.ingester
  + one map entry added:
    envFrom:
    - name: loki-s3-linode-credentials
    │ secretRef: null


spec.template.spec.containers.querier
  + one map entry added:
    envFrom:
    - name: loki-s3-linode-credentials
    │ secretRef: null


spec.template.spec.containers.query-frontend
  + one map entry added:
    envFrom:
    - name: loki-s3-linode-credentials
    │ secretRef: null