Skip to content

Commit 59a717e

Browse files
Y0CossY0Coss
authored
Merge pull request #7471 from ovh/lgr/mks/remove-proxyprotocol-v2-warning
chore(mks/octavia): remove warning proxyprotocol version
2 parents 5205a4b + 8ec7857 commit 59a717e

30 files changed

+45
-120
lines changed

‎pages/public_cloud/containers_orchestration/managed_kubernetes/expose_your_applications_using_a_load_balancer/guide.de-de.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Expose your applications using OVHcloud Public Cloud Load Balancer
33
excerpt: "How to expose your applications hosted on Managed Kubernetes Service using the OVHcloud Public Cloud Load Balancer"
4-
updated: 2025-01-03
4+
updated: 2025-01-30
55
---
66

77
> [!warning]
@@ -411,11 +411,6 @@ test-lb-todel LoadBalancer 10.3.107.18 141.94.215.240 80:30172/TCP
411411

412412
When exposing services like nginx-ingress-controller, it's a common requirement that the client connection information could pass through proxy servers and load balancers, therefore visible to the backend services. Knowing the originating IP address of a client may be useful for setting a particular language for a website, keeping a denylist of IP addresses, or simply for logging and statistics purposes. You can follow the official Cloud Controller Manager documentation on how to [Use PROXY protocol to preserve client IP](https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/openstack-cloud-controller-manager/expose-applications-using-loadbalancer-type-service.md#use-proxy-protocol-to-preserve-client-ip).
413413

414-
> [!warning]
415-
>
416-
> Only ProxyProtocol version 1 is supported at the moment by the MKS's integration.
417-
>
418-
419414
#### Migrate from Loadbalancer for Kubernetes to Public Cloud Load Balancer
420415

421416
In order to migrate from an existing [Loadbalancer for Kubernetes](/links/public-cloud/load-balancer-kubernetes) to a [Public Cloud Load Balancer](/links/public-cloud/load-balancer) you will have to modify an existing Service and change its LoadBalancer class.

‎pages/public_cloud/containers_orchestration/managed_kubernetes/expose_your_applications_using_a_load_balancer/guide.en-asia.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Expose your applications using OVHcloud Public Cloud Load Balancer
33
excerpt: "How to expose your applications hosted on Managed Kubernetes Service using the OVHcloud Public Cloud Load Balancer"
4-
updated: 2025-01-03
4+
updated: 2025-01-30
55
---
66

77
> [!warning]
@@ -411,11 +411,6 @@ test-lb-todel LoadBalancer 10.3.107.18 141.94.215.240 80:30172/TCP
411411

412412
When exposing services like nginx-ingress-controller, it's a common requirement that the client connection information could pass through proxy servers and load balancers, therefore visible to the backend services. Knowing the originating IP address of a client may be useful for setting a particular language for a website, keeping a denylist of IP addresses, or simply for logging and statistics purposes. You can follow the official Cloud Controller Manager documentation on how to [Use PROXY protocol to preserve client IP](https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/openstack-cloud-controller-manager/expose-applications-using-loadbalancer-type-service.md#use-proxy-protocol-to-preserve-client-ip).
413413

414-
> [!warning]
415-
>
416-
> Only ProxyProtocol version 1 is supported at the moment by the MKS's integration.
417-
>
418-
419414
#### Migrate from Loadbalancer for Kubernetes to Public Cloud Load Balancer
420415

421416
In order to migrate from an existing [Loadbalancer for Kubernetes](/links/public-cloud/load-balancer-kubernetes) to a [Public Cloud Load Balancer](/links/public-cloud/load-balancer) you will have to modify an existing Service and change its LoadBalancer class.

‎pages/public_cloud/containers_orchestration/managed_kubernetes/expose_your_applications_using_a_load_balancer/guide.en-au.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Expose your applications using OVHcloud Public Cloud Load Balancer
33
excerpt: "How to expose your applications hosted on Managed Kubernetes Service using the OVHcloud Public Cloud Load Balancer"
4-
updated: 2025-01-03
4+
updated: 2025-01-30
55
---
66

77
> [!warning]
@@ -411,11 +411,6 @@ test-lb-todel LoadBalancer 10.3.107.18 141.94.215.240 80:30172/TCP
411411

412412
When exposing services like nginx-ingress-controller, it's a common requirement that the client connection information could pass through proxy servers and load balancers, therefore visible to the backend services. Knowing the originating IP address of a client may be useful for setting a particular language for a website, keeping a denylist of IP addresses, or simply for logging and statistics purposes. You can follow the official Cloud Controller Manager documentation on how to [Use PROXY protocol to preserve client IP](https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/openstack-cloud-controller-manager/expose-applications-using-loadbalancer-type-service.md#use-proxy-protocol-to-preserve-client-ip).
413413

414-
> [!warning]
415-
>
416-
> Only ProxyProtocol version 1 is supported at the moment by the MKS's integration.
417-
>
418-
419414
#### Migrate from Loadbalancer for Kubernetes to Public Cloud Load Balancer
420415

421416
In order to migrate from an existing [Loadbalancer for Kubernetes](/links/public-cloud/load-balancer-kubernetes) to a [Public Cloud Load Balancer](/links/public-cloud/load-balancer) you will have to modify an existing Service and change its LoadBalancer class.

‎pages/public_cloud/containers_orchestration/managed_kubernetes/expose_your_applications_using_a_load_balancer/guide.en-ca.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Expose your applications using OVHcloud Public Cloud Load Balancer
33
excerpt: "How to expose your applications hosted on Managed Kubernetes Service using the OVHcloud Public Cloud Load Balancer"
4-
updated: 2025-01-03
4+
updated: 2025-01-30
55
---
66

77
> [!warning]
@@ -411,11 +411,6 @@ test-lb-todel LoadBalancer 10.3.107.18 141.94.215.240 80:30172/TCP
411411

412412
When exposing services like nginx-ingress-controller, it's a common requirement that the client connection information could pass through proxy servers and load balancers, therefore visible to the backend services. Knowing the originating IP address of a client may be useful for setting a particular language for a website, keeping a denylist of IP addresses, or simply for logging and statistics purposes. You can follow the official Cloud Controller Manager documentation on how to [Use PROXY protocol to preserve client IP](https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/openstack-cloud-controller-manager/expose-applications-using-loadbalancer-type-service.md#use-proxy-protocol-to-preserve-client-ip).
413413

414-
> [!warning]
415-
>
416-
> Only ProxyProtocol version 1 is supported at the moment by the MKS's integration.
417-
>
418-
419414
#### Migrate from Loadbalancer for Kubernetes to Public Cloud Load Balancer
420415

421416
In order to migrate from an existing [Loadbalancer for Kubernetes](/links/public-cloud/load-balancer-kubernetes) to a [Public Cloud Load Balancer](/links/public-cloud/load-balancer) you will have to modify an existing Service and change its LoadBalancer class.

‎pages/public_cloud/containers_orchestration/managed_kubernetes/expose_your_applications_using_a_load_balancer/guide.en-gb.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Expose your applications using OVHcloud Public Cloud Load Balancer
33
excerpt: "How to expose your applications hosted on Managed Kubernetes Service using the OVHcloud Public Cloud Load Balancer"
4-
updated: 2025-01-03
4+
updated: 2025-01-30
55
---
66

77
> [!warning]
@@ -411,11 +411,6 @@ test-lb-todel LoadBalancer 10.3.107.18 141.94.215.240 80:30172/TCP
411411

412412
When exposing services like nginx-ingress-controller, it's a common requirement that the client connection information could pass through proxy servers and load balancers, therefore visible to the backend services. Knowing the originating IP address of a client may be useful for setting a particular language for a website, keeping a denylist of IP addresses, or simply for logging and statistics purposes. You can follow the official Cloud Controller Manager documentation on how to [Use PROXY protocol to preserve client IP](https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/openstack-cloud-controller-manager/expose-applications-using-loadbalancer-type-service.md#use-proxy-protocol-to-preserve-client-ip).
413413

414-
> [!warning]
415-
>
416-
> Only ProxyProtocol version 1 is supported at the moment by the MKS's integration.
417-
>
418-
419414
#### Migrate from Loadbalancer for Kubernetes to Public Cloud Load Balancer
420415

421416
In order to migrate from an existing [Loadbalancer for Kubernetes](/links/public-cloud/load-balancer-kubernetes) to a [Public Cloud Load Balancer](/links/public-cloud/load-balancer) you will have to modify an existing Service and change its LoadBalancer class.

‎pages/public_cloud/containers_orchestration/managed_kubernetes/expose_your_applications_using_a_load_balancer/guide.en-ie.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Expose your applications using OVHcloud Public Cloud Load Balancer
33
excerpt: "How to expose your applications hosted on Managed Kubernetes Service using the OVHcloud Public Cloud Load Balancer"
4-
updated: 2025-01-03
4+
updated: 2025-01-30
55
---
66

77
> [!warning]
@@ -411,11 +411,6 @@ test-lb-todel LoadBalancer 10.3.107.18 141.94.215.240 80:30172/TCP
411411

412412
When exposing services like nginx-ingress-controller, it's a common requirement that the client connection information could pass through proxy servers and load balancers, therefore visible to the backend services. Knowing the originating IP address of a client may be useful for setting a particular language for a website, keeping a denylist of IP addresses, or simply for logging and statistics purposes. You can follow the official Cloud Controller Manager documentation on how to [Use PROXY protocol to preserve client IP](https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/openstack-cloud-controller-manager/expose-applications-using-loadbalancer-type-service.md#use-proxy-protocol-to-preserve-client-ip).
413413

414-
> [!warning]
415-
>
416-
> Only ProxyProtocol version 1 is supported at the moment by the MKS's integration.
417-
>
418-
419414
#### Migrate from Loadbalancer for Kubernetes to Public Cloud Load Balancer
420415

421416
In order to migrate from an existing [Loadbalancer for Kubernetes](/links/public-cloud/load-balancer-kubernetes) to a [Public Cloud Load Balancer](/links/public-cloud/load-balancer) you will have to modify an existing Service and change its LoadBalancer class.

‎pages/public_cloud/containers_orchestration/managed_kubernetes/expose_your_applications_using_a_load_balancer/guide.en-sg.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Expose your applications using OVHcloud Public Cloud Load Balancer
33
excerpt: "How to expose your applications hosted on Managed Kubernetes Service using the OVHcloud Public Cloud Load Balancer"
4-
updated: 2025-01-03
4+
updated: 2025-01-30
55
---
66

77
> [!warning]
@@ -411,11 +411,6 @@ test-lb-todel LoadBalancer 10.3.107.18 141.94.215.240 80:30172/TCP
411411

412412
When exposing services like nginx-ingress-controller, it's a common requirement that the client connection information could pass through proxy servers and load balancers, therefore visible to the backend services. Knowing the originating IP address of a client may be useful for setting a particular language for a website, keeping a denylist of IP addresses, or simply for logging and statistics purposes. You can follow the official Cloud Controller Manager documentation on how to [Use PROXY protocol to preserve client IP](https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/openstack-cloud-controller-manager/expose-applications-using-loadbalancer-type-service.md#use-proxy-protocol-to-preserve-client-ip).
413413

414-
> [!warning]
415-
>
416-
> Only ProxyProtocol version 1 is supported at the moment by the MKS's integration.
417-
>
418-
419414
#### Migrate from Loadbalancer for Kubernetes to Public Cloud Load Balancer
420415

421416
In order to migrate from an existing [Loadbalancer for Kubernetes](/links/public-cloud/load-balancer-kubernetes) to a [Public Cloud Load Balancer](/links/public-cloud/load-balancer) you will have to modify an existing Service and change its LoadBalancer class.

‎pages/public_cloud/containers_orchestration/managed_kubernetes/expose_your_applications_using_a_load_balancer/guide.en-us.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Expose your applications using OVHcloud Public Cloud Load Balancer
33
excerpt: "How to expose your applications hosted on Managed Kubernetes Service using the OVHcloud Public Cloud Load Balancer"
4-
updated: 2025-01-03
4+
updated: 2025-01-30
55
---
66

77
> [!warning]
@@ -411,11 +411,6 @@ test-lb-todel LoadBalancer 10.3.107.18 141.94.215.240 80:30172/TCP
411411

412412
When exposing services like nginx-ingress-controller, it's a common requirement that the client connection information could pass through proxy servers and load balancers, therefore visible to the backend services. Knowing the originating IP address of a client may be useful for setting a particular language for a website, keeping a denylist of IP addresses, or simply for logging and statistics purposes. You can follow the official Cloud Controller Manager documentation on how to [Use PROXY protocol to preserve client IP](https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/openstack-cloud-controller-manager/expose-applications-using-loadbalancer-type-service.md#use-proxy-protocol-to-preserve-client-ip).
413413

414-
> [!warning]
415-
>
416-
> Only ProxyProtocol version 1 is supported at the moment by the MKS's integration.
417-
>
418-
419414
#### Migrate from Loadbalancer for Kubernetes to Public Cloud Load Balancer
420415

421416
In order to migrate from an existing [Loadbalancer for Kubernetes](/links/public-cloud/load-balancer-kubernetes) to a [Public Cloud Load Balancer](/links/public-cloud/load-balancer) you will have to modify an existing Service and change its LoadBalancer class.

‎pages/public_cloud/containers_orchestration/managed_kubernetes/expose_your_applications_using_a_load_balancer/guide.es-es.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Expose your applications using OVHcloud Public Cloud Load Balancer
33
excerpt: "How to expose your applications hosted on Managed Kubernetes Service using the OVHcloud Public Cloud Load Balancer"
4-
updated: 2025-01-03
4+
updated: 2025-01-30
55
---
66

77
> [!warning]
@@ -411,11 +411,6 @@ test-lb-todel LoadBalancer 10.3.107.18 141.94.215.240 80:30172/TCP
411411

412412
When exposing services like nginx-ingress-controller, it's a common requirement that the client connection information could pass through proxy servers and load balancers, therefore visible to the backend services. Knowing the originating IP address of a client may be useful for setting a particular language for a website, keeping a denylist of IP addresses, or simply for logging and statistics purposes. You can follow the official Cloud Controller Manager documentation on how to [Use PROXY protocol to preserve client IP](https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/openstack-cloud-controller-manager/expose-applications-using-loadbalancer-type-service.md#use-proxy-protocol-to-preserve-client-ip).
413413

414-
> [!warning]
415-
>
416-
> Only ProxyProtocol version 1 is supported at the moment by the MKS's integration.
417-
>
418-
419414
#### Migrate from Loadbalancer for Kubernetes to Public Cloud Load Balancer
420415

421416
In order to migrate from an existing [Loadbalancer for Kubernetes](/links/public-cloud/load-balancer-kubernetes) to a [Public Cloud Load Balancer](/links/public-cloud/load-balancer) you will have to modify an existing Service and change its LoadBalancer class.

‎pages/public_cloud/containers_orchestration/managed_kubernetes/expose_your_applications_using_a_load_balancer/guide.es-us.md

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Expose your applications using OVHcloud Public Cloud Load Balancer
33
excerpt: "How to expose your applications hosted on Managed Kubernetes Service using the OVHcloud Public Cloud Load Balancer"
4-
updated: 2025-01-03
4+
updated: 2025-01-30
55
---
66

77
> [!warning]
@@ -411,11 +411,6 @@ test-lb-todel LoadBalancer 10.3.107.18 141.94.215.240 80:30172/TCP
411411

412412
When exposing services like nginx-ingress-controller, it's a common requirement that the client connection information could pass through proxy servers and load balancers, therefore visible to the backend services. Knowing the originating IP address of a client may be useful for setting a particular language for a website, keeping a denylist of IP addresses, or simply for logging and statistics purposes. You can follow the official Cloud Controller Manager documentation on how to [Use PROXY protocol to preserve client IP](https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/openstack-cloud-controller-manager/expose-applications-using-loadbalancer-type-service.md#use-proxy-protocol-to-preserve-client-ip).
413413

414-
> [!warning]
415-
>
416-
> Only ProxyProtocol version 1 is supported at the moment by the MKS's integration.
417-
>
418-
419414
#### Migrate from Loadbalancer for Kubernetes to Public Cloud Load Balancer
420415

421416
In order to migrate from an existing [Loadbalancer for Kubernetes](/links/public-cloud/load-balancer-kubernetes) to a [Public Cloud Load Balancer](/links/public-cloud/load-balancer) you will have to modify an existing Service and change its LoadBalancer class.

0 commit comments

Comments
 (0)