File tree 1 file changed +4
-4
lines changed
1 file changed +4
-4
lines changed Original file line number Diff line number Diff line change @@ -30,7 +30,7 @@ You can either build binary from source, or just download pre-built binary.
30
30
## Usage
31
31
32
32
1 . Ensure ` kubectl ` and ` helm ` are available in ` $PATH `
33
- 2 . Prepare a ** manifests directory** , see below
33
+ 2 . Prepare a ** resource directory** , see below
34
34
3 . Run ` ezdeploy `
35
35
36
36
## Options
@@ -39,10 +39,10 @@ You can either build binary from source, or just download pre-built binary.
39
39
- ` --kubeconfig ` or ` KUBECONFIG ` , specify path to ` kubeconfig ` file
40
40
- ` KUBECONFIG_BASE64 ` , base64 encoded ` kubeconfig ` file content
41
41
42
- ## Layout of Manifests Directory
42
+ ## Layout of a Resource Directory
43
43
44
44
- Each top-level directory stands for a ** namespace**
45
- - Every manifest file in that directory, will be applied to that ** namespace**
45
+ - Every resource file in that directory, will be applied to that ** namespace**
46
46
47
47
For example:
48
48
@@ -78,7 +78,7 @@ kube-system/
78
78
` ezdeploy ` will create or update a ** release** named ` main ` , using ** chart** ` _helm/ingress-nginx ` , and ** values file**
79
79
` kube-system/primary.ingress-nginx.helm.yaml `
80
80
81
- ` ezdeploy ` also support values file in ` jsonnet `
81
+ ` ezdeploy ` also support values file in ` jsonnet ` , file name should be ` [RELEASE_NAME].[CHART_NAME].helm.jsonnet `
82
82
83
83
## Credits
84
84
You can’t perform that action at this time.
0 commit comments