FAQ

    Refer to the comparison details.

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

    • 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.

    You can use https://kubevela.net/ as a faster alternative.

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

    • Before v1.4.1, the image format is , e.g. “ghcr.io/kubevela/kubevela/vela-core:latest”.
    • After v1.4.1, the image format has changed to , e.g. “ghcr.io/kubevela/oamdev/vela-core:latest”.

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

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

    If you’re using v1.4+, the default password is . 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.

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

    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 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.