Features / Improvements & Fixes
Changelog details for Lenses 6.0.6
New 🎉
Improvements 💪
Minimal start up requirements
The Agent now requires only a connection to HQ for startup. This connection can be configured through environment variables or by setting a provisioning file with HQ details. This streamlined process enhances the user experience for creating a new environment, allowing Lenses HQ to automatically push connection details to the Lenses agent.
SQL Processor Docker image
When developing a SQL processor, the application Docker image is fixed. Consequently, any updates for performance or security enhancements cannot be applied. In this release, a new API and user interface options were introduced to enable attachment of the desired Docker image.
Logging
Enhance the logs outlining the HQ connectivity status.
Helm
Service Type Configuration: Added configurable service.type parameter to allow customization of the Kubernetes service type (ClusterIP, NodePort, LoadBalancer, etc.)
New parameter in
values.yaml:service.type(default:ClusterIP)Updated service template to use the configurable value
Add persistence.provisioning configuration with 50Mi default size, disabled by default
Create PVC template for provisioning data storage at /data/provisioning
Update deployment to mount provisioning volume when enabled
Add helper function for provisioning claim name generation
Add tests for provisioning volume
Switch
.Values.persistence.existingClaimto.Values.persistence.log.existingClaimand.Values.persistence.provisioning.existingClaimand fail the deployment if the old value is being used
Fixes ✅
Helm
Component Label Correction: Fixed component labels from lenses to lenses-agent for proper identification
Updated in
deployment.yamlUpdated in
service.yaml
Last updated
Was this helpful?

