Skip to content
Kure Monitor

Release Notes — 2.6.0

Released: 2026-10-15

Kure Monitor 2.6.0 introduces multi-tenant Team management with granular RBAC, dedicated views for Failing Pods vs. Live Pods, interactive real-time container log streaming with play/pause and log export, and enterprise-grade Keycloak Single Sign-On (SSO) integration with group gating and Kubernetes secret support.

Headline Changes

Section titled “Headline Changes”
  • Teams & Granular Multi-Tenant RBAC (KAN-93): Multi-tenant team access control. Cluster admins can create teams, scope member access to specific namespaces (with live cluster namespace discovery) or all namespaces, assign allowed dashboard tabs (pod_monitoring, security_scanner, diagram, ai_advice), and set read vs write operational permissions.
  • Pod Monitoring Views: Failing Pods & Live Pods (KAN-94): Split Pod Monitoring into dedicated “Failing pods” and “Live Pods” views. The Live Pods view inventories all cluster pods in real time (Ready count, Status, Restarts, Age, Node) with namespace filtering.
  • Interactive Live Log Streaming (KAN-94): Added interactive live log streaming with Play/Pause controls. Users can stream real-time logs via Server-Sent Events (SSE) directly from either failing pods or healthy live pods, switch containers seamlessly, and download logs for offline analysis.
  • Keycloak Enterprise SSO (KAN-96): OpenID Connect (OIDC) single sign-on support configured via Helm chart values or dynamically via the Admin UI. Includes optional group-based access gating (allowed_groups), automatic admin role/group mapping (admin_role, admin_group), and secure clientSecret injection via existing Kubernetes Secrets (existingSecret, existingSecretKey).
  • Configurable Init Container Images: Support custom container images for all wait-for-backend init containers via global.initImage, agent.initImage, and securityScanner.initImage for air-gapped clusters and internal mirror registries.

Teams & Granular RBAC

Section titled “Teams & Granular RBAC”

Kure Monitor now provides multi-tenant team management designed for organizations running shared Kubernetes clusters.

  • Team Management: Admins can create teams, invite team members, and define exact operational boundaries.
  • Namespace Scoping: Teams can be granted access to all namespaces or restricted to a specific list of namespaces. The dashboard features live cluster namespace discovery dropdowns with auto-complete.
  • Allowed Tabs & Permissions: Control exactly which features each team sees — pod_monitoring, security_scanner, diagram, and ai_advice. Define read (view-only) or write (remediation, scans, configuration) permissions.
  • Reorganized Admin Panel: The Admin Panel now places Users & Teams as the first management tab, unifying user invitations, user roles, and team assignments into a cohesive experience.

See Teams & Multi-Tenancy and Authentication & Access Control for configuration guides.

Live Pods Inventory & Streaming Logs

Section titled “Live Pods Inventory & Streaming Logs”

Pod Monitoring has been redesigned to offer complete operational visibility into cluster workloads:

  • Failing Pods View: Focus strictly on unhealthy workloads (CrashLoopBackOff, ImagePullBackOff, OOMKilled, Pending) with AI-powered root-cause analysis and automated solution generation.
  • Live Pods View: Inspect healthy running pods across all or selected namespaces. See real-time statuses, restart counters, container readiness, age, and assigned worker nodes.
  • Live Log Streaming: Stream real-time container stdout/stderr logs over Server-Sent Events (SSE). Includes:
    • Play / Pause controls to freeze incoming output for close inspection.
    • Container selector for multi-container and sidecar pods.
    • Log Download button to export log traces for offline debugging and compliance records.

See Pod Monitoring Guide for more details.

Keycloak Enterprise SSO

Section titled “Keycloak Enterprise SSO”

Integrate Kure Monitor directly into your enterprise identity provider via Keycloak / OpenID Connect:

  • Zero-Code OIDC Integration: Configure SSO credentials directly from the Admin Panel or define them declaratively in values.yaml.
  • Group-Based Access Gating: Restrict Kure Monitor access to specific Keycloak user groups (e.g. platform-admins,devops,sre). Users outside these groups are cleanly denied entry.
  • Admin Role & Group Mapping: Map your organization’s existing Keycloak roles (e.g. kure-admin) or groups (e.g. /platform-admins) to automatic Kure administrator rights upon login.
  • Kubernetes Secret Protection: Store sensitive OAuth clientSecret credentials securely in pre-existing Kubernetes Secrets using keycloak.existingSecret and keycloak.existingSecretKey.

See Keycloak SSO Guide and Helm Chart Configuration for setup instructions.

Love Kure Monitor?Support us on GitHub
Star