Skip to main content
Version: v1.9


Common Questions

Who are using KubeVela?

What is the difference between KubeVela and project-X ?

Refer to the comparison details.

Do you support Crossplane? What's the difference between terraform and Crossplane in KubeVela?

KubeVela natively supports Crossplane as they're already CRDs, while terraform was not a CRD controller, so the KubeVela community authored a terraform controller for integration. You can choose any of them as you wish.

What's the relationship between KubeVela and OAM? What will KubeVela mainly focus?

  • OAM(Open Application Model) is the model behind KubeVela, it provides a platform-agnostic application model including the best practices and methodology for different vendors to follow. The evolution of the model depends primarily on the practices of KubeVela currently.
  • KubeVela is the control plane running on Kubernetes, it works as a CRD controller and brings OAM model into your Cloud Native PaaS along with lots of addon capabilities. KubeVela will mainly focus on application delivery, the goal is to make deploying and operating applications across today's hybrid, multi-cloud environments easier, faster and more reliable.

Common Issues

Why things of https://* is out of date?

Recently, we're removing the dependency of the domain due to some compliance issues, so things are migrated. Please check the following lists to find the new address:

Image Hub"""" or ""
Helm charts
Official Addon Registryhttps://addons.kubevela.net
Experimental Addon Registry-
CLI from release page

You have reached rate limit for Docker Image Registry

By default, the community use images from docker registry for installation. You can use the following alternatives:

  1. You can use github container registry, check the list of official images for more details. There're two kinds of format:
  • Before v1.4.1, the image format is<git-repo>/vela-core:<version>, e.g. "".
  • After v1.4.1, the image format has changed to<align with docker hub>, e.g. "".
  1. If you insist on using Docker registry, you may increase the limit by authenticating and upgrading: .

SchemaError of ApplicationRevision CRD

SchemaError(dev.oam.core.v1beta1.ApplicationRevision.spec.referredObjects): array should have exactly one sub-item)

This could be a potential problem for k8s 1.19. Try to run the following command and see if it can help.

kubectl patch crd --type json -p='[{"op": "remove", "path": "/spec/versions/1/schema/openAPIV3Schema/properties/spec/properties/referredObjects/x-kubernetes-preserve-unknown-fields"}]'

How to change the admin password of VelaUX?

If you're using v1.3, the default password is in the secret:

kubectl get secret admin -n vela-system

If you're using v1.4+, the default password is VelaUX12345. After you first log in, you must change the password. If you forget the password, you could delete the admin user from the database, then restart the API server. The admin user will regenerate.

# Delete the admin user. If you use the MongoDB, you should delete from the MongoDB.
kubectl delete cm usr-admin -n kubevela

# Restart the API server and regenerate the admin user
kubectl delete pod -l -n vela-system

How can I build my own addon registry?

How does KubeVela support stateful workload?

We recommend you to use CRD Operator for stateful workload. If you just want to use StatefulSet, you can refer to this blog to build your own easily.

How to deal with slow multi-cluster requests?

There are several common possible reasons for slow multi-cluster requests.

  1. Your managed cluster is far from your hub cluster. For example, one in Beijing and another one in London. This is hard to speed up. You might need to find methods to build stable network connections between them. KubeVela currently cannot help it.

  2. Your cluster-gateway uses version <= 1.3.2. There is a rate limiter in cluster-gateway in old versions. Therefore, if you have lots of multi-cluster requests, they will be blocked at cluster-gateway. Upgrading cluster-gateway to a newer version could solve it.

  3. Your cluster-gateway hits the resource limits. For example, the CPU/Memory usage is high. This could happen if you have lots of clusters. You can raise the resource configuration for the cluster-gateway.