Air-gapped mode - is this important to you?

[jleni]

We keep hearing from teams that run clusters in restricted environments. No internet access, no phoning home, no cloud dependencies. Military, finance, healthcare, government, the usual suspects.

We're planning air-gapped support for Kunobi. The tool would work fully offline with no license server calls, no telemetry, no external dependencies. Just the binary and your kubeconfig.

Before we go deep on this, we want to understand:

• Are you running clusters in air-gapped environments?
• What tools do you currently use there? (Mostly kubectl?)
• What would make an air-gapped K8s tool actually useful vs just "works offline"?
• How do you handle updates and patches in those environments?

This is genuinely an area where we want to get it right rather than just check a box. If you have experience with air-gapped K8s operations, your input is really valuable here.