File tree 4 files changed +29
-0
lines changed
4 files changed +29
-0
lines changed Original file line number Diff line number Diff line change @@ -114,6 +114,15 @@ $ helm upgrade -i flagger flagger/flagger \
114
114
--set meshProvider=traefik
115
115
```
116
116
117
+ If you need to add labels to the flagger deployment or pods, you can pass the labels as parameters as shown below.
118
+
119
+ ``` console
120
+ helm upgrade -i flagger flagger/flagger \
121
+ <other parameters> \
122
+ --set podLabels.<labelName>=<labelValue> \
123
+ --set deploymentLabels.<labelName>=<labelValue>
124
+ ```
125
+
117
126
The [ configuration] ( #configuration ) section lists the parameters that can be configured during installation.
118
127
119
128
## Uninstalling the Chart
@@ -186,6 +195,8 @@ The following tables lists the configurable parameters of the Flagger chart and
186
195
| ` podDisruptionBudget.minAvailable ` | The minimal number of available replicas that will be set in the PodDisruptionBudget | ` 1 ` |
187
196
| ` noCrossNamespaceRefs ` | If ` true ` , cross namespace references to custom resources will be disabled | ` false ` |
188
197
| ` namespace ` | When specified, Flagger will restrict itself to watching Canary objects from that namespace | ` "" ` |
198
+ | ` deploymentLabels ` | Labels to add to Flagger deployment | ` {} ` |
199
+ | ` podLabels ` | Labels to add to pods of Flagger deployment | ` {} ` |
189
200
190
201
Specify each parameter using the ` --set key=value[,key=value] ` argument to ` helm upgrade ` . For example,
191
202
Original file line number Diff line number Diff line change @@ -9,6 +9,11 @@ metadata:
9
9
app.kubernetes.io/managed-by : {{ .Release.Service }}
10
10
app.kubernetes.io/instance : {{ .Release.Name }}
11
11
app.kubernetes.io/version : {{ .Chart.AppVersion }}
12
+ {{- if .Values.deploymentLabels }}
13
+ {{- range $key, $value := .Values.deploymentLabels }}
14
+ {{ $key }}: {{ $value | quote }}
15
+ {{- end }}
16
+ {{- end }}
12
17
{{- with .Values.annotations }}
13
18
annotations :
14
19
{{- toYaml . | nindent 4 }}
Original file line number Diff line number Diff line change @@ -195,8 +195,12 @@ podDisruptionBudget:
195
195
enabled : false
196
196
minAvailable : 1
197
197
198
+ # Additional labels to be added to pods
198
199
podLabels : {}
199
200
201
+ # Additional labels to be added to deployments
202
+ deploymentLabels : { }
203
+
200
204
noCrossNamespaceRefs : false
201
205
202
206
# Placeholder to supply additional volumes to the flagger pod
Original file line number Diff line number Diff line change @@ -81,6 +81,15 @@ $ helm upgrade -i flagger flagger/flagger \
81
81
--set metricsServer=http://osm-prometheus.osm-system.svc:7070
82
82
```
83
83
84
+ If you need to add labels to the flagger deployment or pods, you can pass the labels as parameters as shown below.
85
+
86
+ ``` console
87
+ helm upgrade -i flagger flagger/flagger \
88
+ <other parameters> \
89
+ --set podLabels.<labelName>=<labelValue> \
90
+ --set deploymentLabels.<labelName>=<labelValue>
91
+ ```
92
+
84
93
You can install Flagger in any namespace as long as it can talk to the Prometheus service on port 9090.
85
94
86
95
For ingress controllers, the install instructions are:
You can’t perform that action at this time.
0 commit comments