Skip to content

fix(lb): doc review #5159

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 24, 2025
Merged

fix(lb): doc review #5159

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions pages/load-balancer/how-to/create-manage-flex-ips.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ content:
paragraph: This page explains how to create and manage flexible IP addresses for your Scaleway Load Balancer
tags: load-balancer flexible-ip failover-ip flex-ip ip-address reverse reverse-dns
dates:
validation: 2024-12-16
validation: 2025-06-23
posted: 2023-12-05
categories:
- network
Expand All @@ -22,9 +22,9 @@ This page shows you how to use [Load Balancer flexible IP addresses](/load-balan

<Message type="note">
The following limitations apply to Load Balancer flexible IPs:
- A public Load Balancer must have an IPv4 address, and optionally an IPv6 address as well. It cannot have only an IPv6 address.
- A public Load Balancer must have an IPv4 address, and can optionally have an IPv6 address as well. It cannot have only an IPv6 address.
- You cannot currently change the flexible IP address of an existing Load Balancer, that is to say you cannot detach its flexible IP after creation to attach a different one. You can attach a flexible IPv6 to a Load Balancer that does not already have one, but you cannot modify or change this address once attached.
- Flexible IPs are associated with a particular product and cannot be moved to a different type of resource. For example, a flexible IP for Load Balancer can be used with another Load Balancer, but it cannot be used with other resource types like Instances or Elastic Metal servers.
- Flexible IPs are associated with a particular product and cannot be moved to a different type of resource. For example, a flexible IP for Load Balancer can be used with another Load Balancer in the same AZ, but it cannot be used with other resource types like Instances or Elastic Metal servers.
</Message>

<Macro id="requirements" />
Expand Down
4 changes: 2 additions & 2 deletions pages/load-balancer/reference-content/public-private-accessibility.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,15 +1,15 @@
---
meta:
title: Public vs private Load Balancers
description: Learn how to choose an appropriate accessibility setting for your Scaleway Load Balancer, favouring security and isolating with a private Load Balancer, or public accessibility over the internet with a public Load Balancer.
description: Learn how to choose an appropriate accessibility setting for your Scaleway Load Balancer, favoring security and isolating with a private Load Balancer, or public accessibility over the internet with a public Load Balancer.
h1: Public vs private Load Balancers
paragraph: Learn how to choose an appropriate accessibility setting for your Scaleway Load Balancer, favoring security and isolating with a private Load Balancer, or public accessibility over the internet with a public Load Balancer.
tags: load-balancer public private accessibility
categories:
- load-balancer
- network
dates:
validation: 2024-12-16
validation: 2025-06-23
posted: 2024-06-14
---

Expand Down