You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Dennis-Mircea Ciupitu (Jira)" <ji...@apache.org> on 2026/04/20 15:57:00 UTC

[jira] [Created] (FLINK-39501) Logback Support in Flink Kubernetes Operator

Dennis-Mircea Ciupitu created FLINK-39501:
---------------------------------------------

             Summary: Logback Support in Flink Kubernetes Operator
                 Key: FLINK-39501
                 URL: https://issues.apache.org/jira/browse/FLINK-39501
             Project: Flink
          Issue Type: Improvement
          Components: Kubernetes Operator
            Reporter: Dennis-Mircea Ciupitu


h1. Summary
Introduce Logback as an alternative logging framework for the Flink Kubernetes Operator, selectable at install time via Helm configuration.

h1. Motivation
The Flink Kubernetes Operator currently only supports Log4j2 for logging. Logback is a widely adopted logging framework in the Java ecosystem and many organizations standardize on it across their infrastructure. Adding Logback support gives users the flexibility to align the operator's logging with their existing observability stack without custom image builds.

h1. Goals
 * Allow users to switch between Log4j2 (default) and Logback at install time via the {{logging.framework}} Helm value
 * Ship default Logback configuration files ({{{}logback-operator.xml{}}}, {{{}logback-console.xml{}}}) with log output format aligned to the existing Log4j2 defaults
 * Handle XML configuration overrides correctly (replacement instead of append, since XML cannot be concatenated)
 * Document the feature, its usage, and known limitations (SLF4J 1.7.x / Logback 1.2.x version constraints)
 * Add E2E test coverage for both logging frameworks



--
This message was sent by Atlassian Jira
(v8.20.10#820010)