You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/gitbook/usage/how-it-works.md
+5
Original file line number
Diff line number
Diff line change
@@ -147,6 +147,7 @@ spec:
147
147
appProtocol: http
148
148
targetPort: 9898
149
149
portDiscovery: true
150
+
headless: false
150
151
```
151
152
152
153
The container port from the target workload should match the `service.port` or `service.targetPort`.
@@ -155,6 +156,7 @@ The `service.targetPort` can be a container port number or name.
155
156
The `service.portName` is optional (defaults to `http`), if your workload uses gRPC then set the port name to `grpc`.
156
157
The `service.appProtocol` is optional, more details can be found [here](https://kubernetes.io/docs/concepts/services-networking/service/#application-protocol).
157
158
159
+
158
160
If port discovery is enabled, Flagger scans the target workload and extracts the containers ports
159
161
excluding the port specified in the canary service and service mesh sidecar ports.
160
162
These ports will be used when generating the ClusterIP services.
@@ -204,6 +206,9 @@ Note that the `apex` annotations are added to both the generated Kubernetes Serv
204
206
generated service mesh/ingress object. This allows using external-dns with Istio `VirtualServices`
205
207
and `TraefikServices`. Beware of configuration conflicts [here](../faq.md#ExternalDNS).
206
208
209
+
If you want for the generated Kubernetes ClusterIP services to be [headless](https://kubernetes.io/docs/concepts/services-networking/service/#headless-services),
210
+
then set `service.headless` to true.
211
+
207
212
Besides port mapping and metadata, the service specification can
208
213
contain URI match and rewrite rules, timeout and retry polices:
0 commit comments