Once SRVKS-702 is fixed, we will start using Kourier Gateway with service type ClusterIP.

It should not effect on users in general as they should access to the OpenShift Route deployed in front of the Kourier Gateway since our initial release.
However, some users might access to the Kourier Gateway directory and this change might have impact on them. So we should announce the change as well as guideline how to undo the change in the release-note.

In addition to the release note,  Interacting with a serverless application using HTTP2 and gRPC  needs to undo the change, so we should add the note in two places.

Suggested wording (two places in the doc)

1. In 1.18 release note

Kourier Gateway will start to default the service type to ClusterIP as OpenShift Route is placed in front of the service.

If you think this change might negatively impact your existing workloads, you can undo it before upgrading to 1.18 by adding the following to your KnativeServing:

spec:
  ingress:
    kourier:
      service-type: LoadBalancer

2. In Interacting with a serverless application using HTTP2 and gRPC

IMPORTANT

This method needs to expose Kourier Gateway by LoadBalancer service type. You can configure the service type by adding the following setting to your KnativeServing.

spec:
  ingress:
    kourier:
      service-type: LoadBalancer