in_kubernetes_events: 5 missing or unexposed configuration parameters

[eschabell]

Bug Report

Describe the bug In the Kubernetes Events input plugin there are struct fields that may represent missing or unexposed configuration parameters. Looking at kubernetes_events.h, the following struct members are referenced in the code but have no corresponding config_map entries:

• db_locking (line 97) - Used in kubernetes_events_conf.c line 61, but no config entry
• db_journal_mode (line 98) - Used in kubernetes_events_conf.c line 70, but no config entry
• dns_retries (line 70) - Defined in struct but no config entry
• dns_wait_time (line 71) - Defined in struct but no config entry
• db.sync is defined in config_map but with FLB_FALSE offset, yet no code in kubernetes_events_conf.c that reads this property with flb_input_get_property(), so the config entry exists but appears unused.

In summary, 4 struct fields potentially missing config entries: db_locking, db_journal_mode, dns_retries, dns_wait_time and db.sync appears defined but not properly wired to be read from configuration.

To Reproduce None, they don't exist or are unreachable.

Expected behavior That the above mentioned configuration parameters are defined and available to be used.

Screenshots N/A

Your Environment

• Version used: all
• Configuration: all
• Environment name and version (e.g. Kubernetes? What version?): all
• Server type and version: all
• Operating System and version: all
• Filters and plugins: in_kubernetes_events

Additional context N/A

[patrick-stephens]

The db ones are probably similar to the tail input I guess @pwhelan?

[pwhelan]

As far as I can tell they seem to be lifted directly from the tail plugin. The db_journal_mode and db_locking property are derived from the initial commit; [e1e8e943f51e2] by @edsiper. Can you corroborate Eduardo?