Unable to add a second Identity Broker node for High Availability in VCF 9.1

Products

• VCF Operations

Issue/Introduction

• Administrators are unable to add a second VMware Identity Broker node to an existing VMware Identity Broker 9.1 instance.

Environment

• VCF Cloud Foundation 9.1
• VMware Identity Broker 9.1

Cause

In VCF 9.1, the vIDB architecture was updated. The service has been containerized and moved to the VCF Management Services platform. Because of this transition to a container-based architecture, the traditional method of manually deploying and adding individual Virtual Machine nodes to achieve redundancy is no longer applicable.

Resolution

To achieve High Availabilityand add redundancy to an existing vIDB 9.1 instance, administrators must utilize the 'Scale Up' function rather than deploying additional nodes.

Follow these steps to scale up the vIDB instance:

1. Log in to the VCF Operations UI.

2. Navigate to the 'Build' menu and select the 'Lifecycle' tab.

3. Locate and open the 'Identity Broker' component menu.

4. Click on the 'Actions' drop-down menu.

5. Select the 'Scale Up' option to increase the sizing and redundancy of the instance.