PCF Runtime for Windows v1.12 Release Notes

Operators can install PCF Runtime for Windows on vSphere, Amazon Web Services (AWS), Google Cloud Platform (GCP), or Azure. See the Deploying PCF Runtime for Windows topic for more information.

Releases

1.12.2

  • Bumps stemcell to v1200.4.

Component Version
Stemcell1200.4
consul173
diego1.25.3
event_log0.2
garden-windows0.7.0
hwc-offline-buildpack2.3.8
loggregator96
windows-utilities0.3.0
* Components marked with an asterisk have been patched to resolve security vulnerabilities or fix component behavior.

1.12.1

  • [Feature] Bumps diego-release to v1.25.3 to include support for Azure MySQL Release Notes.
  • Removes the “Advanced Features” section as these features do not have any impact on Diego functionality.

Component Version
Stemcell1200.3
consul173
diego1.25.3
event_log0.2
garden-windows0.7.0
hwc-offline-buildpack2.3.8
loggregator96
windows-utilities0.3.0
* Components marked with an asterisk have been patched to resolve security vulnerabilities or fix component behavior.

1.12.0

Component Version
Stemcell1200.3
consul173
diego1.25.1
event_log0.2
garden-windows0.7.0
hwc-offline-buildpack2.3.8
loggregator96
windows-utilities0.3.0
* Components marked with an asterisk have been patched to resolve security vulnerabilities or fix component behavior.

How to Upgrade

The PCF Runtime for Windows v1.12 tile is available with the release of Pivotal Cloud Foundry (PCF) version v1.12. To use the PCF Runtime for Windows tile, you need Ops Manager v1.12.0 or later and Elastic Runtime v1.12.0 or later.

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

Note: If your existing PCF v1.11.x installation includes both PCF Runtime for Windows and MySQL for PCF v1.x, you must upgrade to MySQL for PCF v1.10.3 or later before you upgrade to PCF Elastic Runtime v1.12. For instructions on how to upgrade MySQL for PCF, see the MySQL for PCF documentation.

New Features in PCF Runtime for Windows v1.12

This section describes new features of the release.

BOSH SSH Support

If operators select a checkbox when configuring the PCF Runtime for Windows 1.12 tile, users can SSH onto Windows VMs with the bosh ssh command. For more information, see the Deploying PCF Runtime for Windows topic.

Note: This feature is beta and not considered production-ready.

Operators Can Manage the Windows Admin Password

Operators can now manage a password strategy for the Windows admin user on Windows VMs when configuring the PCF Runtime for Windows. They can use the Windows default password, specify a password, or generate random passwords for each VM. For more information, see the Deploying PCF Runtime for Windows topic.

Windows Event Logs Consumable via Syslog

Operators can now configure a syslog endpoint for Windows Event Logs in the PCF Runtime for Windows tile. Windows Events Logs provide a consolidated, system-level logging mechanism that is especially useful in troubleshooting problems with running applications. For more information, see the Deploying PCF Runtime for Windows topic.

Improved Security

Diego Cells now use the Metron API v2. This gRPC-based API supports mutual TLS authentication and ensures that Metrons in PCF Runtime for Windows are protected from spoofing attacks.

Application Instance Identity Credentials

The instance identity system in Diego provides each app container with a PEM-encoded X.509 certificate and PKCS #1 RSA private key. The values of the environment variables CF_INSTANCE_CERT and CF_INSTANCE_KEY contain the absolute paths to the certificate and private key files. The validity period is 3 years for the Instance Identity root and 2 years for the intermediate CA certificates.

See the App Instance Container Identity Credentials section for more information.

KMS Host Configuration

Operators can configure their Windows VMs to register with and activate against an operator-defined KMS host via runtime configuration. See Configuring a KMS Host.

Diego Cell Max-in-Flight Default

This release lowers the default max-in-flight percentage on Diego Cells to 4%. Previously, this value was set to 10%, which can cause the following issues in larger environments:

  • Many simultaneous VM creates/deletes and BOSH blob updates placing significant stress on the underlying infrastructure, especially on vSphere which has a greater probability of being under-provisioned.
  • Cells that are draining are no longer available for allocation, resulting in a 10% decrease in total memory and disk capacity during deployment. This can cause deployments to no longer have sufficient total capacity to run all work, or to have insufficient headroom to place larger workloads successfully.

Operators can still use the Ops Manager API to configure this setting to fit their needs. For more information about this property, see Managing Diego Cell Limits During Upgrade.

About Advanced Features

The Advanced Features pane of the PCF Runtime for Windows tile includes new functionality that may have certain constraints. Although these features are fully supported, Pivotal recommends caution when using them in production.

Create a pull request or raise an issue on the source for this page in GitHub