configuring-keda-module-3cc1f25.md

Configuring Keda Module

By default, the Keda module comes with the default configuration. You can change the configuration using the Keda CustomResourceDefinition (CRD). See how to configure the logging.level attribute, enable the Istio sidecar injection, change resource consumption, define custom annotations, or override the minimum TLS version.

Prerequisites

• You have added the Keda module. To learn how to do it, see Adding and Deleting a Kyma Module.

Procedure

1. Go to Kyma dashboard. The URL is in the Overview section of your subaccount.

2. Choose Modify Modules, and in the View tab, choose keda.

3. Go to Edit, and provide your configuration changes. You can use the Form or YAML tab.

   • To define the level of detail of your logs, set the logging.level attribute to one of the following values:

     • debug - is the most detailed option. Useful for a developer during debugging.

     • info - provides standard log level indicating operations within the Keda module. For example, it can show whether the workload scaling operation was successful or not.

     • error - shows error logs only. This means only log messages corresponding to errors and misconfigurations are visible in logs.

     • warn - shows warning logs only. This means only log messages corresponding to warnings and potential issues are visible in logs.

     spec:
       logging:
         operator:
           level: "debug"
     

   • To define the log output format, set the logging.format attribute to one of the following values:

     • json - outputs logs in JSON format, which is structured and machine-readable.

     • console - outputs logs in plain text format, which is human-readable.

     spec:
      logging:
        operator:
          level: "info"
          format: "json"
        metricServer:
          level: "info"
          format: "json"
        admissionWebhook:
          level: "info"
          format: "json"
     

     For more information about logging configuration, see Keda logging configuration.

   • To enable the Istio sidecar injection for operator and metricServer, set the value of enabledSidecarInjection to true. For example:

     spec:
       istio:
         metricServer:
           enabledSidecarInjection: true
         operator:
           enabledSidecarInjection: true
     

   • To change the resource consumption, enter your preferred values for operator, metricServer, and admissionWebhook. For example:

     spec:
       resources:
         operator:
           limits:
             cpu: "1"
             memory: "200Mi"
           requests:
             cpu: "150m"
             memory: "150Mi"
         metricServer:
           limits:
             cpu: "1"
             memory: "1000Mi"
           requests:
             cpu: "150m"
             memory: "500Mi"
         admissionWebhook:
           limits:
             cpu: "1"
             memory: "1000Mi"
           requests:
             cpu: "50m"
             memory: "800Mi"
     
     

   • To define custom annotations for KEDA workloads, enter your preferred values for operator, metricServer and admissionWebhook. For example:

     spec:
       podAnnotations:
        operator:
          metrics.dynatrace.com/scrape: 'true'
          metrics.dynatrace.com/path: '/metrics'
        metricServer:
          metrics.dynatrace.com/scrape: 'true'
          metrics.dynatrace.com/path: '/metrics'
        admissionWebhook:
          metrics.dynatrace.com/scrape: 'true'
          metrics.dynatrace.com/path: '/metrics'
     
     

   • To override the minimum TLS version used by KEDA (default isTLS12), set the KEDA_HTTP_MIN_TLS_VERSION environment variable. For example:

     spec:
       env:
         - name: KEDA_HTTP_MIN_TLS_VERSION
           value: TLS13
     
     

Next Steps

For more information about the KEDA resources, see KEDA concepts.