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
A panic occurs when there is an Ingress resource with a load balancer's address configured as a hostname. And this hostname is a CNAME to another record.
How to reproduce
An Ingress resource with the load balancer's address configured as a hostname:
Support checking the answers from Dig for CNAMEs, and ensure that any
CNAMEs returned are answered, recursively calling to resolve them if
not.
Closesk8gb-io#1782
Signed-off-by: Brandon Ewing <[email protected]>
A panic occurs when there is an Ingress resource with a load balancer's address configured as a hostname. And this hostname is a CNAME to another record.
How to reproduce
An Ingress resource with the load balancer's address configured as a hostname:
And where this hostname is a CNAME:
Fix
Support CNAME records in addition to A records:
k8gb/controllers/utils/dns.go
Line 68 in 40f7264
Additional bug
It would be great if the panic log message showed the line where it panics instead of the line of code where the logger emitted the message.
Reported in: https://cloud-native.slack.com/archives/C021P656HGB/p1732219873734419
The text was updated successfully, but these errors were encountered: