Please ensure you do the following when reporting a bug:
Overview
Kubernetes v1.18+ introduced Application Protocol for all Services. This is a simple field called appProtocol which identifies the application protocol being used on that service port.
The services created by the v5.2.0 PGO does not include these fields, which prevents other services looking for them to work with the Crunchy PGO. Such as Istio:
https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/#explicit-protocol-selection
Environment
Please provide the following details:
- Platform: Kubernetes
- Platform Version: 1.22
- PGO Image Tag: ubi8-5.2.0-0
- Postgres Version 14
- Storage: PVC
Steps to Reproduce
- Install latest Crunchy PGO
- Provision a new Instance
- Inspect Services created for the Instance, notice the
port is missing the appProtocol field.
EXPECTED
- When creating a service, I would expect the Crunchy PGO to populate the
appProtocol field appropriately.
ACTUAL
- No
appProtocol field is populated
Logs
n/a
Additional Information
n/a
Please ensure you do the following when reporting a bug:
Overview
Kubernetes v1.18+ introduced Application Protocol for all Services. This is a simple field called
appProtocolwhich identifies the application protocol being used on that service port.The services created by the v5.2.0 PGO does not include these fields, which prevents other services looking for them to work with the Crunchy PGO. Such as Istio:
https://istio.io/latest/docs/ops/configuration/traffic-management/protocol-selection/#explicit-protocol-selection
Environment
Please provide the following details:
Steps to Reproduce
portis missing theappProtocolfield.EXPECTED
appProtocolfield appropriately.ACTUAL
appProtocolfield is populatedLogs
n/a
Additional Information
n/a