Helm

Packages

• We have made new alpha release 18:

  • Agent image:

    • lensting/lenses-agent:6.0.0-alpha.4

  • HQ image:

    • lensting/lenses-hq:6.0.0-alpha.18

  • HQ CLI image

    • lensting/lenses-cli:6.0.0-alpha.18

• New Helm version 18 for agent and for the HQ: https://lenses.jfrog.io/ui/native/helm-charts-preview/

HQ Changelog

Support for ESO SecretStore

In the past only ClusterSecretStore when handling external secret was support. With a new version you can choose to pick either ClusterSecretStore or a SecretStore when creating external secret.

ClusterSecretStore

values.yaml

lensesHq:
  storage:
    postgres:
      enabled: true
      host: postgres.host.url
      port: 5432
      username: postgres
      database: hq
      passwordSecret:
        type: "externalSecret"
        name: postgres
        key:  password
        externalSecret:
          secretStoreRef:
              type: ClusterSecretStore
              name: css-secrets

SecretStore

values.yaml

lensesHq:  
  storage:
    postgres:
      enabled: true
      host: postgres.host.url
      port: 5432
      username: postgres
      database: hq
      passwordSecret:
        type: "externalSecret"
        name: postgres
        key:  password
        externalSecret:
          secretStoreRef:
              type: SecretStore
              name: ss-secrets

ESO additional specs

New property has been added to external secret template called additionalSpecs where you can add or change any of the specs that would normally be added in ExternalSecret resource.

Example:

lensesHq:  
  storage:
    postgres:
      enabled: true
      host: postgres.host.url
      port: 5432
      username: postgres
      database: hq
      passwordSecret:
        type: "externalSecret"
        name: postgres
        key:  password
        externalSecret:
          additionalSpecs:
            refreshInterval: 12h
          secretStoreRef:
              type: ClusterSecretStore
              name: css-secrets

Small bugfixes

• lensesHq.http.tls property was referencing wrong properties within defined values.yaml