Skip to content

Conversation

@Elvinra
Copy link

@Elvinra Elvinra commented Dec 12, 2025

Description

This MR updates the NGINX ingress controller documentation to include the service.beta.kubernetes.io/scw-loadbalancer-ip-ids annotation, which allows users to configure both IPv4 and IPv6 flexible IPs for their Load Balancer.

Source : scaleway/scaleway-cloud-controller-manager#176

@Elvinra Elvinra requested a review from bene2k1 as a code owner December 12, 2025 14:55
@bene2k1 bene2k1 added status: tech review Waiting for technical review do not merge PR that shouldn't be merged before a specific date (eg release) labels Dec 15, 2025
<Message type="note">
- Replace `195.154.72.226` with your reserved flexible IP. Omitting `loadBalancerIP` results in an ephemeral IP.
- **Option 1 - `loadBalancerIP`**: Replace `195.154.72.226` with your reserved flexible IPv4 address. This field only supports a single IPv4 address.
- **Option 2 - `service.beta.kubernetes.io/scw-loadbalancer-ip-ids`**: Use this annotation for IPv4 and IPv6 support. It accepts a single IP ID or a comma-delimited list (at most one IPv4 and one IPv6). At least one IPv4 is required. This annotation takes priority over `loadBalancerIP`.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- **Option 2 - `service.beta.kubernetes.io/scw-loadbalancer-ip-ids`**: Use this annotation for IPv4 and IPv6 support. It accepts a single IP ID or a comma-delimited list (at most one IPv4 and one IPv6). At least one IPv4 is required. This annotation takes priority over `loadBalancerIP`.
- **Option 2 - `service.beta.kubernetes.io/scw-loadbalancer-ip-ids`**: Use this annotation for IPv4 and IPv6 support. It accepts a single IP ID or a comma-delimited list (at most one IPv4 and one IPv6). At least one IPv4 address is required. This annotation takes priority over `loadBalancerIP`.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge PR that shouldn't be merged before a specific date (eg release) status: tech review Waiting for technical review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants