Skip to content

Commit

Permalink
Spelling correction in README.md
Browse files Browse the repository at this point in the history
Replacement of k3s-io#170, now signed-off for DCO.

Signed-off-by: Bert Roos <[email protected]>
  • Loading branch information
Bert-R authored and brandond committed Dec 12, 2023
1 parent cf4b87d commit b2596ed
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ supporting the [acceptance of K3s as a CNCF sandbox project](https://github.com/
A simple way to manage helm charts (v2 and v3) with Custom Resource Definitions in k8s.

## Manifests and Deploying
The `./manifests` folder contains useful YAML manifests to use for deploying and developing the Helm Controller. This simply YAML deployment creates a HelmChart CRD + a Deployment using the `rancher/helm-controller` container. The YAML might need some modifications for your environment so read below for Namespaced vs Cluster deployments and how to use them properly.
The `./manifests` folder contains useful YAML manifests to use for deploying and developing the Helm Controller. This simple YAML deployment creates a HelmChart CRD + a Deployment using the `rancher/helm-controller` container. The YAML might need some modifications for your environment so read below for Namespaced vs Cluster deployments and how to use them properly.

#### Namespaced Deploys
Use the `deploy-namespaced.yaml` to create a namespace and add the Helm Controller and CRD to that namespace locking down the Helm Controller to only see changes to CRDs within that namespace. This is defaulted to `helm-controller` so update the YAML to your needs before running `kubectl create`
Expand Down

0 comments on commit b2596ed

Please sign in to comment.