Update reference for helm-secrets to latest maintained fork (#1676)
* Update referance for helm-secrets to latest maintained fork * Missed a referance in the docs to an older edition of helm secrets * Removed docker2 changes back to original method Co-authored-by: Nathan Flynn <nflynn@williamhill.co.uk> Co-authored-by: Yusuke Kuoka <ykuoka@gmail.com>
This commit is contained in:
		
							parent
							
								
									bf9f36b2bb
								
							
						
					
					
						commit
						14a83e7cbe
					
				|  | @ -46,7 +46,7 @@ RUN set -x && \ | ||||||
|     mv kustomize /usr/local/bin/kustomize |     mv kustomize /usr/local/bin/kustomize | ||||||
| 
 | 
 | ||||||
| RUN helm plugin install https://github.com/databus23/helm-diff --version v3.1.3 && \ | RUN helm plugin install https://github.com/databus23/helm-diff --version v3.1.3 && \ | ||||||
|     helm plugin install https://github.com/futuresimple/helm-secrets && \ |     helm plugin install https://github.com/jkroepke/helm-secrets && \ | ||||||
|     helm plugin install https://github.com/hypnoglow/helm-s3.git && \ |     helm plugin install https://github.com/hypnoglow/helm-s3.git && \ | ||||||
|     helm plugin install https://github.com/aslafy-z/helm-git.git |     helm plugin install https://github.com/aslafy-z/helm-git.git | ||||||
| 
 | 
 | ||||||
|  |  | ||||||
|  | @ -554,7 +554,8 @@ Note that `delete` doesn't purge releases. So `helmfile delete && helmfile sync` | ||||||
| The `secrets` parameter in a `helmfile.yaml` causes the [helm-secrets](https://github.com/jkroepke/helm-secrets) plugin to be executed to decrypt the file. | The `secrets` parameter in a `helmfile.yaml` causes the [helm-secrets](https://github.com/jkroepke/helm-secrets) plugin to be executed to decrypt the file. | ||||||
| 
 | 
 | ||||||
| To supply the secret functionality Helmfile needs the `helm secrets` plugin installed. For Helm 2.3+ | To supply the secret functionality Helmfile needs the `helm secrets` plugin installed. For Helm 2.3+ | ||||||
| you should be able to simply execute `helm plugin install https://github.com/jkroepke/helm-secrets --version v3.5.0`. | you should be able to simply execute `helm plugin install https://github.com/jkroepke/helm-secrets | ||||||
|  | `. | ||||||
| 
 | 
 | ||||||
| ### test | ### test | ||||||
| 
 | 
 | ||||||
|  | @ -852,7 +853,7 @@ Environment Secrets (not to be confused with Kubernetes Secrets) are encrypted v | ||||||
| You can list any number of `secrets.yaml` files created using `helm secrets` or `sops`, so that | You can list any number of `secrets.yaml` files created using `helm secrets` or `sops`, so that | ||||||
| Helmfile could automatically decrypt and merge the secrets into the environment values. | Helmfile could automatically decrypt and merge the secrets into the environment values. | ||||||
| 
 | 
 | ||||||
| First you must have the [helm-secrets](https://github.com/futuresimple/helm-secrets) plugin installed along with a | First you must have the [helm-secrets](https://github.com/jkroepke/helm-secrets) plugin installed along with a | ||||||
| `.sops.yaml` file to configure the method of encryption (this can be in the same directory as your helmfile or | `.sops.yaml` file to configure the method of encryption (this can be in the same directory as your helmfile or | ||||||
| in the sub-directory containing your secrets files). | in the sub-directory containing your secrets files). | ||||||
| 
 | 
 | ||||||
|  |  | ||||||
|  | @ -1,6 +1,6 @@ | ||||||
| # Secrets  | # Secrets  | ||||||
| 
 | 
 | ||||||
| helmfile can handle secrets using [helm-secrets](https://github.com/zendesk/helm-secrets) plugin or using remote secrets storage  | helmfile can handle secrets using [helm-secrets](https://github.com/jkroepke/helm-secrets) plugin or using remote secrets storage  | ||||||
| (everything that package [vals](https://github.com/variantdev/vals) can handle vault, AWS SSM etc)   | (everything that package [vals](https://github.com/variantdev/vals) can handle vault, AWS SSM etc)   | ||||||
| This section will describe the second use case.  | This section will describe the second use case.  | ||||||
| 
 | 
 | ||||||
|  |  | ||||||
		Loading…
	
		Reference in New Issue