Add more about faq
Signed-off-by: Jianbo Sun <jianbo.sjb@alibaba-inc.com>
This commit is contained in:
Jianbo Sun
parent
df03a1ae8e
commit
2fea67389a
|
|
@ -2,48 +2,11 @@
|
|||
title: FAQ
|
||||
---
|
||||
|
||||
## What is the difference between KubeVela and project-X ?
|
||||
### What is the difference between KubeVela and project-X ?
|
||||
|
||||
Refer to the [comparison details](https://kubevela.io/docs/#kubevela-vs-other-software).
|
||||
|
||||
## 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](https://github.com/orgs/kubevela/packages) for more details. Use it like:
|
||||
|
||||
```
|
||||
docker pull ghcr.io/kubevela/kubevela/vela-core:latest
|
||||
```
|
||||
|
||||
2. Alibaba Container Registry also sponsor KubeVela community, you can use `acr.kubevela.net/` as prefix, acr has a sync for each KubeVela official images. Use it like:
|
||||
|
||||
```
|
||||
docker pull acr.kubevela.net/oamdev/vela-core:latest
|
||||
```
|
||||
|
||||
* You can check if the error occurs by:
|
||||
|
||||
Check the logs of Pod kubevela-vela-core and found the issue as below.
|
||||
|
||||
```
|
||||
kubectl get pod -n vela-system -l app.kubernetes.io/name=vela-core
|
||||
```
|
||||
```console
|
||||
NAME READY STATUS RESTARTS AGE
|
||||
kubevela-vela-core-f8b987775-wjg25 0/1 - 0 35m
|
||||
```
|
||||
|
||||
>Error response from daemon: too many requests: You have reached your pull rate limit. You may increase the limit by
|
||||
>authenticating and upgrading: https://www.docker.com/increase-rate-limit
|
||||
|
||||
You can use github container registry instead.
|
||||
|
||||
```
|
||||
docker pull ghcr.io/kubevela/kubevela/vela-core:latest
|
||||
```
|
||||
|
||||
## Do yo support Crossplane, what's the difference between terraform and corssplane in KubeVela?
|
||||
### Do yo support Crossplane? What's the difference between terraform and Corssplane in KubeVela?
|
||||
|
||||
KubeVela natively support Crossplane as they're already CRDs, while terraform was not a CRD controller, so the KubeVela community author a [terraform controller](https://github.com/kubevela/terraform-controller) for integration. You can choose any of them as you wish.
|
||||
|
||||
|
|
@ -53,3 +16,22 @@ KubeVela natively support Crossplane as they're already CRDs, while terraform wa
|
|||
* 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
|
||||
|
||||
### The document website is very slow to access.
|
||||
|
||||
You can use https://kubevela.net/ as a faster alternative.
|
||||
|
||||
### 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](https://github.com/orgs/kubevela/packages) for more details. There're two kinds of format:
|
||||
|
||||
* Before v1.4.1, the image format is `ghcr.io/<git-repo>/vela-core:<version>`, e.g. "ghcr.io/kubevela/kubevela/vela-core:latest".
|
||||
* After v1.4.1, the image format has changed to `ghcr.io/kubevela/<align with docker hub>`, e.g. "ghcr.io/kubevela/oamdev/vela-core:latest".
|
||||
|
||||
2. Alibaba Container Registry also sponsor KubeVela community, you can use `acr.kubevela.net/` as prefix for the docker registry, acr has a sync for each KubeVela official images. Use it like `acr.kubevela.net/oamdev/vela-core:latest`.
|
||||
|
||||
3. If you insist on using Docker registry, you may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit .
|
||||
|
||||
|
|
@ -100,7 +100,8 @@ Choose `> Cluster: local | Namespace: vela-system | Component: velaux | Kind: Se
|
|||
|
||||
If you have loadbalaner or ingress, please refer to [VelaUX addon docs](./reference/addons/velaux) for more advanced installation ways.
|
||||
|
||||
VelaUX need authentication. Default username is `admin` and the password is `VelaUX12345`. Please must set and remember the new password after the first login.
|
||||
VelaUX need authentication. Default username is `admin` and the password is `VelaUX12345`.
|
||||
It requires you to override with a new password for the first login, please make sure to remember the new password.
|
||||
|
||||
## 3. Cleanup
|
||||
|
||||
|
|
|
|||
|
|
@ -185,11 +185,9 @@ After finished [the installation of VelaUX](./install#2-install-velaux), you can
|
|||
vela port-forward addon-velaux -n vela-system 8080:80
|
||||
```
|
||||
|
||||
* Check the password by:
|
||||
* VelaUX need authentication, default username is `admin` and the password is `VelaUX12345`.
|
||||
|
||||
```
|
||||
vela logs -n vela-system --name apiserver addon-velaux | grep "initialized admin username"
|
||||
```
|
||||
It requires you to override with a new password for the first login, please make sure to remember the new password.
|
||||
|
||||
* Check the resources deployed
|
||||
|
||||
|
|
|
|||
|
|
@ -2,48 +2,11 @@
|
|||
title: FAQ
|
||||
---
|
||||
|
||||
## What is the difference between KubeVela and project-X ?
|
||||
### What is the difference between KubeVela and project-X ?
|
||||
|
||||
Refer to the [comparison details](https://kubevela.io/docs/#kubevela-vs-other-software).
|
||||
|
||||
## 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](https://github.com/orgs/kubevela/packages) for more details. Use it like:
|
||||
|
||||
```
|
||||
docker pull ghcr.io/kubevela/kubevela/vela-core:latest
|
||||
```
|
||||
|
||||
2. Alibaba Container Registry also sponsor KubeVela community, you can use `acr.kubevela.net/` as prefix, acr has a sync for each KubeVela official images. Use it like:
|
||||
|
||||
```
|
||||
docker pull acr.kubevela.net/oamdev/vela-core:latest
|
||||
```
|
||||
|
||||
* You can check if the error occurs by:
|
||||
|
||||
Check the logs of Pod kubevela-vela-core and found the issue as below.
|
||||
|
||||
```
|
||||
kubectl get pod -n vela-system -l app.kubernetes.io/name=vela-core
|
||||
```
|
||||
```console
|
||||
NAME READY STATUS RESTARTS AGE
|
||||
kubevela-vela-core-f8b987775-wjg25 0/1 - 0 35m
|
||||
```
|
||||
|
||||
>Error response from daemon: too many requests: You have reached your pull rate limit. You may increase the limit by
|
||||
>authenticating and upgrading: https://www.docker.com/increase-rate-limit
|
||||
|
||||
You can use github container registry instead.
|
||||
|
||||
```
|
||||
docker pull ghcr.io/kubevela/kubevela/vela-core:latest
|
||||
```
|
||||
|
||||
## Do yo support Crossplane, what's the difference between terraform and corssplane in KubeVela?
|
||||
### Do yo support Crossplane? What's the difference between terraform and Corssplane in KubeVela?
|
||||
|
||||
KubeVela natively support Crossplane as they're already CRDs, while terraform was not a CRD controller, so the KubeVela community author a [terraform controller](https://github.com/kubevela/terraform-controller) for integration. You can choose any of them as you wish.
|
||||
|
||||
|
|
@ -53,3 +16,22 @@ KubeVela natively support Crossplane as they're already CRDs, while terraform wa
|
|||
* 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
|
||||
|
||||
### The document website is very slow to access.
|
||||
|
||||
You can use https://kubevela.net/ as a faster alternative.
|
||||
|
||||
### 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](https://github.com/orgs/kubevela/packages) for more details. There're two kinds of format:
|
||||
|
||||
* Before v1.4.1, the image format is `ghcr.io/<git-repo>/vela-core:<version>`, e.g. "ghcr.io/kubevela/kubevela/vela-core:latest".
|
||||
* After v1.4.1, the image format has changed to `ghcr.io/kubevela/<align with docker hub>`, e.g. "ghcr.io/kubevela/oamdev/vela-core:latest".
|
||||
|
||||
2. Alibaba Container Registry also sponsor KubeVela community, you can use `acr.kubevela.net/` as prefix for the docker registry, acr has a sync for each KubeVela official images. Use it like `acr.kubevela.net/oamdev/vela-core:latest`.
|
||||
|
||||
3. If you insist on using Docker registry, you may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit .
|
||||
|
||||
|
|
@ -100,7 +100,8 @@ Choose `> Cluster: local | Namespace: vela-system | Component: velaux | Kind: Se
|
|||
|
||||
If you have loadbalaner or ingress, please refer to [VelaUX addon docs](./reference/addons/velaux) for more advanced installation ways.
|
||||
|
||||
VelaUX need authentication. Default username is `admin` and the password is `VelaUX12345`. Please must set and remember the new password after the first login.
|
||||
VelaUX need authentication. Default username is `admin` and the password is `VelaUX12345`.
|
||||
It requires you to override with a new password for the first login, please make sure to remember the new password.
|
||||
|
||||
## 3. Cleanup
|
||||
|
||||
|
|
|
|||
|
|
@ -185,11 +185,9 @@ After finished [the installation of VelaUX](./install#2-install-velaux), you can
|
|||
vela port-forward addon-velaux -n vela-system 8080:80
|
||||
```
|
||||
|
||||
* Check the password by:
|
||||
* VelaUX need authentication, default username is `admin` and the password is `VelaUX12345`.
|
||||
|
||||
```
|
||||
vela logs -n vela-system --name apiserver addon-velaux | grep "initialized admin username"
|
||||
```
|
||||
It requires you to override with a new password for the first login, please make sure to remember the new password.
|
||||
|
||||
* Check the resources deployed
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue