Standard cluster update - 09/12/2024

News
1

Standard cluster update notification

:warning: Update - September 12, 2024

The scheduled update for non-production clusters did not take place today due to issues with our ARM image. To avoid any potential risks, we have decided to postpone the update. The issue has since been resolved, and we have rescheduled the maintenance to September 16, 2024 at 8:00 AM UTC.

Context

We are announcing a series of cluster updates to improve performance, security, and introduce new features that will enhance your experience. These updates are part of our ongoing effort to optimize our services and ensure high reliability.

Impact

Is any action required on your part?

  • Yes, please refer to the details below for specific actions that may impact your setup.

Update Details

The following updates and new features will be applied:

  • Cert-Manager Update: This requires configuration changes related to certificate management.
    More details and instructions here.
  • NGINX Ingress Name Update: The ingress name will be updated, and you may need to adjust your configurations accordingly.
    More information available here.
  • ALB Controller Flag Activation (Non-production only): We will enable the AWS Load Balancer (ALB) controller for non-production clusters, as part of our transition away from the NLB controller.
    Learn more about this change.

New Schedule for Non-Production Clusters

  • Date: September 16, 2024
  • Time: 8:00 AM UTC

New Schedule for production Clusters

  • Date: September 19, 2024
  • Time: 8:00 AM UTC

Additional Information

If you have any questions or require further assistance, please don’t hesitate to contact us.

Thank you for your patience and understanding as we work to ensure a smooth update process.

2

Hi, is it possible to opt-out of NLB to ALB migration?

3

@Julien_Dan The link to the NLB->ALB details isn’t opening: https://discuss.qovery.com/t/aws-migration-moving-from-nlb-controller-to-alb-controller/2953

image
image1602×324 24.8 KB

1 Like
4

Thanks @Kyle_Flavin it should be ok now.

5

The message is poorly written:

It’s not “AWS Application Load Balancer (ALB)” but “AWS Load Balancer (ALB)” (still being powered by NLB and not the Application Load Balancer). I just found out this in the other article.

6

Hey @prki,
Could you please elaborate on your reasons for opting out of this migration? Is it primarily a matter of timing, or are there other factors?

7

No need to opt-out anymore. I was confused that the migration was going to change to Application Load Balancer but it’s still going to be using Network Load Balancer (managed by ALB controller). It’s partly AWS fault of having two different things behind ALB acronym.

1 Like
8

Thanks indeed the ALB acronym is confusing. I have updated the post.
Thanks again!