You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
k8gb looks for the status.loadbalancer.ingress.hostname field to determine how to populate the global dns record. this corresponds to the status.ingress.routeCanonicalHostname field in the corresponding route.
This hostname is actually an wildcard entry and cannot be resolved (or at least it cannot be resolved when running on AWS). As a result k8gb is unable to populate the global record.
A fix to this solution would be to make the wildcard name resolvable.
A more immediate but inelegant workaround would be for k8gb to try to resolve anything.{status.ingress.routeCanonicalHostname}
The text was updated successfully, but these errors were encountered:
k8gb looks for the
status.loadbalancer.ingress.hostname
field to determine how to populate the global dns record. this corresponds to thestatus.ingress.routeCanonicalHostname
field in the corresponding route.This hostname is actually an wildcard entry and cannot be resolved (or at least it cannot be resolved when running on AWS). As a result k8gb is unable to populate the global record.
A fix to this solution would be to make the wildcard name resolvable.
A more immediate but inelegant workaround would be for k8gb to try to resolve
anything.{status.ingress.routeCanonicalHostname}
The text was updated successfully, but these errors were encountered: