With the expansion of our sketch providers to shortly support Digital Ocean, which utilizes ipv6 differently from Linode, this is used to make sure we don't foobar our Digital Ocean setup.
Digital Ocean requires the usage of systemd-resolved and utilizes hard coded/static /etc/netplan/*.yaml setup.
The current disable-ipv6 role if applied to Digital Ocean will break the ansible flow specifically around when the system tries to update or do anything after that. Digital Ocean is reliant on systemd-resolved for its DNS resolution for internal and external.
Regardless of whether this role is applied in the playbook now, if its a Linode system it will run and if its anything else the role's tasks are skipped.
Changelog
With the expansion of our sketch providers to shortly support Digital Ocean, which utilizes ipv6 differently from Linode, this is used to make sure we don't foobar our Digital Ocean setup.
Digital Ocean requires the usage of systemd-resolved and utilizes hard coded/static
/etc/netplan/*.yaml
setup.The current disable-ipv6 role if applied to Digital Ocean will break the ansible flow specifically around when the system tries to update or do anything after that. Digital Ocean is reliant on systemd-resolved for its DNS resolution for internal and external.
Regardless of whether this role is applied in the playbook now, if its a Linode system it will run and if its anything else the role's tasks are skipped.
Improved