rssLink RSS for all categories
 
icon_red
icon_green
icon_red
icon_blue
icon_red
icon_green
icon_green
icon_orange
icon_red
icon_red
icon_green
icon_green
icon_green
icon_orange
icon_green
icon_green
icon_green
icon_blue
icon_red
icon_red
icon_green
icon_green
icon_green
icon_blue
icon_orange
icon_blue
icon_green
icon_green
icon_green
icon_green
icon_red
icon_red
icon_green
icon_green
icon_green
icon_green
 

FS#47890 — LBaaS beta EOSL

Attached to Project— Kubernetes
Maintenance
Backend / Core
CLOSED
100%
Planned starting date : 16 March 09AM UTC
Planned End Date : 16 March 5PM UTC

Services concerned : All managed Kubernetes services which are running Beta Load Balancers

As stated in an email sent to all Kubernetes users running beta version of our load balancer early December, all beta load balancers will be terminated.

http://travaux.ovh.net/?do=details&id=47889
Date:  Friday, 02 April 2021, 11:07AM
Reason for closing:  Done
Comment by OVH - Tuesday, 16 March 2021, 12:17PM

Starting backend migration on BHS.

As a reminder, here is a part of the mail campaign that was sent to the Managed Kubernetes customers:

Dear Kubernetes customer,
We strongly recommend you read through the whole email, keeping in mind the following key information:

Our legacy load balancers for Kubernetes will reach end of life on January 18, 2021
DNS resolution and IP address resolution for these legacy load balancers will not work anymore on March 16, 2021

Our Load Balancers, integrated with our Managed Kubernetes Service, are now available in all our regions and datacentres, where the service is provided with the following production-optimised benefits:

High availability: Deployed on brand-new highly available infrastructure.
Shorter launch and configuration update: Super quick launch and update time (under a minute).
Dedicated IPv4 public IP: Each Load Balancer has a unique, dedicated IPv4 public IP.
Integration with your customer panel: Load Balancer and billing accessible via the OVHcloud customer panel and OVHcloud API
16 Load Balancers per Kubernetes cluster: Increased number of Load Balancers allowed per Kubernetes cluster
Hourly Pay-as-You-Go billing: per hour, on a 10 € per month basis. (or price equivalent in your local currency)
SLA backed service: Backed up by a 99.99% SLA

In our previous dedicated email communication in April and September 2020, we invited you to delete and re-create your existing legacy load balancers provisioned before the new service availability, so you can take advantage of the new features. We are now planning the retirement of the legacy beta load balancer for Kubernetes.
We have noticed that you still have active legacy load balancers that have been created before August 5th, 2020 hence deployed on the legacy infrastructure and that does not offer the aforementioned benefits. There are two main cases, you should consider:
Case #1: These legacy load balancers are not useful for you
If you don’t use these legacy load balancers and/or associated Kubernetes cluster(s) anymore, we are inviting you to delete these before January, 18th, 2021. Without any action from your part, these legacy load balancers will be automatically replaced by our new load balancers and will be invoiced in accordance with the applicable pricing.
Case #2: You are still using these legacy load balancers
If you are still using these legacy load balancers, you should as soon as possible create new ones and delete the legacy ones.
Without any action from your part, each legacy load balancer will be automatically replaced by a new load balancer and will be invoiced in accordance with the applicable pricing, with the same configuration but with a new dedicated IP address – which will be displayed in the field “external IP” of the new load balancer.
To simplify the transition, the resolution of the former domain name (DNS resolution) with the former IP address will terminate definitely on March, 16, 2021. From this date, any connection to the former domain name or to the former IP address will not work anymore.
How to identify the legacy load balancers, requiring your attention:
To identify these legacy load balancers, check the “External-IP” field. If this is a domain name and not an IPv4 address, there are the ones that require your attention.
You can track the progress of the retirement of the legacy load balancers for K8S by viewing this task
For any question, reach out to our support team or to your account manager.

The OVHcloud Public Cloud team


Comment by OVH - Tuesday, 16 March 2021, 14:36PM

Starting backend migration on GRA5


Comment by OVH - Tuesday, 16 March 2021, 15:37PM

Starting backend migration on WAW1


Comment by OVH - Tuesday, 16 March 2021, 15:52PM

Starting backend migration on SYD


Comment by OVH - Tuesday, 16 March 2021, 15:52PM

Starting backend migration on SGP


Comment by OVH - Tuesday, 16 March 2021, 16:23PM

Starting backend migration on GRA7


Comment by OVH - Wednesday, 17 March 2021, 12:20PM

There is actually some clusters impacted by the backend migration on GRA7.
Some ApiServers on GRA7 could not respond well.

We are still trying to stabilize this region.


Comment by OVH - Friday, 19 March 2021, 15:18PM

There was an impact on one of the components.
The component has been corrected and redeployed.
Deletion will start again on Monday


Comment by OVH - Wednesday, 31 March 2021, 15:08PM

Deletion is planned tomorrow morning (April 1st).
Be sure you don't use anymore old loadbalancers.


Comment by OVH - Thursday, 01 April 2021, 14:06PM

Starting back the deletion


Comment by OVH - Thursday, 01 April 2021, 21:11PM

Every loadbalancer in GRA5 have been deleted.


Comment by OVH - Thursday, 01 April 2021, 21:11PM

Starting deletion on BHS


Comment by OVH - Thursday, 01 April 2021, 21:20PM

Starting deletion on SBG


Comment by OVH - Thursday, 01 April 2021, 21:37PM

GRA7 is still up and running, deletion planned for tomorrow morning (April 2th 8h UTC)


Comment by OVH - Friday, 02 April 2021, 10:51AM

Starting deletion on GRA7