Make Gateway Discovery work with GKE and kube-dns #140
Labels
area/feature
New feature or request
area/gcp
migrated-from-archive
Issues migrated from the archived KGO repository
Problem Statement
https://github.com/Kong/gateway-operator/pull/1261 enabled Gateway Discovery in ControlPlanes with Service
DNSStrategy
, setting the admin servicesspec.publishNotReadyAddresses
field to true. This means that the admin service endpoints are created before the ready probes of the pod are successful. This implementation allows us to solve the chicken-egg problem (caused by the enablement of the dataplane/status/ready
endpoint) that follows:This solution has been tested and has some problems in GKE
pod-ip-address.service-name.namespace.svc
addressProposed Solution
To make KGO work with GKE and kube-dns, we may want to do the follows:
--controlplane-dns-strategy
with default value "service" and allowed values {"service", "pod"}*.namespace.pod
subject instead of*.service-name.namespace.svc
Acceptance Criteria
The text was updated successfully, but these errors were encountered: