Cyclops — Developer-Friendly Kubernetes Deployment UI

Introduction

Cyclops bridges the gap between platform engineers who define Helm charts and developers who need to deploy applications. It reads Helm chart values schemas and generates a user-friendly web form, so developers can deploy and configure apps without touching YAML or learning kubectl.

What Cyclops Does

• Generates web forms from Helm chart values.yaml and JSON Schema definitions
• Validates user input against schema constraints before deploying
• Deploys and updates Helm releases through the web interface
• Shows real-time status of deployed workloads including pods, services, and events
• Provides a module system where platform teams define templates developers consume

Architecture Overview

Cyclops runs as a controller and web server inside the Kubernetes cluster. Platform engineers register Helm chart repositories as templates. When a developer creates a new module, Cyclops fetches the chart's values schema, renders a dynamic form in the React frontend, validates the input, then performs a Helm install or upgrade. The backend watches deployed resources and surfaces their status through the UI.

Self-Hosting & Configuration

• Deploy via a single kubectl apply manifest into any Kubernetes cluster
• Register Helm chart repositories as template sources in the Cyclops settings
• Define JSON Schema annotations in your Helm chart values.yaml for rich form controls
• Configure RBAC to control which teams can deploy which templates
• Supports air-gapped installs with pre-pulled images and private chart repos

Key Features

• Zero YAML for developers: all configuration happens through validated web forms
• Platform team controlled: templates define what developers can and cannot change
• Schema-driven forms support dropdowns, toggles, number ranges, and conditional fields
• Real-time deployment status shows pod health, events, and logs in one view
• Helm-native means existing charts work without modification when schemas are present

Comparison with Similar Tools

• Backstage — developer portal with catalog; Cyclops focuses specifically on deployment UI
• Portainer — Docker/K8s management for admins; Cyclops targets developer self-service
• Rancher — full cluster management; Cyclops is a lightweight deployment interface layer
• Headlamp — generic K8s web UI; Cyclops provides guided, form-based deployment workflows
• KubeVela — OAM-based platform; Cyclops works with standard Helm charts directly

FAQ

Q: Do I need to modify my existing Helm charts to work with Cyclops? A: Cyclops works with any Helm chart. For richer forms (dropdowns, descriptions, validation), add JSON Schema annotations to your values.yaml.

Q: Can developers see logs and debug failed deployments? A: Yes. The UI shows pod status, events, and log streams for each deployed module, giving developers enough visibility to self-diagnose common issues.

Q: How does Cyclops handle multi-environment deployments? A: Platform teams register different chart versions or value overrides per environment. Developers select the target environment from the UI when deploying.

Q: Is Cyclops suitable for production clusters? A: Yes. It runs with minimal privileges and delegates all deployment logic to Helm. RBAC controls ensure developers can only access their designated templates and namespaces.

Sources

• https://github.com/cyclops-ui/cyclops
• https://cyclops-ui.com/docs