Helm

Packages

• We have made new alpha release 17:

  • Agent image:

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

  • HQ image:

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

  • HQ CLI image

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

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

HQ Changelog

Support for additional environment variables

When working on software projects, there often arises a need to create additional environment variables for various purposes. One common scenario for this is when users need to securely handle sensitive information, such as passwords or API keys. By storing a user password in a secret, the system ensures that such sensitive information is not exposed to unauthorized access, and this practice offers enhanced security.

Additional Environment syntax

values.yaml

lensesHq:
  # Additional env variables appended to deployment
  # Follows the format of [EnvVar spec](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.21/#envvar-v1-core)
  additionalEnv:
    - name: ADMIN_USER
      valueFrom:
        secretKeyRef:
          name: multi-credentials-secret
          key: user1-username
    - name: ADMIN_USER_PWD
      valueFrom:
        secretKeyRef:
          name: multi-credentials-secret
          key: user1-password

Reading username & pwd from secret

Rest port consolidation

Property restPorthas been removed and replaced by lensesHq.http.address

Small bugfixes

Agent changelog

Syntax changes

In the provisioning, there has been slight adjustment in the parent agent configuration parameter.

Changes:

• lenses has been renamed to lensesAgent

Old connection structure

values.yaml

lenses:
  provision:
    enabled: true
    version: "2"
    path: /mnt/provision-secrets
    connections:
      grpcServer:     # Property that has changed
        - name: lenses-hq
          version: 1
          tags: ['hq']
          configuration:
            server:
              value: [HQ_URL]
            port:
              value: 10000
            apiKey:     # Property that has changed
              value: ${LENSESHQ_AGENT_KEY}

New connection structure

Provisioning changes

As provisioning with the latest version (2) is mandatory for successful running of the agent, both configs are removed.

values.yaml

lensesAgent:   # Renamed property
  provision:
    path: /mnt/provision-secrets
    connections:
      lensesHq:
        - name: lenses-hq
          version: 1
          tags: ['hq']
          configuration:
            server:
              value: [HQ_URL]
            port:
              value: 10000
            agentKey:   
              value: ${LENSESHQ_AGENT_KEY}

Removal of H2 database support

In the the past it was possible to use H2 database which would be instantly deployed and ready to use alongside the agent.

Due to certain performance limitations which come with H2 database which can impact the agent functionality, we decided to completely remove H2 support.

However, persistence parameter still remains and can be used to enable extra volume creation dedicated specifically just logs.

persistence:
  log:
    # -- (boolean) Extra volume creation dedicated for logs.
    # @section -- Persistence scope values
    enabled: true
    # -- (boolean) Annotations dedicated for logs.
    # @section -- Persistence scope values
    annotations: {}
    # -- (list) Access mode rights for created persistence volumes.
    # @section -- Persistence scope values
    accessModes:
      - ReadWriteOnce
    # -- (string) Size of persistence that will be created.
    # @section -- Persistence scope values
    size: 5Gi