Guest cluster is 1.35.2 or lower and may have gateway-api packages pre installed.
For example VKr 1.35.2 has an older version of gateway-api ie 1.4.0.
After trying KB 422796 below error may be visible in the kube-apiserver on the Supervisor cluster.
# clusterbootstraps.run.tanzu.vmware.com "<cluster-bootstrap-name>" was not valid:
# * spec.additionalPackages: Invalid value: "gateway-api.tanzu.vmware.com.1.4.0+vmware.2-tkg.1": Based on the ClusterbootstrapTemplate's additional packages, expect to upgrade the referenced package gateway-api.tanzu.vmware.com.1.4.0+vmware.2-tkg.1 to gateway-api.tanzu.vmware.com, but cannot find the corresponding package in the updated Clusterbootstrap. The deletion of packages that still in ClusterbootstrapTemplate is not allowed
vCenter: 8.0.3 24853646
ESXi: VMware ESXi, 8.0.3, 24859861
VKS: 3.6.2+v1.35
Supervisor: v1.30.10+vmware.1-fips-vsc0.1.12-24799161
Guest cluster k8s version: v1.35.2---vmware.1-vkr.3
For guest clusters on VKr 1.35.2 the opt-out via custom ClusterBootstrap as per KB 422796 is possible with some manual workarounds.
For example there may be a webhook that may can block ClusterBootstrap modification.
However, this opt-out method while it may work is not officially documented.
Therefore modifications to system packages like gateway-api is not officially supported and therefore should not be attempted.
VKr 1.36 comes packaged with gateway-api v1.5.0 which will enable the use of ListenerSet.
Also note that in VKr 1.36 there is an official opt-out label method and this is specifically for the gateway-api package to be disabled so a higher version can be installed if required.