Skip to content

Services missing appProtocol definition #3435

Open
@szelenka

Description

@szelenka

Please ensure you do the following when reporting a bug:

  • Provide a concise description of what the bug is.
  • Provide information about your environment.
  • Provide clear steps to reproduce the bug.
  • Attach applicable logs. Please do not attach screenshots showing logs unless you are unable to copy and paste the log data.
  • Ensure any code / output examples are properly formatted for legibility.

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

  1. Install latest Crunchy PGO
  2. Provision a new Instance
  3. Inspect Services created for the Instance, notice the port is missing the appProtocol field.

EXPECTED

  1. When creating a service, I would expect the Crunchy PGO to populate the appProtocol field appropriately.

ACTUAL

  1. No appProtocol field is populated

Logs

n/a

Additional Information

n/a

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions