Pivotal ships Spring Cloud Services update just in time for summer

Pivotal ships Spring Cloud Services update just in time for summer

Pivotal has shipped Spring Cloud Services v3.0.0, but if you’re really attached to v2.0.x, don’t worry. You can run both versions of the microservices management platform alongside each other.

The side by side option seems to be mainly be down to the fact that “the current Service Registry and Circuit Breaker Dashboard services are not included in the SCS v3.0.0 release.”

So, as Pivotal puts it, “In order to maintain the availability of current Service Registry and Circuit Breaker Dashboard capabilities in your marketplace, both the SCS v2.0.x and SCS v3.0.0 tiles should be deployed and used “side by side” in your PCF environment.

The upgrade does include a number of new features, with Pivotal highlighting the debut of a “mirror” service, which it said was a response to feedback from users who ran large numbers of Config Servers instances per PCF foundation.

These were typically configured to use Git repositories from the same Git server, which could lead to “a significant load on the Git server during a Pivotal Application service upgrade. This meant each Config Server instance’s backing application was relocated to a new cell, which meant recloning the Git repository, often leading to “a tremendous load”.

The mirror service will cache the user’s configuration, and “reduce this back and forth chatter significantly”, and increase the availability of the Git repositories configured on Confit Server.

The update also sees CredHuib secrets management being added to Config Server, with each instance having “a secured path for secrets in the Pivotal Application Service (PAS) CredHub.” This can be accessed via an API.

Other changes in Spring Cloud Services include changing the way Config Server instances are provisioned via the PCF marketplace “ever-so-slightly”, and a change to the installation profiles, meaning no more RabbitMQ or MySQL tile dependencies.

Full details and links to the documentation are here.