Tanzu Application Platform v1.7+ installs the Contour’s Envoy pods as a Deployment instead of a DaemonSet. This change causes application downtime during an upgrade.

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

As documented in TAP v1.7.0 Breaking changes: Contour , by default, Tanzu Application Platform v1.7.0 installs the Contour’s Envoy pods as a Deployment instead of a DaemonSet. The purpose for introducing this change is for providing choice for customers to be able to effectively use resources. However, this change causes application downtime during an upgrade.

Environment

Product Version: 1.6

Resolution

To avoid the upgrade downtime for Tanzu Application Platform v1.7 and later, customers can keep running Envoy as a DaemonSet by adding contour.envoy.workload.type to the values file and setting it to DaemonSet before performing the upgrade:

contour:
  envoy:
    workload:
      type: DaemonSet

If customers choose to run Envoy as a Deployment, then contour.envoy.workload.replicas can be set to configure the desired replica numbers. 

contour:
  envoy:
    workload:
      replicas: 3