-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Adding missing extra_fqdn support for operator that was supported previously #197
Conversation
…onrroller and External DNS
length(var.extra_fqdn) > 0 && var.enable_dummy_dns ? { | ||
"external-dns.alpha.kubernetes.io/hostname" = <<-EOF | ||
${local.fqdn}\,${join("\\,", var.extra_fqdn)}\,${local.fqdn} | ||
EOF |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason I use the local.fqdn
twice is because of a bug with external dns not reading this form of the annotation correctly:
external-dns.alpha.kubernetes.io/hostname: |
smooth-operator.sandbox-aws.wandb.ml,rough-operator.sandbox-aws.wandb.ml
In order to get around this, I added ${local.fqdn}
to the end which works just perfectly. 😢
time="2024-03-29T21:23:33Z" level=debug msg="Endpoints generated from ingress: default/wandb: [smooth-operator.sandbox-aws.wandb.ml 0 IN CNAME smooth-operator-alb-k8s-388333795.us-east-2.elb.amazonaws.com [] rough-operator.sandbox-aws.wandb.ml 0 IN CNAME smooth-operator-alb-k8s-388333795.us-east-2.elb.amazonaws.com [] smooth-operator.sandbox-aws.wandb.ml\n 0 IN CNAME smooth-operator-alb-k8s-388333795.us-east-2.elb.amazonaws.com []]"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That sure doesn't look perfect to me with a duplicated entry in the endpoints generated. Is there something goofy we're doing with writing out these annotations that it ends up in an incompatible format or is it just good ol' externaldns madness?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
External DNS madness. I am actually creating an issue now in https://github.com/kubernetes-sigs/external-dns/issues. Will comment when I create it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approved but only merge after #196 is in
### [4.7.1](v4.7.0...v4.7.1) (2024-04-17) ### Bug Fixes * Adding missing extra_fqdn support for operator that was supported previously ([#197](#197)) ([7adf420](7adf420))
This PR is included in version 4.7.1 🎉 |
This needs to go in after https://github.com/wandb/terraform-aws-wandb/pull/196/files
Given these vars as a constant:
I went from
to:
with:
Step 2. Enable
Then I enabled:
module.wandb_infra.module.app_lb.aws_route53_record.alb
gets replaced.module.wandb_infra.module.wandb.helm_release.wandb
will be updated in-place with the following:module.wandb_infra.module.app_eks.module.external_dns.helm_release.external_dns
will getOutcome: