You can follow these steps to install Spring Cloud Services.

1. Verify that your system uses only products listed as supported in Requirements.

2. Download Spring Cloud Services from the Broadcom Support portal.

3. In the Installation dashboard of Tanzu Operations Manager, click Import a Product on the left sidebar to upload the Spring Cloud Services tile.

4. In the left sidebar, under Spring Cloud Services, click the + button next to the version number.

5. When the Spring Cloud Services tile appears in the Installation Dashboard, click it. In the Settings tab, click Assign AZs and Networks.

   

6. Select the availability zones for the tile to use. In the Network section, select the network used by Tanzu Platform for Cloud Foundry. Click Save.

7. Return to the Installation Dashboard.

8. Click Review Pending Changes. For more information about this Tanzu Operations Manager page, see Reviewing Pending Product Changes.

9. Click Apply Changes to install the tile.

Server name differences in SCS v3.x

SCS v3.x includes a new Config Server service, and a new Service Registry service. Both have been renamed compared to their v2.x versions:

• Config Server service: p.config-server (previously p-config-server)
• Service Registry service: p.service-registry (previously p-service-registry)

Network connectivity requirements

A client accessing Config Server or Registry over HTTPS is successful without specifying any additional ports. If traffic is coming to the foundation, then this should work, too. See Writing Client Applications.

If the service registry employs container-to-container networking, then you must add a network policy, but you don’t need to configure any specific ports.

The ports required for Config Server depend on the backend used:

• If you are using a Git backend, the config server only communicates directly with the mirror service over SSH. Therefore, you must allow communication over port 22. The mirror service may also communicate with the Git server over SSH or HTTPS, so both port 22 and 443 must be open.
• If you are using Vault, you must allow traffic to your Vault servers. The Vault servers are external, so you should know the ports to open.

You also need all of the standard ports open for BOSH-deployed VMs.

Differences between v3.x Config Server and earlier config server

The p.config-server service includes new features (including the CredHub backend) and can run alongside the services included in SCS v2.1 and earlier versions. You may want to deactivate the older p-config-server service and allow only the new p.config-server Config Server service to be created.

Older Config Server service instances cannot be upgraded to the new p.config-server service. Instead, you must recreate p-config-server service instances. Most parameters used to create a p-config-server service instance with the Cloud Foundry CLI (cf CLI), using the cf create-service command with the -c flag, can also be used to create a p.config-server service instance.

The following parameters are exceptions that can be used with the p-config-server service but cannot be used with the p.config-server service:

• git.repos
• composite.git
• composite.vault

See Composite Backends for information about how to configure the composite backend in the SCS v3.x Config Server.

SCS v3.x service instances are backwards-compatible with version 2.0.1.RELEASE of the SCS client dependencies.

Upgrading from SCS v3.0-v3.1 to SCS v3.2

In SCS v3.2, Config Server uses main as the default label, rather than master, which was used in earlier versions.

• If all of your service instances are configured with a label explicitly, the upgrade can be done by running the upgrade-all-instances errand during 3.2.x tile installation or later.

• If the service instances rely on the default value (master) for the label, do the following before running the upgrade-all-instances errand:

  • Git backends: You can rename the master branch to main or create a new branch called main from the master branch. Alternatively, you can update all service instances by setting label to master explicitly.

  • CredHub backends: You need to update all secrets by replacing master with main in their path.