Skip to content

[hermes] feat(log-router): add kafkaForwarding configuration - #12707

Open
wiltongarcia wants to merge 1 commit into
masterfrom
hermes-log-router-kafka-forwarding
Open

[hermes] feat(log-router): add kafkaForwarding configuration#12707
wiltongarcia wants to merge 1 commit into
masterfrom
hermes-log-router-kafka-forwarding

Conversation

@wiltongarcia

Copy link
Copy Markdown

Summary

  • Adds logRouter.kafkaForwarding block to values.yaml (disabled by default): enabled, brokers, topic, tls
  • Adds a conditional block in log-router-configmap.yaml that injects LOG_ROUTER_KAFKA_FORWARDING_BROKERS, LOG_ROUTER_KAFKA_FORWARDING_TOPIC, and LOG_ROUTER_KAFKA_FORWARDING_TLS when kafkaForwarding.enabled=true
  • Uses required guards so a deployment with enabled=true but missing brokers/topic fails at render time

No other template changes needed

TLS with a public CA (fortlogs broker) requires no mounted Secret files — the env var LOG_ROUTER_KAFKA_FORWARDING_TLS: "true" instructs log-router to use system root CAs.

Related

  • log-router code change: SAP-cloud-infrastructure/log-router#42
  • Activated for qa-de-1 via the accompanying secrets PR

Adds logRouter.kafkaForwarding (enabled, brokers, topic, tls) to
values.yaml (disabled by default) and a conditional block in the
log-router ConfigMap template that injects the three
LOG_ROUTER_KAFKA_FORWARDING_* env vars when enabled.

No Secret or StatefulSet changes needed — TLS with a public CA
requires no mounted cert files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant