4.1

Deployments

Options for specific deployment targets:

Global options 

Common settings, independently the underlying deployment target:

KeyDescriptionDefault
lenses.deployments.events.buffer.sizeBuffer size for events coming from Deployment targets such as Kubernetes10000
lenses.deployments.errors.buffer.sizeBuffer size for errors happening on the communication between Lenses and the Deployment targets such as Kubernetes1000

Kafka Connect 

Kafka Connect connectivity is optional. Set up when using Kafka Connect clusters.

KeyDescriptionTypeDefault
lenses.deployments.connect.status.intervalTime interval to fetch ConnectAPI looking for new updates on running Connectors. It can be expressed like 30 second, 2 minute or 3 hour, mind the time unit is singularduration30.second
lenses.deployments.connect.actions.buffer.sizeBuffer size for events produced by user actions when interacting when Connectint1000

Kubernetes 

Kubernetes connectivity is optional. Minimum supported K8 version 0.11.10. All settings are string.

KeyDescriptionDefault
lenses.kubernetes.processor.image.nameThe url for the streaming SQL docker for K8lensesioextra/sql-processor
lenses.kubernetes.processor.image.tagThe version/tag of the above container4.1
lenses.kubernetes.config.fileThe path for the kubectrl config file/home/lenses/.kube/config
lenses.kubernetes.pull.policyPull policy for K8 containers: IfNotPresent or AlwaysIfNotPresent
lenses.kubernetes.service.accountThe service account for deployments. Will also pull the imagedefault
lenses.kubernetes.init.container.image.nameThe docker/container repository url and name of the Init Container image used to deploy applications to Kuberneteslensesio/lenses-cli
lenses.kubernetes.init.container.image.tagThe tag of the Init Container image used to deploy applications to Kubernetes4.1.0
lenses.kubernetes.watch.reconnect.limitHow many times to reconnect to Kubernetes Watcher before considering the cluster unavailable10
lenses.kubernetes.watch.reconnect.intervalHow often to wait between Kubernetes Watcher reconnection attempts expressed in milliseconds5000
lenses.kubernetes.websocket.timeoutHow long to wait for a Kubernetes Websocket response expressed in milliseconds15000
lenses.kubernetes.websocket.ping.intervalHow often to ping Kubernetes Websocket to check it’s alive expressed in milliseconds30000
lenses.kubernetes.pod.heapThe max amount of memory the underlying Java process will use900M
lenses.kubernetes.pod.min.heapThe initial amount of memory the underlying Java process will allocate128M
lenses.kubernetes.pod.mem.requestThe value will control how much memory resource the Pod Container will request128M
lenses.kubernetes.pod.mem.limitThe value will control the Pod Container memory limit1152M
lenses.kubernetes.pod.cpu.requestThe value will control how much cpu resource the Pod Container will requestnull
lenses.kubernetes.pod.cpu.limitThe value will control the Pod Container cpu limitnull
lenses.kubernetes.namespacesObject setting a list of Kubernetes namespaces that Lenses will see for each of the specified and configured clusternull
lenses.kubernetes.pod.liveness.initial.delayAmount of time Kubernetes will wait to check Processor’s health for the first time. It can be expressed like 30 second, 2 minute or 3 hour, mind the time unit is singular60 second
lenses.deployments.events.buffer.sizeBuffer size for events coming from Deployment targets such as Kubernetes10000
lenses.deployments.errors.buffer.sizeBuffer size for errors happening on the communication between Lenses and the Deployment targets such as Kubernetes1000