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
Ignition can fetch metadata from OpenStack's IPv4 metadata endpoint1. However, since OpenStack Victoria, the metadata service now supports both an IPv4 and an IPv6 endpoint2. In single-stack IPv6 environments we only have the IPv6 endpoint, which prevents ignition from fetching metadata.
Environment
OpenStack
Desired Feature
Add support for the IPv6 metadata endpoint to the OpenStack provider.
I think the implementation should be done internally and not per provider:
A provider defines a map of two endpoints ("v4" and "v6")
Ignition detects if the network runtime is ipv4 only, ipv6 only or dual-stack
The fetcher uses the associated endpoint
The challenge seats in 2) "Ignition detects if the runtime is ipv4 only, ipv6 only or dual-stack" - especially for systems where network setup is not immediate.
For example if we set "ipv6" only because "ipv4" was unreachable because of slow network setup, this would be incorrect.
Feature Request
Ignition can fetch metadata from OpenStack's IPv4 metadata endpoint1. However, since OpenStack Victoria, the metadata service now supports both an IPv4 and an IPv6 endpoint2. In single-stack IPv6 environments we only have the IPv6 endpoint, which prevents ignition from fetching metadata.
Environment
OpenStack
Desired Feature
Add support for the IPv6 metadata endpoint to the OpenStack provider.
Other Information
Footnotes
https://github.com/coreos/ignition/blob/7548ac6dafbb93fe89baf8853e97b71123cc5aed/internal/providers/openstack/openstack.go#L46-L53 ↩
https://docs.openstack.org/nova/2024.1/user/metadata.html ↩
The text was updated successfully, but these errors were encountered: