Link11 WAAP
v2.18
v2.18
  • Link11 WAAP v2.18 Portal
  • Introduction
  • Getting Started
  • Setup Checklists
  • Marketplace Onboarding
    • AWS
      • Deploy Reblaze
      • Configure the Reblaze Platform
      • Set Up a Load Balancer for Traffic Routing
      • AWS Version Upgrade
    • GCP
      • Deploy Reblaze
      • Configure the Reblaze Platform
      • Set Up GCP Health Checks
      • Set Up GCP Load Balancer
      • GCP BYOL Upgrade
  • Console UI Walkthrough
    • General UI flow
    • Traffic
      • Traffic Concepts
      • Dashboard
      • View Log
    • Security
      • Security Section Concepts
      • Dynamic Rules
      • Quarantined
      • Profiles
        • Profile Concepts
        • Profiles
        • ACL Policies
        • WAF/IPS Policies
        • Custom Signature
      • Args Analysis
      • Tag Rules
      • Rate Limiting
      • Cloud Functions
    • Settings
      • Web Proxy
      • Backend Services
      • Error Pages
      • SSL
      • DNS
      • CDN
      • Planet Overview
      • Global
      • Account
  • Using the product
    • Best Practices
      • Saving and Publishing Your Changes
      • Enabling Passive Challenges
      • Using the Reblaze Query Box
      • Understanding and Diagnosing Traffic Issues
    • How Do I...
      • Ban, Unban, and Whitelist Traffic Sources
      • Bypass Rate Limits for Loadtesting
      • Control Caching Behavior
      • Filter by Content
      • Quickly Block an Attacker
      • Secure Traffic from a Third-Party Page
      • Set Rate Limits and Exemptions
      • Set up SIEM/SOC integration
      • Video Tutorials
        • DNS Training
    • API
      • Reblaze REST API
      • Mobile SDK
  • Reference Information
    • Access log-structure
    • Acronyms
    • Deployment Terminology
    • Hostile Bot Detection / RCSI
      • Environmental detection and browser verification
      • Client authentication
      • Biometric behavioral verification
    • HTTP Response Codes
    • Pattern Matching Syntax
    • Signatures
    • Tags
    • TTL Expression Syntax
  • Support
Powered by GitBook
On this page
  • Procedure Overview
  • Procedure Details

Was this helpful?

Export as PDF
  1. Marketplace Onboarding
  2. GCP

GCP BYOL Upgrade

Upgrading BYOL - GCP

PreviousSet Up GCP Load BalancerNextGeneral UI flow

Last updated 2 years ago

Was this helpful?

Procedure Overview

#

Step

Executed by

Comments

Estimated duration

1.

Console creation

Reblaze

Configuration will be migrated

1 day

2.

Create new deployment

Customer

Creating a new instance group

30 minutes

3.

Setup canary instance

Reblaze & Customer

Adding a new template

15 minutes

4.

Verify traffic monitoring

Reblaze & Customer

Verifying that there are no issues with site performance, and making changes to security profiles if necessary.

1 hour

5.

Rеmove old template

Customer

Replace all instances

15 minutes

Procedure Details

Step 1: Console Creation by Reblaze

The Reblaze team will set up a new 2.x console for you. Once this is done, proceed to Step 2.

Step 2: Create New Deployment

Go to the Marketplace and create a new Reblaze Deployment in version 2.x.

For the Deployment type, make sure to select “New region”.

For the Template resource zone, select the same region as the one in the previous installation. (Otherwise, the upgrade will not work.)

Scroll further down the page to the following:

For the Networking region, select the same region as the one in the previous installation. (Otherwise, the upgrade will not work.)

Auto-scaling settings - Minimum number of instances: At least as many instances as in the previous installation. In any case, it should never be less than 2 instances.

Redis settings: If you already have a Redis server installed (which is usually true for Reblaze installations of v2.14 and later), you do not need to create a new one, so you can uncheck the Redis deployment checkbox.

After choosing these settings, click the Deploy button at the bottom of the page.

Once your setup is complete, notify Reblaze support. Reblaze personnel will ensure the console is seeing the new instance group, and will connect the Redis server to it.

Step 3: Setup Canary Instance

Within your GCP console, go to Instance groups and select your current (i.e., the older version) instance group.

Here’s an example where the current group is 6887:

Select it by clicking on its name. The following screen will appear:

Now click on Update VMs. to see the You’ll see this:

Click on Add a Second Template. Add the new template you created. (In this example, the new template is 2354.) Now click on Update VMs.

Click on Add a Second Template. Add the new template you created. (In this example, the new template is 2354.) Now click on Update VMs.

Step 4: Verify Traffic Monitoring

Go to your Reblaze dashboard, and make sure that you see traffic in the new instances, and that your sites are working as expected.

Step 5: Remove Old Template

In your GCP console, delete the template for the old version.