frostmoln_kubernetes_cluster_addons (Data Source)

Reads, per addon of one Kubernetes cluster, the version it is pinned to beside the version the platform last confirmed it applied. This is the platform's record, not a read inside the cluster. When no version data is available (a cluster still being created, a deployment in progress or the platform unreachable) the read succeeds with a warning and addons is null.

Example Usage

data "frostmoln_kubernetes_cluster_addons" "main" {
  cluster_id = frostmoln_kubernetes_cluster.main.id
}

# Pins that went stale: the cluster keeps running them, but the version is
# deprecated or end of life. addons is null when no version data is available
# (for example while the cluster is still being created).
output "stale_addon_pins" {
  value = [
    for a in coalesce(data.frostmoln_kubernetes_cluster_addons.main.addons, []) :
    a.key if contains(["deprecated", "eol"], a.pinned_status)
  ]
}

Schema

Required

• cluster_id (String) The ID of the Kubernetes cluster.

Read-Only

• addons (Attributes List) The cluster's addons in the platform's order: its current selection first, then any addon it still owes a removal for. Never sorted. (see below for nested schema)

Nested Schema for addons

Read-Only:

• applied_version (String) The version the platform last confirmed it applied. It lags pinned_version while a change converges, and is empty when nothing is confirmed yet.
• key (String) The addon's catalog key.
• pinned_status (String) The lifecycle status of pinned_version now (for example current, supported, deprecated or eol) — how a pin that went stale is noticed. Empty when there is no pin or the version is no longer published. New values may appear.
• pinned_version (String) The version the cluster is pinned to. Empty for an addon with nothing to pin.
• state (String) How the pin and the applied version relate (for example converged, converging, removing or unsupported). New values may appear.