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