Changed
- (deps) Update assistant-ui packages in #2029 by @renovate[bot]
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.180.5...v0.180.6
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.180.5...v0.180.6
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.180.4...v0.180.5
trivy to upstream version v0.72.0.v2.8.0 version.Full Changelog: https://github.com/giantswarm/backstage/compare/v0.180.3...v0.180.4
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.180.2...v0.180.3
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.180.1...v0.180.2
Full Changelog: https://github.com/giantswarm/backstage/compare/v0.180.0...v0.180.1
Envoy Gateway | Overview dashboard: a lean single-pane health view
(traffic, latency, error rate, saturation) that avoids duplicating the detail
boards.Envoy Gateway | Clusters.Flux Logs dashboard to Shared Org / GitOps. It covers the Flux
controllers on the management cluster; workload-cluster Flux logs are not
ingested yet, because the flux-system namespace there has no tenant
assignment and Alloy drops untenanted pod logs.scripts/update-flux-dashboards.sh (make update-flux-dashboards), which
syncs the Flux dashboards from
fluxcd/flux2-monitoring-example
and re-applies our patches. It runs in the monthly dashboard-update workflow
and fails loudly if a patch stops applying.Organization and Cluster selectors to both Flux dashboards. They are
deployed to the management cluster’s Grafana, whose Mimir holds metrics for
every workload cluster, so until now every panel aggregated across a
customer’s whole fleet.Cilium | Overview for
triage, Cilium | Agent, Cilium | Datapath & Policy and Cilium | Operator.
Rows load collapsed and the per-agent panels use topk, so the entry point is
no longer a 355 kB dashboard that fires 75 queries at once.Cilium | Operator. The cilium-operator PodMonitor has always been
enabled, but none of its metrics were graphed: identity garbage collection,
workqueues, unmanaged pods and LB-IPAM.Overview,
Clusters, Access Logs and Control Plane. The Control Plane board
(formerly Global) absorbs the config push status panels, and Logs is
renamed to Access Logs.etcd-health dashboard cluster selector to etcd_server_id instead of up, so clusters with a managed control plane (aks, eks) no longer appear as empty options.Envoy Gateway | Proxy Global and
Envoy Gateway | Configuration dashboards, folded into the boards above.Flux Cluster Stats dashboard, which showed no data at all: every
panel queried gotk_reconcile_condition, a metric the Flux controllers no
longer expose. It now uses gotk_resource_info, the same metric our Flux
alerting rules use, and gains upstream’s Suspended Objects panel.gotk_resource_info on the Flux Cluster Stats dashboard. On
management clusters both flux-ksm and kube-state-metrics export identical
series, so the resource counts read exactly double.Flux Control Plane dashboard to the Flux namespace. Its
controller_runtime_* panels matched any operator exposing the same
controller label values (for example controller="helmrelease" is also
emitted by dex-operator and team-stamper).Flux Control Plane range windows from [1m] to
[$__rate_interval]. With our 60s scrape interval a one-minute window cannot
hold two samples, so the reconciliation and API-request panels were empty. The
ops/min panels use rate(...) * 60 so they stay per-minute rather than
reporting the count over the whole (range-dependent) window.Flux Cluster Stats targets at the $datasource variable. Seven of
them were pinned to a prometheus datasource uid that does not exist here,
and the target-level datasource overrides the panel.Flux namespace selector on Flux Control Plane to the Flux
controller pods. It was derived from a generic controller-runtime metric, so on
a management cluster it also offered external-secrets, giantswarm and
kube-system, and the dashboard could open on another operator’s data.Nodes Overview dashboard.make update-mixin
target that no longer exists (it was renamed to update-all-mixin), so the
automation failed instead of opening a PR.Cilium Metrics and Cilium performance dashboards, replaced by
the set above. 16 of their panels queried metrics Cilium no longer exposes
(the kvstore and BPF syscall sections, the L7 proxy counters and the policy
trigger panels), and Cilium performance duplicated the Overview.Full Changelog: https://github.com/giantswarm/backstage/compare/v0.179.11...v0.180.0