canonical / canonical/cloud-init
[enhancement]: Add ability to pass specific ipv4/ipv6 options to network renderers
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 1.1k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 18
Description
# Enhancement
Please see the discussion in https://github.com/canonical/cloud-init/pull/4474 . Currently network renderers use various default settings for ip configurations. For example, settings for `IPV4_FAILURE_FATAL` and `IPV6_FAILURE_FATAL` in ifcfg files and `may-fail` settings for nm keyfiles. See tables 70 and 71 in https://people.freedesktop.org/~lkundrak/nm-docs/nm-settings-ifcfg-rh.html for various ipv4 and ipv6 options that can be set and how they translate to ifcfg files and keyfiles. Unfortunately, the defaults may not be appropriate for some use cases and it may be required to override the default values with specific values for some of these settings. My ask here to add to cloud-init ability to override some of these values. For example it could be similar to `dhcpv6-override` and `dhcp4-override` options that are currently available https://netplan.readthedocs.io/en/latest/netplan-yaml/#dhcp-overrides . Since the above override options seems set in stone and we cannot add arbitrary options, we can introduce a new set of override options, like `ipv4-override` or `ipv6-override` that maybe passed on to the renderers and then renderers can consume it appropriately.
Contributor guide
Assessment
This issue has not been assessed yet.