github/flagger
1
0
Fork 0
mirror of https://github.com/fluxcd/flagger.git synced 2026-04-15 06:57:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1185 from philnichol/adding-appprotocol

Browse Source 
feat: Add an optional `appProtocol` field to `spec.service`
This commit is contained in:
Sanskar Jaiswal
2022-05-19 19:26:49 +05:30
committed by GitHub
parent c03d138cd0 d79898848e
commit 560f884cc0
6 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/gitbook/usage/how-it-works.md
+2
View File
@@ -134,6 +134,7 @@ spec:
name: podinfo
port: 9898
portName: http
appProtocol: http
targetPort: 9898
portDiscovery: true
```
@@ -142,6 +143,7 @@ The container port from the target workload should match the `service.port` or `
The `service.name` is optional, defaults to `spec.targetRef.name`.
The `service.targetPort` can be a container port number or name.
The `service.portName` is optional (defaults to `http`), if your workload uses gRPC then set the port name to `grpc`.
The `service.appProtocol` is optional, more details can be found [here](https://kubernetes.io/docs/concepts/services-networking/service/#application-protocol).
If port discovery is enabled, Flagger scans the target workload and extracts the containers ports
excluding the port specified in the canary service and service mesh sidecar ports.