Periodic reload every ~10m with Global v3 unchanged (LogTargetList)

[ali-ghasempor]

Hi!

After upgrading to chart 1.48.0 and controller 3.2.6 (runtime logs show HAProxy 3.2.12), HAProxy reloads every ~10 minutes with:

reload required : Global config updated: map[LogTargetList:[[0xc000396fa0] []]]

But Global CR does not change (resourceVersion and generation stay constant).

Config uses ingress.v3.haproxy.org/v3 and spec.log_target_list with one stdout target.

I've seen similar issue reported but not exactly same: #765

Expected: no reload when Global/Defaults are unchanged.

Actual: periodic reload loop.

$ kubectl -n ingress get globals.ingress.v3.haproxy.org haproxy-kubernetes-ingress -o yaml
apiVersion: ingress.v3.haproxy.org/v3
kind: Global
metadata:
  creationTimestamp: "2026-02-17T08:41:48Z"
  generation: 1
  name: haproxy-kubernetes-ingress
  namespace: ingress
  resourceVersion: "721964690"
  uid: 04e04437-4dd1-43e6-a877-112e126b83a7
spec:
  close_spread_time: 1200000
  hard_stop_after: 1800000
  log_target_list:
  - address: stdout
    facility: daemon
    format: raw
    length: 65535
  lua_options:
    loads:
    - file: /etc/haproxy/lua/robots.lua
  performance_options:
    maxcompcpuusage: 50
    maxconn: 1010
    maxzlibmem: 10
    server_state_file: /tmp/server_state
  ssl_options:
    default_bind_ciphers: ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
    default_bind_ciphersuites: TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256
    default_bind_options: ssl-min-ver TLSv1.2 no-tls-tickets
    default_server_ciphers: ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
    default_server_ciphersuites: TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256
    default_server_options: ssl-min-ver TLSv1.2 no-tls-tickets
  tune_lua_options:
    bool_sample_conversion: normal
  tune_options:
    http_logurilen: 64000

[hdurand0710]

Hi @ali-ghasempor ,

It's actually similar to the issue you mentionned, as it's also an issue due to the migration to v3 CRDs.
It happens when the Global v3 CRD contains a log target list and it leads to the constant reloads you can experience.
A fix is under review.
We will keep you posted when merged and available in a release