Appfile is as below:
Under the hood,
Appfile will build the image from source code, and then generate
Application resource with the image name.
Before learning about Appfile's detailed schema, we recommend you to get familiar with core concepts in KubeVela.
To learn about how to set the properties of specific workload type or trait, please use
vela show <TYPE | TRAIT>.
In the following workflow, we will build and deploy an example NodeJS app under examples/testapp/.
git clone and go to the testapp directory:
The example contains NodeJS app code, Dockerfile to build the app.
In the directory there is a vela.yaml which follows Appfile format supported by Vela. We are going to use it to build and deploy the app.
NOTE: please change
oamdevto your own registry account so you can push. Or, you could try the alternative approach in
Local testing without pushing image remotelysection.
Run the following command:
Check the status of the service:
If you have local kind cluster running, you may try the local push option. No remote container registry is needed in this case.
Add local option to
Then deploy the app to kind:
(Advanced) Check rendered manifests
By default, Vela renders the final manifests in
Then deploy Appfile again to update the application:
Congratulations! You have just deployed an app using
Play more with your app: