Welcome to KubeVela! In this guide, we'll walk you through how to install KubeVela, and deploy your first simple application.
Make sure you have finished and verified KubeVela installation following this guide.
A simple deployment definition in KubeVela looks as below:
Now deploy it to KubeVela:
This command will deploy a web service component to target environment, which in our case is the Kubernetes cluster that KubeVela itself is installed.
After deployed, you can now directly visit this application as it already attached with a
ingress trait (assume your cluster has Ingress enabled).
KubeVela allows you to deploy diverse components types. In above example, the
Web Service component is actually a predefined CUE module.
You can also try:
... and many many more. Please check the
Deploying Components section under
User Manuals for all supported types, and even go ahead to add your own.
KubeVela is not just about deploy. It allows you to attach predefined operational behaviors (named
Traits) to your components in-place. For example, let's assign a batch rollout strategy to our web service:
Now whenever the image version is updated in above YAML file, the
express-server component will rollout following strategy defined in
For all supported traits in KubeVela, please check
Attaching Traits section under
User Manuals. Not surprisingly, you can also add your own traits to KubeVela with just minimal effort.
Components and traits are just the beginning of your vela sail. KubeVela is by design a full functional Continuous Delivery (CD) platform with fine grained support for hybrid/multi-cloud/multi-cluster deployment.
I want to deploy an micro-services application with two components, firstly to staging cluster with only 1 instance, then pause and wait for manual approval. If approved, then deploy it to production cluster but with instances scaled to 3.
Oops, imagine how many add-hoc scripts and glue code are needed in your CI/CD pipeline to achieve automation and deployment success rate in above process.
While with KubeVela, above process can be easily modeled as a declarative deployment plan as below:
No more add-hoc scripts or glue code, KubeVela will get the application delivery workflow done with full automation and determinism. Most importantly, KubeVela expects you keep using the CI solutions you are already familiar with and KubeVela is fully complementary to them as the CD control plane.
For using KubeVela with your own CI pipelines and other tools, please check
Best Practices section in the sidebar for more real world examples.
All above features are just the first glance of KubeVela. For next steps, we recommend: