public-cloud-roadmap
public-cloud-roadmap copied to clipboard
ovh
IPv6 support for Managed Kubernetes and LBaaS
As as Managed Kubernetes Service User I'd like to deploy IPv6 accessible Workloads to make them available in IPv6 only enabled environments.
This UseCase describes only the external accessibility of a kubernetes LoadBalancer service. It isn't mandatory, that the Pods can access IPv6 only ressources.
I want to deploy a backend application that is used by an iOS app. Apple requires that all resources accessed by an iOS app be accessible from a IPv6-only environment. Apple's internal test infrastructure is IPv6-only, and a growing number of mobile customers also rely on IPv6.
For my use case, it would be sufficient if an external IPv6 load balancer address is available.
I can fully support it. In 2022 it must be possible to setup the whole eco-system with Ipv6
@JacquesMrz Could you provide any feedback on if and when OVH will support IPv6 on managed Kubernetes as we are planning to migrate some apps requiring IPv6?
IPv6 is mandatory in our industry. We cannot make our deployment public without a public IPv6 address. Internal IPs don't matter.
I ended up with a SPOF gateway on a VPS, cause they actually have an IPv6 address.
I got an answer via OVHs support portal. At the moment nothing is planned regarding IPv6 but my ticket got forwarded to the department responsible for networking.
It's a pity that no one responds here and that this issue is not prioritized. IPv6 is extremely important in this day and age and should be supported by default.
Hello @lusu007
I confirm we cannot yet share an ETA regarding IPV6 support. We will be able to communicate an ETA after the migration of K8s LBaaS to Octavia, which will happen this year.
Hey @mhurtrel, thank you for bringing us up to date.
It would be cool if you could keep us updated on this issue. 😊
Two and a half months later: As a new customer, this really is a dealbreaker for me. Getting new products online should include providing basic access via the internet protocol version 6 and 4, while version 6 is the current standard. As living in Germany, ~70 % of users are accessing Google and therefore the internet via ipv6 (source). Most mobile networks support v6 now, and while most households are switching to fiber now, their ISPs are only offering DS behind CG-NAT (no public v4 anymore). Only providing access to my services via ipv4 results in higher latency and slower loading times in high demand time slots, in which my product target audience is supposed to use my products.
Ipv6 is a must. Any updates on this? Would also appreciate being a beta tester of some sort if already possible, as I really like your service and am generally not willing to switch our infrastructure to one of the giant competitors, g cloud or AWS.
