How to Upgrade a Cloudguard VMSS (Scaleset) Solution from R80.20 --> R80.30 in Azure

[#1]

As R80.10 and R80.20 images are soon to be delisted from the Azure Marketplace,

I put together a step-by-step guide with screenshots on how to upgrade a Cloudguard VMSS (Scale Set) from R80.20 to R80.30 in Microsoft Azure - with R80.20 Management. This "how-to" is based on the new procedure from the Admin Guide which you can find here: CloudGuard Network for Azure VMSS R80.10 and Higher Administration Guide (This link was edited by Check Point on 19 Dec 2021)

Your feedback and comments are appreciated. 

[#2]

As R80.10 and R80.20 images are soon to be delisted from the Azure Marketplace,

I put together a step-by-step guide with screenshots on how to upgrade a Cloudguard VMSS (Scale Set) from R80.20 to R80.30 in Microsoft Azure - with R80.20 Management. This "how-to" is based on the new procedure from the Admin Guide which you can find here: CloudGuard Network for Azure VMSS R80.10 and Higher Administration Guide (This link was edited by Check Point on 19 Dec 2021)

Your feedback and comments are appreciated. 

[#3]

As R80.10 and R80.20 images are soon to be delisted from the Azure Marketplace,

I put together a step-by-step guide with screenshots on how to upgrade a Cloudguard VMSS (Scale Set) from R80.20 to R80.30 in Microsoft Azure - with R80.20 Management. This "how-to" is based on the new procedure from the Admin Guide which you can find here: CloudGuard Network for Azure VMSS R80.10 and Higher Administration Guide (This link was edited by Check Point on 19 Dec 2021)

Your feedback and comments are appreciated. 

[Eugene_Tcheby]

You're welcome Martin.

[Eugene_Tcheby]

You're welcome Martin.

[LazarusG]

outstanding! - I don't suppose there is something similar for AWS?

Specifically:

1) is it possible to have more than one template that binds the same policy to multiple versions of scalesets? (so that you can migrate production traffic from the old ones to the new ones one at a time).

2) If there is no support for in-place upgrade of scalesets, and a parallel deployment is needed - can the front end IP be moved to the new scaleset, and moved back to the old one as a roll back in case of issues?

Thanks

[LazarusG]

outstanding! - I don't suppose there is something similar for AWS?

Specifically:

1) is it possible to have more than one template that binds the same policy to multiple versions of scalesets? (so that you can migrate production traffic from the old ones to the new ones one at a time).

2) If there is no support for in-place upgrade of scalesets, and a parallel deployment is needed - can the front end IP be moved to the new scaleset, and moved back to the old one as a roll back in case of issues?

Thanks

[Serv]

Hello Eugene_Tcheby,

Very nice document. Thanks for that, do you have any such for the AWS.

[Serv]

Hello Eugene_Tcheby,

Very nice document. Thanks for that, do you have any such for the AWS.