Does OctoDNS handle weighted Route53 records? about octodns-route53

[ross]

• I can't find a way to generate the right YAML.

Weighted records are configured in octoDNS with dyanmic, see https://github.com/octodns/octodns/blob/main/docs/dynamic_records.md. In this case that'd look something like:

test1:
  dynamic:
    pools:
      main:
        values:
          - value: 192.169.0.1
            weight: 10
          - value: 192.169.0.2
            weight: 15
    rules:
      - pool: main
  type: A
  values:
    - 192.169.0.1
    - 192.169.0.2

2. I used "octodns-dump" in order to dump the 2 records and shows how the Yaml was generetad but the command nevers dumped the records with "weighted".

octoDNS tries to unify behaviors across providers and thus doesn't support all possible setups so the manually created weighted set won't be imported if it doesn't match how an octoDNS created record would look.

In the case above the dynamic section tells octoDNS what to create for providers that support the advanced dynamic features (like Route53.) The plain values sections tells it what to do when pushed to providers that don't support the dynamic features.

[ross]

Usually, we used only records with weight (as I mentionned it in my first post) and that's all.
I need to check if the result is the same ;)

so long as there are no geo-rules the resulting effect should be roughly the same. You may also want to look at the status configuration options to avoid the need for health checks if you don't care about the health of the IPs.

The documentation says we could use "1 and 255" but if "you want to stop sending traffic to a resource, you can change the weight for that record to 0.".

I've always preferred to drain by disabling the health check for an IP/site rather than making DNS changes for every operational thing like that. So I would use a healthcheck for the site and then add support fo manually causing the healthcheck to fail, even when the site/ip is fine and will serve requests. This will allow a graceful drain form the application rather than with DNS change.

If you'd prefer to make DNS changes then the best bet is to remove the record rather than set it's weight to 0. Not all providers support a 0 weight record so octoDNS doesn't.

[lbrachet]

Hello Ross,

Thanks a lot for your answer, it helped me!

The way OctoDNS configures R53 is quite different: there is a Routing Policy = Geolocation with Failover Primary / Secondary.

Usually, we used only records with weight (as I mentionned it in my first post) and that's all.
I need to check if the result is the same ;)

Last question: R53 handles weight from 0 but I can't set this value, I received:

- invalid weight "0" in pool "main" value 2

The documentation says we could use "1 and 255" but if "you want to stop sending traffic to a resource, you can change the weight for that record to 0.".
I don't know if this setting (to 0) is available with OctoDNS?

Thanks.