Open Source · AGPL-3.0 · Self-hosted

Model Kubernetes visually. Generate artifacts for supported resources.

IzyKube provides a visual namespace modeler with tested YAML and Helm export paths. The repository also contains cluster operations, inspection, and local-AI integrations with the limits recorded in its evidence matrix.

Open Installer Flow Pull Docker Image
Self-hosted; no hosted service required Works locally with Docker Compose Standalone GUI installer included Capability status documented publicly

Repository-backed model

The visual editor and supported artifact generators are traceable to code and automated tests.

From diagram to artifacts

Generate YAML or a Helm archive for resource types covered by the current model and tests.

Self-hosted integration

Run the application locally and connect it to third-party components such as Kubernetes, MongoDB, and Ollama.

What is present today

Keep the visual model and generated artifacts in one application

The repository implements a model-to-artifact workflow. Live-cluster apply/delete and inspection paths exist, but their end-to-end verification is partial.

Common split workflow

  • Architecture diagrams are maintained separately
  • Kubernetes manifests are authored in another tool
  • Cluster inspection happens through separate commands
  • Evidence for feature claims may be scattered

With IzyKube

  • A visual model feeds supported artifact generators
  • YAML and Helm export paths have automated tests
  • Apply/delete operations are available with partial integration coverage
  • Implemented, partial, planned, and external items are separated
Visible architecture Supported workloads and relationships can be represented on one canvas.
Exportable model The current model can generate tested YAML and Helm artifacts for supported resource types.
Auditable claims Each material capability is linked to implementation and verification evidence.

Core features

Implemented and partially verified product paths

The labels below are deliberately scoped. Full status, dependencies, and verification commands are in the evidence matrix.

Visual Namespace Modeler

Place workloads, services, config maps, ingresses, secrets, and volumes on a shared canvas.

Version Snapshots

Save, list, open, and delete namespace version records. A tested one-click rollback flow is not established.

YAML and Helm Export

Generate Kubernetes YAML or a Helm archive for the resource types covered by current code and tests.

Deploy and Undeploy

Use the available apply/delete paths with a connected cluster; automated live-cluster coverage is still partial.

Runtime Inspection

Inspect implemented cluster resource views and sync indicators; comprehensive drift detection is not established.

Open Architecture

Built with repository code plus external Angular, Spring Boot, MongoDB, Fabric8, Kubernetes, and related components.

Evidence and roadmap

Current claims are classified and reproducible

The audit separates implemented, partial, planned, and external-dependency items. OPA/Rego, SPIFFE/SPIRE, MCP, OpenTelemetry, first-party SBOM publication, and Sigstore/SLSA provenance are roadmap only.

Read Capability Evidence Read Background-IP Record

Standalone installer

Install and remove the stack from a separate GUI

The installer is external to the Java app. It runs Docker Compose and Makefile tasks from a dedicated setup toolchain, ships with Python and Tkinter inside the executable, and supports Italian and English.

What the installer does

  • Guides the configured installation and uninstall tasks
  • Shows phase progress instead of raw logs
  • Orchestrates Compose and addon tasks from outside the app
  • Uses a compact Izylife-themed interface

What the host needs

  • Docker Engine with Compose
  • No local Python installation
  • No local Tcl/Tk installation
  • Installer executable can be built locally with the documented Docker build
Read Installer Docs Build the Installer

Quickstart

Run IzyKube locally with Compose

Use the manual path for direct control over the configured services, or use the installer to run the same orchestration through a GUI.

1) Clone the repository 
git clone https://github.com/gcassata74/izykube.git
cd izykube
2) Start the configured services 
docker compose up
3) Open the UI and model your first namespace 
http://localhost:8090

FAQ

Common questions before adoption

Is IzyKube a hosted SaaS?

No. IzyKube is open-source and self-hostable. You can run it locally or in your own infrastructure.

Does it replace kubectl or Helm?

No. It complements your existing tooling by generating manifests and charts from a visual architecture model.

Who is it for?

The project is intended for platform teams, DevOps engineers, architects, and backend teams evaluating a visual Kubernetes modeling workflow.

Is there a separate graphical installer?

Yes. IzyKube ships a standalone GUI installer that orchestrates Compose and Makefile tasks without using the Java backend UI.

Evaluate the model-to-artifact workflow

Read the evidence matrix first, then use the installer or Compose path that fits your local evaluation.

Open Installer