// Module included in the following assemblies:
//
// assembly-tls-sidecar.adoc

[id='ref-tls-sidecar-{context}']
= TLS sidecar configuration

The TLS sidecar can be configured using the `tlsSidecar` property in:

* `Kafka.spec.kafka`
* `Kafka.spec.zookeeper`
* `Kafka.spec.entityOperator`

The TLS sidecar supports the following additional options:

* `image`
* `resources`
* `logLevel`
* `readinessProbe`
* `livenessProbe`

The `resources` property can be used to specify the xref:assembly-resource-limits-and-requests-{context}[memory and CPU resources] allocated for the TLS sidecar.

The `image` property can be used to configure the container image which will be used.
For more details about configuring custom container images, see xref:assembly-configuring-container-images-{context}[].

The `logLevel` property is used to specify the logging level.
Following logging levels are supported:

* emerg
* alert
* crit
* err
* warning
* notice
* info
* debug

The default value is _notice_.

For more information about configuring the `readinessProbe` and `livenessProbe` properties for the healthchecks, see xref:ref-healthchecks-{context}[].

.Example of TLS sidecar configuration
[source,yaml,subs=attributes+]
----
apiVersion: {KafkaApiVersion}
kind: Kafka
metadata:
  name: my-cluster
spec:
  kafka:
    # ...
    tlsSidecar:
      image: my-org/my-image:latest
      resources:
        requests:
          cpu: 200m
          memory: 64Mi
        limits:
          cpu: 500m
          memory: 128Mi
      logLevel: debug
      readinessProbe:
        initialDelaySeconds: 15
        timeoutSeconds: 5
      livenessProbe:
        initialDelaySeconds: 15
        timeoutSeconds: 5
    # ...
  zookeeper:
    # ...
----