KubeVela — Modern Application Delivery Platform on Kubernetes

Introduction

KubeVela is a CNCF incubating project that gives platform engineers a vocabulary above raw Kubernetes YAML. Instead of shipping raw Deployments, Services and NetworkPolicies, teams describe Applications composed of Components (stateless service, web-service, helm) and Traits (ingress, autoscaling, sidecar) that the control plane compiles into the right cluster-native objects.

What KubeVela Does

• Provides a declarative Application CRD with Components, Traits, Policies and Workflow
• Renders those high-level definitions into Kubernetes objects via CUE-powered templates
• Orchestrates multi-cluster rollouts with Canary, Blue/Green and manual-approval steps
• Bundles an addon registry (observability, secrets, FluxCD, Velero) for one-click install
• Offers a web UI, CLI and REST API for developer-friendly workflows

Architecture Overview

The core is a vela-core controller that reconciles Application, ComponentDefinition, TraitDefinition, PolicyDefinition and WorkflowStepDefinition CRDs. Definitions are CUE scripts; the controller evaluates them to generate child resources (Deployments, Services, Argo Rollouts, etc.) and tracks ownership. A multi-cluster manager (ClusterGateway) projects those resources onto managed clusters. The VelaUX add-on provides a dashboard for developer self-service.

Self-Hosting & Configuration

• Install with vela install or the published Helm chart
• Register managed clusters with vela cluster join <kubeconfig>
• Author reusable Components/Traits as CUE files checked into Git
• Integrate with Flux, Terraform or Crossplane through built-in definitions
• Secure the control plane with RBAC projections per tenant

Key Features

• Open Application Model abstractions standardise how apps are shipped
• CUE-based definitions are code — type-checked, testable, reusable
• Workflow engine for advanced rollouts (canary, dependency, approval)
• Multi-cluster and multi-environment delivery in one Application
• Addon ecosystem brings Argo, Flux, Velero and more

Comparison with Similar Tools

• Argo CD — GitOps for raw manifests; KubeVela adds modelling above that
• Flux — also GitOps-focused; KubeVela adds rollouts and app abstractions
• Crossplane — cloud resource control plane; KubeVela focuses on app delivery
• Helm — templating; KubeVela models full applications with traits and workflows
• Backstage + plugins — developer portal layer; KubeVela exposes the runtime substrate

FAQ

Q: Do I need to learn CUE? A: Basic CUE helps when authoring custom Components/Traits. For day-to-day use the CLI, UI and built-in definitions are enough.

Q: Does KubeVela replace GitOps? A: No. It complements GitOps tools like Flux and Argo CD; you commit KubeVela Applications to Git and let the controller reconcile them.

Q: How does multi-cluster work? A: The ClusterGateway component proxies API calls to managed clusters, so the control plane schedules resources to them transparently.

Q: Is there a UI for developers? A: Yes. Enable the VelaUX add-on for a web console covering applications, environments, targets and deployment history.

Sources

• https://github.com/kubevela/kubevela
• https://kubevela.io