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
Copy file name to clipboardExpand all lines: pages/public_cloud/containers_orchestration/managed_kubernetes/expose_your_applications_using_a_load_balancer/guide.de-de.md
+40-18Lines changed: 40 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Expose your applications using OVHcloud Public Cloud Load Balancer
3
3
excerpt: "How to expose your applications hosted on Managed Kubernetes Service using the OVHcloud Public Cloud Load Balancer"
4
-
updated: 2025-02-17
4
+
updated: 2025-10-06
5
5
---
6
6
7
7
> [!warning]
@@ -27,9 +27,6 @@ To be able to deploy [Public Cloud Load Balancer](/links/public-cloud/load-balan
27
27
28
28
| Kubernetes versions |
29
29
| ------------------- |
30
-
| 1.26.4-3 >= |
31
-
| 1.27.12-1 >= |
32
-
| 1.28.8-1 >= |
33
30
| 1.29.3-3 >= |
34
31
| 1.30.2-1 >= |
35
32
@@ -70,9 +67,9 @@ If you have an existing/already deployed cluster and if:
70
67
71
68
When exposing your load balancer publicly (public-to-public or public-to-private):
72
69
73
-
- If it does not already exist, a single OVHcloud Gateway will be automatically created and billed for all Load Balancers spawned in the subnet <https://www.ovhcloud.com/de/public-cloud/prices/#10394>.
74
-
- A Public Floating IP will be used: <https://www.ovhcloud.com/de/public-cloud/prices/#10346>.
75
-
- Each Public Cloud Load Balancer is billed according to its flavor: <https://www.ovhcloud.com/de/public-cloud/prices/#10420>.
70
+
- If it does not already exist, a single OVHcloud Gateway will be automatically created and billed for all Load Balancers spawned in the subnet <https://www.ovhcloud.com/en-gb/public-cloud/prices/#10394>.
71
+
- A Public Floating IP will be used: <https://www.ovhcloud.com/en-gb/public-cloud/prices/#10346>.
72
+
- Each Public Cloud Load Balancer is billed according to its flavor: <https://www.ovhcloud.com/en-gb/public-cloud/prices/#10420>.
# Use `openstack loadbalancer flavor list` to get the full list of available flavors.
111
+
loadbalancer.ovhcloud.com/flavor: small # Name of a loadbalancer flavor, used in MKS Free ONLY.
112
+
loadbalancer.openstack.org/flavor-id: xxx # UUID of a loadbalancer flavor, used in MKS Standard ONLY.
113
113
spec:
114
114
ports:
115
115
- name: 80-80
@@ -155,7 +155,11 @@ metadata:
155
155
namespace: test-lb-ns
156
156
annotations:
157
157
loadbalancer.ovhcloud.com/class: "octavia"//not required for cluster running kubernetes versions >= 1.31
158
-
loadbalancer.ovhcloud.com/flavor: "medium"//optional, default = small
158
+
159
+
# Use `openstack loadbalancer flavor list` to get the full list of available flavors.
160
+
# When not specified, the "small" flavor is used by default.
161
+
loadbalancer.ovhcloud.com/flavor: medium # Name of a loadbalancer flavor, used in MKS Free ONLY.
162
+
loadbalancer.openstack.org/flavor-id: yyy # UUID of a loadbalancer flavor, used in MKS Standard ONLY.
159
163
labels:
160
164
app: test-octavia
161
165
spec:
@@ -213,7 +217,11 @@ metadata:
213
217
namespace: test-lb-ns
214
218
annotations:
215
219
loadbalancer.ovhcloud.com/class: "octavia"//not required for cluster running kubernetes versions >= 1.31
216
-
loadbalancer.ovhcloud.com/flavor: "medium"//optional, default = small
220
+
221
+
# Use `openstack loadbalancer flavor list` to get the full list of available flavors.
222
+
# When not specified, the "small" flavor is used by default.
223
+
loadbalancer.ovhcloud.com/flavor: medium # Name of a loadbalancer flavor, used in MKS Free ONLY.
224
+
loadbalancer.openstack.org/flavor-id: yyy # UUID of a loadbalancer flavor, used in MKS Standard ONLY.
217
225
labels:
218
226
app: test-octavia
219
227
spec:
@@ -241,10 +249,18 @@ spec:
241
249
242
250
Authorized values: 'octavia'= Public Cloud Load Balancer, 'iolb' = Loadbalancer for Managed Kubernetes Service (will be deprecated in future versions). If not specified, the default class of the MKS Kubernetes versions you are using will be applied, please refer to the [versions matrix section](#kube-versions).
Not a standard OpenStack Octavia annotation (specific to OVHcloud). The size used for creating the loadbalancer. Specifications can be found on the [Load Balancer specifications](/links/public-cloud/load-balancer) page. Authorized values => `small`,`medium`,`large`, `xl`. Default is 'small'.
247
255
256
+
- `loadbalancer.openstack.org/flavor-id`(MKS Standard only)
257
+
258
+
The UUID of the flavor used to create the loadbalancer. To get the flavors UUIDs, see the following guides:
259
+
260
+
- [Prepare the environment to use the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api),
261
+
- [Load the OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables).
262
+
- Run `openstack loadbalancer flavor list` to get the list of flavors and their UUIDs.
There is no proper way to "hot-resize" your loadbalancer yet (work in progress). The best alternative to change the flavor of your load balancer is to recreate a new Kubernetes Service that will use the same public IP as an existing one.
367
-
You can find the complete HowTo and examples on our public Github repository: <https://github.com/ovh/public-cloud-examples>
384
+
There is no proper way to "hot-resize" your loadbalancer yet ([work in progress](https://github.com/ovh/public-cloud-roadmap/issues/418)). The best alternative to change the flavor of your load balancer is to recreate a new Kubernetes Service that will use the same public IP as an existing one.
385
+
386
+
You can find the complete HowTo and examples on our public Github repository: <https://github.com/ovh/public-cloud-examples/tree/main/containers-orchestration/managed-kubernetes/use-public-cloud-load-balancer>.
368
387
369
388
- First, make sure that the existing service is using the `loadbalancer.openstack.org/keep-floatingip` annotation. If it's not using it, the public Floating IP will be released (it can be added after the service creation).
If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
577
599
578
-
Join our community of users on <https://community.ovh.com/en/>.
Copy file name to clipboardExpand all lines: pages/public_cloud/containers_orchestration/managed_kubernetes/expose_your_applications_using_a_load_balancer/guide.en-asia.md
+40-18Lines changed: 40 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Expose your applications using OVHcloud Public Cloud Load Balancer
3
3
excerpt: "How to expose your applications hosted on Managed Kubernetes Service using the OVHcloud Public Cloud Load Balancer"
4
-
updated: 2025-02-17
4
+
updated: 2025-10-06
5
5
---
6
6
7
7
> [!warning]
@@ -27,9 +27,6 @@ To be able to deploy [Public Cloud Load Balancer](/links/public-cloud/load-balan
27
27
28
28
| Kubernetes versions |
29
29
| ------------------- |
30
-
| 1.26.4-3 >= |
31
-
| 1.27.12-1 >= |
32
-
| 1.28.8-1 >= |
33
30
| 1.29.3-3 >= |
34
31
| 1.30.2-1 >= |
35
32
@@ -70,9 +67,9 @@ If you have an existing/already deployed cluster and if:
70
67
71
68
When exposing your load balancer publicly (public-to-public or public-to-private):
72
69
73
-
- If it does not already exist, a single OVHcloud Gateway will be automatically created and billed for all Load Balancers spawned in the subnet <https://www.ovhcloud.com/asia/public-cloud/prices/#10394>.
74
-
- A Public Floating IP will be used: <https://www.ovhcloud.com/asia/public-cloud/prices/#10346>.
75
-
- Each Public Cloud Load Balancer is billed according to its flavor: <https://www.ovhcloud.com/asia/public-cloud/prices/#10420>.
70
+
- If it does not already exist, a single OVHcloud Gateway will be automatically created and billed for all Load Balancers spawned in the subnet <https://www.ovhcloud.com/en-gb/public-cloud/prices/#10394>.
71
+
- A Public Floating IP will be used: <https://www.ovhcloud.com/en-gb/public-cloud/prices/#10346>.
72
+
- Each Public Cloud Load Balancer is billed according to its flavor: <https://www.ovhcloud.com/en-gb/public-cloud/prices/#10420>.
# Use `openstack loadbalancer flavor list` to get the full list of available flavors.
111
+
loadbalancer.ovhcloud.com/flavor: small # Name of a loadbalancer flavor, used in MKS Free ONLY.
112
+
loadbalancer.openstack.org/flavor-id: xxx # UUID of a loadbalancer flavor, used in MKS Standard ONLY.
113
113
spec:
114
114
ports:
115
115
- name: 80-80
@@ -155,7 +155,11 @@ metadata:
155
155
namespace: test-lb-ns
156
156
annotations:
157
157
loadbalancer.ovhcloud.com/class: "octavia"//not required for cluster running kubernetes versions >= 1.31
158
-
loadbalancer.ovhcloud.com/flavor: "medium"//optional, default = small
158
+
159
+
# Use `openstack loadbalancer flavor list` to get the full list of available flavors.
160
+
# When not specified, the "small" flavor is used by default.
161
+
loadbalancer.ovhcloud.com/flavor: medium # Name of a loadbalancer flavor, used in MKS Free ONLY.
162
+
loadbalancer.openstack.org/flavor-id: yyy # UUID of a loadbalancer flavor, used in MKS Standard ONLY.
159
163
labels:
160
164
app: test-octavia
161
165
spec:
@@ -213,7 +217,11 @@ metadata:
213
217
namespace: test-lb-ns
214
218
annotations:
215
219
loadbalancer.ovhcloud.com/class: "octavia"//not required for cluster running kubernetes versions >= 1.31
216
-
loadbalancer.ovhcloud.com/flavor: "medium"//optional, default = small
220
+
221
+
# Use `openstack loadbalancer flavor list` to get the full list of available flavors.
222
+
# When not specified, the "small" flavor is used by default.
223
+
loadbalancer.ovhcloud.com/flavor: medium # Name of a loadbalancer flavor, used in MKS Free ONLY.
224
+
loadbalancer.openstack.org/flavor-id: yyy # UUID of a loadbalancer flavor, used in MKS Standard ONLY.
217
225
labels:
218
226
app: test-octavia
219
227
spec:
@@ -241,10 +249,18 @@ spec:
241
249
242
250
Authorized values: 'octavia'= Public Cloud Load Balancer, 'iolb' = Loadbalancer for Managed Kubernetes Service (will be deprecated in future versions). If not specified, the default class of the MKS Kubernetes versions you are using will be applied, please refer to the [versions matrix section](#kube-versions).
Not a standard OpenStack Octavia annotation (specific to OVHcloud). The size used for creating the loadbalancer. Specifications can be found on the [Load Balancer specifications](/links/public-cloud/load-balancer) page. Authorized values => `small`,`medium`,`large`, `xl`. Default is 'small'.
247
255
256
+
- `loadbalancer.openstack.org/flavor-id`(MKS Standard only)
257
+
258
+
The UUID of the flavor used to create the loadbalancer. To get the flavors UUIDs, see the following guides:
259
+
260
+
- [Prepare the environment to use the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api),
261
+
- [Load the OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables).
262
+
- Run `openstack loadbalancer flavor list` to get the list of flavors and their UUIDs.
There is no proper way to "hot-resize" your loadbalancer yet (work in progress). The best alternative to change the flavor of your load balancer is to recreate a new Kubernetes Service that will use the same public IP as an existing one.
367
-
You can find the complete HowTo and examples on our public Github repository: <https://github.com/ovh/public-cloud-examples>
384
+
There is no proper way to "hot-resize" your loadbalancer yet ([work in progress](https://github.com/ovh/public-cloud-roadmap/issues/418)). The best alternative to change the flavor of your load balancer is to recreate a new Kubernetes Service that will use the same public IP as an existing one.
385
+
386
+
You can find the complete HowTo and examples on our public Github repository: <https://github.com/ovh/public-cloud-examples/tree/main/containers-orchestration/managed-kubernetes/use-public-cloud-load-balancer>.
368
387
369
388
- First, make sure that the existing service is using the `loadbalancer.openstack.org/keep-floatingip` annotation. If it's not using it, the public Floating IP will be released (it can be added after the service creation).
If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
577
599
578
-
Join our community of users on <https://community.ovh.com/en/>.
0 commit comments