Skip to content

Allow platform Kubernetes monitoring to reference an existing Observability instance #88

Open

Description

@lweberru

The root management module and each platform Kubernetes module can create separate STACKIT Observability instances. Users need to choose a compatible existing or centrally declared instance for SKE monitoring instead of necessarily creating another.

Current behavior: src/modules/platform-kubernetes/2-observability.tf creates an instance whenever observability.enabled is true; 3-cluster.tf directly references that resource. The root observability input creates a separate instance in the management project. Management currently exposes no Observability instance output for this reference.

Proposed scope:

  • Explicit monitoring modes disabled / create managed instance / reference compatible instance.
  • Publish needed instance ID and endpoint outputs and wire declarative references without storing credentials in configuration.
  • Verify SKE project/region/permissions requirements for cross-project references before offering central management-instance selection.
  • Preserve current resource addresses/defaults; prevent silent destruction when changing ownership to a reference.
  • Validate dangling/disabled references and test reuse creates no duplicate instance.
  • Keep cluster-system monitoring separate from application telemetry and Telemetry Router.

Official SKE documentation describes choosing an existing instance: https://docs.stackit.cloud/products/runtime/kubernetes-engine/how-tos/monitor-your-clusters/

Activity

  1. added
    area:acceleratorAccelerator Terraform/OpenTofu roots, modules and examples
    priority:p2Important improvement; schedule after P1 and prerequisites
    effort:lArchitecture, lifecycle or multiple systems; split before implementation
    enhancementNew feature or request
    needs-investigationValidate API/provider behavior or product contract before implementation
    on Oct 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:acceleratorAccelerator Terraform/OpenTofu roots, modules and exampleseffort:lArchitecture, lifecycle or multiple systems; split before implementationenhancementNew feature or requestneeds-investigationValidate API/provider behavior or product contract before implementationpriority:p2Important improvement; schedule after P1 and prerequisites

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions