LATEST VERSION: 1.10 - CHANGELOG
Pivotal Cloud Foundry v1.10

PCF Runtime for Windows v1.10 Release Notes

Releases

1.10.0

Component Version
Stemcell1056.0
consul153
diego1.7.6
garden-windows0.4.0
loggregator77
HWC Buildpack2.3.2

Operators can install PCF Runtime for Windows on vSphere, Amazon Web Services (AWS), Google Cloud Platform (GCP), or Azure.

How to Upgrade

The PCF Runtime for Windows tile is available with the release of Pivotal Cloud Foundry (PCF) version 1.10. To use the PCF Runtime for Windows tile, you need OpsManager 1.10.3 or later and Elastic Runtime 1.10.0 or later.

For information about upgrading to PCF Runtime for Windows v1.10.0, see the Upgrading Windows Cells topic in the PCF Runtime for Windows documentation.

New Features in PCF Runtime for Windows 1.10

  • Cell local communication between Diego rep and Consul agent is secured.
  • Windows Buildpack support:
    • The tile installs the HWC buildpack for enabling IIS applications without running the full IIS process.
    • Supports the binary buildpack included with ERT 1.10.0, used to run Windows .exe and .bat executables.
    • For apps that use the older start command, the tile provides a warning after upgrade.
    • Backwards compatible with old apps.
  • The 1.10 Runtime for Windows tile can be deployed as an isolation segment.
  • The CF healthcheck is configurable for Windows apps.
  • The IPSec add-on is supported to secure communications between Windows and Linux virtual machines.

Known Issues

New Issues

  • Pushing .exe and .bat files with the binary buildpack requires ERT 1.10.3 or later (binary buildpack 1.0.11 or later).
  • AWS S3 blobstores are known not to work with GCP deployments.

Notes

  • Note that any behavior that restarts the Windows OS will result in BOSH resurrecting the cell. Pivotal-provided stemcells are configured to disable any auto-restart behaviors.
  • cf ssh is not supported.
Create a pull request or raise an issue on the source for this page in GitHub