Redis for VMware Tanzu Application Service Release Notes

Note: Pivotal Platform is now part of VMware Tanzu. In v2.4 and later, Redis for Pivotal Platform is named Redis for VMware Tanzu Application Service.

Page last updated:

For product versions and upgrade paths, see Upgrade Planner.

v2.4.4

Release Date: October 8, 2021

Features

New feature in this release:

Known Issues

There are no known issues for this release.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell 621.90
VMware Tanzu Application Service for VMs 2.9, 2.10, 2.11 and 2.12
shared-redis-release 437.0.19
on-demand-service-broker 0.42.1
routing 0.224.0
service-metrics 2.0.14
service-backup 18.4.0
loggregator-agent 6.3.4
bpm 1.1.13
Redis OSS 5.0.13

v2.4.3

Release Date: August 17, 2021

Security Fixes

This release includes the following security fix:

Resolved Issues

This release has the following fixes:

  • A log error related to an unused component no longer appears:
    This error sometimes appeared in logs as: {"error":"Get /v2/info: unsupported protocol scheme "\""}}.

  • Backups of shared-redis plans are working as intended: This issue did not affect on-demand plans. It only affected backups of shared-redis plans on newer deployments of the Redis for Tanzu Application Service tile.

    In the following Redis for Tanzu Application Service versions, backups were configured through a persistent statefile.json created by the Redis for Tanzu Application Service tile:

    • v2.2.2
    • v2.2.1
    • v2.2.0
    • v2.1.4
    • v2.0.6

    This is not true for later Redis for Tanzu Application Service versions. However, backups of shared-redis plans for these later versions still depended on the existence of that statefile.json file.
    This meant installations of Redis for Tanzu Application Service that had created this file, and later been upgraded, persisted the file and worked as expected. Meanwhile, newer installations of Redis for Tanzu Application Service failed to backup shared-redis instances.

    This error sometimes appeared in logs as: {"message": "ServiceBackup.WithIdentifier.Perform backup completed with error", "error": "exit Status 3"}

Known Issues

There are no known issues for this release.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell 621.90
VMware Tanzu Application Service for VMs 2.9, 2.10, and 2.11
shared-redis-release 437.0.19
on-demand-service-broker 0.42.1
routing 0.217.0
service-metrics 2.0.13
service-backup 18.4.0
loggregator-agent 6.3.3
bpm 1.1.12
Redis OSS 5.0.13

v2.4.2

Release Date: May 10, 2021

Features

New features and changes in this release:

  • Secure service bindings are configured from the UI: In earlier releases, secure service bindings for Redis were always stored in CredHub if secure instance credentials were enabled in VMware Tanzu Application Service for VMs. Now, Redis for Tanzu Application Service operators can deactivate this functionality for Redis service instances.
    For information, see step 8 of Configure On-Demand Service Settings of Installing Redis for VMware Tanzu Application Service.

  • Redis OSS: Updated to v5.0.10

Resolved Issues

This release has the following fixes:

  • The upgrade-all-service-instances errand no longer fails when TLS is enforced: This issue was fixed by updating the on-demand-service-broker component to v0.41.0.

  • Healthwatch is no longer a required dependency for Redis for Tanzu Application Service: In v2.4.1, Healthwatch was a required dependency. Attempting to remove Healthwatch from the foundation resulted in an error message, “Product Redis depends on Pivotal Healthwatch”.

Known Issues

There are no known issues for this release.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell 621.90
VMware Tanzu Application Service for VMs 2.9, 2.10, and 2.11
shared-redis-release 437.0.18
on-demand-service-broker 0.41.0
routing 0.213.0
service-metrics 2.0.13
service-backup 18.3.5
loggregator-agent 6.2.0
bpm 1.1.9
Redis OSS 5.0.10

v2.4.1

Release Date: August 20, 2020

Features

New features and changes in this release:

  • Operators can specify which TLS versions to make Redis TLS connections when TLS is enabled: This feature allows control of the versions of TLS that Redis connections support. VMware discourages using TLS v1.0, but it is an option for apps that only support this protocol. For more information, see Configure On-Demand Service Settings.

  • Operators see an error when trying to install an incompatible Healthwatch version: Operators can only install Healthwatch v1.8 and later with the Redis for Tanzu Application Service tile. If the operator tries to install a previous Healthwatch version, the operator sees an error.

  • Operators can enable telemetry to help improve the product: The telemetry program enables VMware to collect data from customer installations to improve the enterprise experience. Collecting data at scale enables VMware to identify patterns and alert you to warning signals in your installation. For more information, see Pivotal Telemetry.

Resolved Issues

This release has the following fix:

  • Rotating the Services TLS CA certificate no longer causes app downtime: In Redis for PCF v2.2 and Redis for Pivotal Platform v2.3, following the Rotating the Services TLS CA and Its Leaf Certificates procedure can cause downtime for apps bound to the Redis service. This issue does not occur in Redis for Tanzu Application Service.

Known Issues

This release has the following issues:

  • Service creation can fail when using an external UAA: An issue with the Redis on-demand service broker and TLS verification means that service creation might fail on the TLS handshake. This has been observed as the upgrade-all-service-instances errand failing, particularly when a separate internal load balancer is present.

  • Healthwatch is a required dependency for Redis for VMware Tanzu Application Service: If you try to remove Healthwatch from Ops Manager where Redis for VMware Tanzu Application Service is also installed, the error message, “Product Redis depends on Pivotal Healthwatch” appears. For more information about this issue, see the VMware Tanzu Support documentation in the Knowledge Base.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell 621.76
VMware Tanzu Application Service for VMs 2.9, 2.10, and 2.11
shared-redis-release 437.0.15
on-demand-service-broker 0.40.0
routing 0.203.0
service-metrics 2.0.13
service-backup 18.3.5
loggregator-agent 6.1.0
bpm 1.1.8
Redis OSS 5.0.7

View Release Notes for Another Version

To view the release notes for another product version, select the version from the dropdown at the top of this page.