Skip to content

Retire Headlamp from the platform once the KSail web UI reaches feature parity #2496

Closed
1 of 1 issue completed

Description

@devantler

🤖 Generated by the Daily AI Assistant
Filed on the maintainer's direct direction (2026-07-05).

Platform half of the cross-repo epic devantler-tech/ksail#5827 (KSail web UI reaches Headlamp feature parity and absorbs its plugin capabilities).

Problem

The platform runs Headlamp (+ flux, cert-manager, keda, opencost, kubescape, and crossview plugins) as its Kubernetes UI while KSail grows its own web UI. Once KSail reaches parity (tracked in ksail#5827), keeping Headlamp means a duplicate UI to operate, patch, SSO-wire, and security-harden.

Proposed direction

GATED on ksail#5827's parity matrix reaching its must-have bar — do not start removal before that. Then, as one or a few reviewable slices:

  • Remove the Headlamp app (k8s/bases/apps/headlamp/) and its pluginsManager entries, HTTPRoute/SSO wiring, netpol, and VPA/exception references (grep the tree — kubescape exceptions and docs reference headlamp today).
  • Repoint anything that surfaces Headlamp (homepage tile, docs, runbooks) at the KSail web UI.
  • Fold the Kubescape Headlamp-plugin workflows (posture exceptions UI, runtime-alert tab) into their KSail-side equivalents per the parity matrix — these are the stickiest dependencies.

Acceptance criteria

  • Headlamp and all its plugins removed from every overlay; validate + scan green
  • No orphaned SSO client, netpol, VPA, exception, or docs references remain
  • The operator workflows Headlamp carried (resource browsing, Flux view, Kubescape posture/alerts, cost) have documented KSail-UI equivalents

Rough size: M (the removal itself is mechanical; the gate is the epic).

Activity

  1. coderabbitai commented on Jul 5, 2026

    @coderabbitai
    Contributor
    🔗 Related PRs

    #2320 - feat(kubescape): mirror ClusterSecurityException CRs as Headlamp plugin ConfigMap [closed]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. moved this to 📥 Backlog in 🌊 Project Boardon Jul 18, 2026
  3. added theissue type on Jul 18, 2026
  4. moved this from 🧊 Icebox to 🏃🏻‍♂️ In Progress in 🌊 Project Boardon Oct 26, 2026
  5. devantler commented on Oct 28, 2026

    @devantler
    ContributorAuthor

    Closing as completed. On 26 October 2026 the maintainer decided to remove Headlamp now instead of waiting for the KSail parity gate.

    🤖 Generated with Claude Code

  6. moved this from 🏃🏻‍♂️ In Progress to ✅ Done in 🌊 Project Boardon Oct 28, 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

    No labels
    No labels

    Type

    Fields

    No fields configured for Epic.

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions