[BUG] ALB Controller Helm Chart mismatches Pod Log Level

[jonas-budde]

Describe the bug The Helm Chart requires the logLevel "warning", but the pod only accepts the following log levels: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace' and 'disabled'.

The Helm Chart should be modified to reflect these log levels. (See line 67 in values.schema.json of chart)

To Reproduce Steps to reproduce the behavior:

1. set logLevel to "warning"
2. See error, because "alb-controller" pod get in a ready state

Expected behavior The helm chart should reflect the supported Log Levels.

Screenshots

{"level":"info","version":"1.8.12","Timestamp":"2025-12-02T09:45:11.617133631Z","message":"Starting alb-controller"}
{"level":"fatal","version":"1.8.12","error":"Invalid log level 'warning' specified. Please specify one of [debug info warn error fatal panic disabled trace]","Timestamp":"2025-12-02T09:45:11.617280678Z","message":"Invalid log level for ALB Controller.\n\tPlease enter a valid log level.\n\tThe valid log levels are 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace' and 'disabled'."

Environment (please complete the following information):

• Kubernetes version: 1.32.9
• Helm Chart Version: 1.8.12

Additional context

This bug probably also occurs in the ALB Service Mesh Exentension Helm Deployment.