Discussion: keep CUBE telemetry/logging backend swappable for OpenShift-native options

[rudolphpienaar]

Discussion: keep CUBE telemetry/logging backend swappable for OpenShift-native options

Status

Discussion only

Priority

P2

Context / Background

Meeting discussion raised a valid concern that a custom or Kafka-heavy logging design may duplicate capabilities already available in OpenShift or native platform logging.

The immediate question is not which backend to adopt. The question is how to preserve the ability to swap telemetry/logging components based on real deployment conditions.

Detailed Scope

1. Record what deployment realities matter for first production deployment.
2. Record where native platform logging may already satisfy requirements.
3. Define what it means for telemetry/logging components to be swappable.
4. Identify which interfaces or boundaries in CUBE should remain backend-agnostic.

Acceptance Criteria

• Deployment concern is documented clearly.
• Native logging possibility is captured explicitly.
• Swappable requirements are stated concretely.
• Follow-up implementation implications are listed briefly.

Management Note

This is a bounded discussion issue.

Out of scope:

• final backend selection
• implementation of a logging stack