github/kubevela
1
0
Fork 0
mirror of https://github.com/kubevela/kubevela.git synced 2026-08-27 16:17:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1118 from yangsoon/fixdoc

Browse Source 
fix:fix doc, error link and format
This commit is contained in:
Jianbo Sun
2021-03-02 13:37:23 +08:00
committed by GitHub
parent a8337921bc 488341398a
commit 84f34e3f01
4 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/concepts.md
+1 -1
View File
@@ -66,7 +66,7 @@ We also reference workload type and trait as "application/capability modules" in
## Definitions
Both the schemas of workload settings and trait properties in `Application` are enforced by application modules that are pre-defined separately in a set of definition objects. The platform teams or component providers are responsible for registering and managing definitions in target cluster following [workload definition](https://github.com/oam-dev/spec/blob/master/4.workload_definitions.md) and [trait definition](https://github.com/oam-dev/spec/blob/master/6.traits.md) specifications in Open Application Model (OAM).
Both the schemas of workload settings and trait properties in `Application` are enforced by application modules that are pre-defined separately in a set of definition objects. The platform teams or component providers are responsible for registering and managing definitions in target cluster following [workload definition](https://github.com/oam-dev/spec/blob/master/4.workload_types.md) and [trait definition](https://github.com/oam-dev/spec/blob/master/6.traits.md) specifications in Open Application Model (OAM).
Currently, KubeVela supports [CUE](https://github.com/cuelang/cue) as the module type in definitions, with more types such as Helm and Terraform are coming in following releases. In the case of Helm, a chart could be directly referenced as a component type in `Application` and its `values.yaml` will become the component's specification.
docs/en/cue/trait.md
+1 -1
View File
@@ -384,7 +384,7 @@ spec:
containers: [{
name: context.name
image: parameter.image
ports:[{containerPort: parameter.port}]
ports: [{containerPort: parameter.port}]
envFrom: [{
configMapRef: name: context.name + "game-config"
}]
docs/en/install.md
+1 -1
View File
@@ -88,7 +88,7 @@ These steps will install KubeVela controller and its dependency.
like `0.4.0-rc-master`.
```shell script
helm search repo kubevela/vela-core -l --devel
$ helm search repo kubevela/vela-core -l --devel
NAME CHART VERSION APP VERSION DESCRIPTION
kubevela/vela-core 0.4.0-rc-master 0.4.0-rc-master A Helm chart for KubeVela core
kubevela/vela-core 0.3.2 0.3.2 A Helm chart for KubeVela core
docs/en/platform-engineers/workload-type.md
+3 -2
View File
@@ -74,14 +74,15 @@ Note that OpenFaaS also requires a namespace and secret configured before first-
<details>
```bash
# create namespace
$ kubectl apply -f https://raw.githubusercontent.com/openfaas/faas-netes/master/namespaces.yml
# generate a random password
$ PASSWORD=$(head -c 12 /dev/urandom | shasum| cut -d' ' -f1)
$ kubectl -n openfaas create secret generic basic-auth \
--from-literal=basic-auth-user=admin \
--from-literal=basic-auth-password="$PASSWORD"
$ kubectl apply -f https://raw.githubusercontent.com/openfaas/faas-netes/master/namespaces.yml
```
</details>