blob: 6ad80a94691280ddbe442a13d2535ca14f32ab54 [file] [log] [blame]
tmeneaucf41dc32017-10-16 15:23:05 -04001helm:
2 client:
3
4 #
5 # The version of the Helm client to install
6 #
7 # version: 2.6.2
8
9 #
10 # The hash for the helm client binary. You must calculate the hash for the
11 # version of the binary you install.
12 # Defaults to the SHA 256 hash for the helm-v2.6.2-linux-amd64.tar.gz
13 #
14 #
15 # The binary is downloaded from:
16 #
17 # https://storage.googleapis.com/kubernetes-helm/helm-v[[ client.version ]]-linux-amd64.tar.gz
18 #
19 # Here is an example command you can use to calculate the sha256 hash for
20 # the binary:
21 #
22 # ```
23 # shasum -a 256 /path/to/helm-v[[ client.version ]]-linux.amd64.tar.gz
24 # ```
25 #
26 # download_hash: sha256=ba807d6017b612a0c63c093a954c7d63918d3e324bdba335d67b7948439dbca8
tmeneaucf41dc32017-10-16 15:23:05 -040027
28 #
29 # Configurations to manage the cluster's Tiller installation
30 #
31 # tiller:
32 #
33 # Whether Tiller should be deployed to the kubernetes cluster as part of
34 # this formaul. Defaults to true.
35 #
36 # install: true
37
38 #
39 # The namespace to which Tiller should be installed (only used if
40 # `helm:client:tiller:install` is set to true).
41 # Defaults to `kube-system`
42 #
43 # naamespace: kube-system
44
45 #
46 # The host IP or name and port for an existing tiller installation that
47 # should be used by the Helm client. Defaults to Helm's default if
48 # unspecified.
49 #
50 # host:
51
52 #
53 # Configurations defined to manage the target minion's kubectl installation
54 #
55 # kubectl:
56 #
57 # Whether kubectl should be installed as part of this formula.
58 # Defaults to false
59 #
60 # install: false
61
62 #
63 # The version of the kubectl binary to install.
64 # Defaults to 1.6.7
65 #
66 # version: 1.6.7
67
68 #
69 # The hash for the kubectl binary version to install. You must calculate
70 # the hash for the version of the binary you install.
71 #
72 #
73 # The binary is downloaded from:
74 #
75 # https://dl.k8s.io/v[[ client.kubectl.version ]]/kubernetes-client-linux-amd64.tar.gz
76 #
77 #
78 # Defaults to the SHA 256 hash for the Linux distribution of version 1.6.7
79 #
80 # Here is an example command you can use to calculate the sha256 hash for
81 # the binary:
82 #
83 # ```
84 # shasum -a 256 /path/to/kubernetes-client-linux-amd64.tar.gz
85 # ```
86 #
87 # download_hash: sha256=54947ef84181e89f9dbacedd54717cbed5cc7f9c36cb37bc8afc9097648e2c91
88
89
90 #
91 # Configuration parameters that should be applied to the kubectl
92 # installation's kubeconfig. Not that this will only be applied to the
93 # kubectl installation managed by this formula.
94 #
95 # While the kubectl tool can be configured to connect to multiple
96 # clusters and allow switching between cluster contexts, this kubectl
97 # configuration managed by this formula will only be configured with
98 # the cluster context details used by this formula.
99 #
100 # config:
101 # cluster:
102 # server: https://kubernetes.example.com
103 # certificate-authority-data: base64_of_ca_certificate
104 # cluster_name: kubernetes.example
105 # context_name: kubernetes-example
106 # user:
107 # username: admin
108 # password: uberadminpass
109 # user_name: admin
110
111
112 #
113 # The mapping of repository names to urls that should be registered and
114 # kept up-to-date with the helm client
115 #
116 repos:
117 mirantisworkloads: https://mirantisworkloads.storage.googleapis.com/
118 incubator: https://kubernetes-charts-incubator.storage.googleapis.com/
119
120 #
121 # The listing of releases that should be managed by the formula. Note that
122 # if configured, the releases listed under this `helm:client:releases` key
123 # will be used as an authoritative, exclusive listing of the releases that
124 # should be configured and deployed to the Tiller installation; any
125 # release existing in the tiller cluster that is not configured here
126 # **will be deleted**
127 #
128 releases:
129 zoo1:
130
131 #
132 # The name of the release
133 #
134 name: my-zookeeper
135
136 #
137 # The repository name and chart name combination for the chart to
138 # release
139 #
140 chart: mirantisworkloads/zookeeper
141
142 #
143 # The version of the helm chart to install
144 #
145 version: 1.2.0
146
147 #
148 # The namespace to which the release should be deployed
149 #
150 namespace: helm-example-namespace
151
152 #
153 # Configuration values that should be supplied to the chart.
154 #
155 values:
156 logLevel: INFO