github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #554 from erikwilson/master 

Update README for helm controller changes
pull/558/head
Erik Wilson 2019-06-19 15:16:47 -07:00 committed by GitHub
parent 7ffe802a73 783d9d7bfc
commit ce9f43d45d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -111,7 +111,7 @@ Kubernetes in a manner similar to `kubectl apply`.
It is also possible to deploy Helm charts. k3s supports a CRD controller for installing charts. A YAML file specification can look as following (example taken from `/var/lib/rancher/k3s/server/manifests/traefik.yaml`):
```yaml
apiVersion: k3s.cattle.io/v1
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
name: traefik
@ -126,7 +126,7 @@ spec:
Keep in mind that `namespace` in your HelmChart resource metadata section should always be `kube-system`, because k3s deploy controller is configured to watch this namespace for new HelmChart resources. If you want to specify the namespace for the actual helm release, you can do that using `targetNamespace` key in the spec section:
```
apiVersion: k3s.cattle.io/v1
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
name: grafana
@ -149,6 +149,8 @@ spec:
Also note that besides `set` you can use `valuesContent` in the spec section. And it's okay to use both of them.
k3s versions <= v0.5.0 used `k3s.cattle.io` for the api group of helmcharts, this has been changed to `helm.cattle.io` for later versions.
Storage Backends
----------------