public_git
/
helmfile
mirror of https://github.com/helmfile/helmfile.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

chore: documentation updates: grammar & rm whitespace (#1639)

This commit is contained in:
Zubair Haque 2024-07-21 01:31:41 -04:00 committed by GitHub
parent a1326d6971
commit fb7046292b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
3 changed files with 5 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/advanced-features.md
View File

@ -17,13 +17,13 @@ Helmfile integrates [vals]() to import configuration parameters from following b
See [Vals "Supported Backends"](https://github.com/helmfile/vals#supported-backends) for the full list of available backends. See [Vals "Supported Backends"](https://github.com/helmfile/vals#supported-backends) for the full list of available backends.
This feature was implemented in https://github.com/roboll/helmfile/pull/906. This feature was implemented in https://github.com/roboll/helmfile/pull/906.
If you're curious how it's designed and how it works, please consult the pull request. If you're curious about how it's designed and how it works, please review the pull request.
### Deploy Kustomizations with Helmfile ### Deploy Kustomizations with Helmfile
You can deploy [kustomize](https://github.com/kubernetes-sigs/kustomize) "kustomization"s with Helmfile. You can deploy [kustomize](https://github.com/kubernetes-sigs/kustomize) "kustomization"s with Helmfile.
Most of Kustomize operations that is usually done with `kustomize edit` can be done declaratively via Helm values.yaml files. Most Kustomize operations are usually done with `kustomize edit` and can be done declaratively via Helm `values.yaml` files.
Under the hood, Helmfile transforms the kustomization into a local chart in a temporary directory so that it can be `helm upgrade --install`ed. Under the hood, Helmfile transforms the kustomization into a local chart in a temporary directory so that it can be `helm upgrade --install`ed.

3
docs/remote-secrets.md
View File

@ -54,5 +54,4 @@ service:
login: svc-login # fetched from vault login: svc-login # fetched from vault
password: pass password: pass
``` ```

4
docs/shared-configuration-across-teams.md
View File

@ -1,6 +1,6 @@
# Shared Configuration Across Teams # Shared Configuration Across Teams
Assume you have a two or more teams, each works for a different internal or external service, like: Assume you have two or more teams, each work for a different internal or external service, like:
- Product 1 - Product 1
- Product 2 - Product 2
@ -30,7 +30,7 @@ releases:
# snip # snip
``` ```
This works, but what if you wanted to a separate cluster per service to achieve smaller blast radius? This works, but what if you wanted to a separate cluster per service to achieve a smaller blast radius?
Let's start by creating a `helmfile.yaml` for each service. Let's start by creating a `helmfile.yaml` for each service.