Skip to content

v2.1.2

Compare
Choose a tag to compare
@genesis-bot genesis-bot released this 17 Feb 18:56
· 161 commits to main since this release

Feature Updates

  • Adds v1 vm support fix back in
  • Better support for vm_types, especially in context of upgrading from v1 environments.
  • Updated Credhub and UAA to newer version to fix Log4J vulnerabilities

New feature v1-vm-types sets up the manifest to use the same VM types as was used in the v1.x versions of the kit, or as close to possible. This allows you to use your existing cloud config and tuning. Where the instance group name changes, it will use the vm type that the instance group was migrated from.

The exceptions are tcp-router, which will use the router vm type, and cc-worker and credhub, which continue to use minimum as there was no prevous instance group for these functions.

Fixes spelling of scheduler in MANUAL.MD

  • Removes references to adapter/syslogger instances/vms.
  • This has been merged with syslog jobs as of cf-deployment v15.7.0, and implemented in v2.1.0 of this kit

Bug Fixes:

  • Environments migrated from v1.x were suppose to retain the blobstore name
    for the app packages blobstore (was -packages- in v1.x,
    moved to -app-packages- to better match canonical in
    v2.0.x for new environment). This has been restored. If you upgraded to
    v2.0.x, you can keep the new blobstore name by adding the following to your
    environment:

    meta:
      blobstore_bucket_path:
        app-packages: (( concat meta.blobstore_bucket_prefix "-app-packages-" meta.blobstore_bucket_suffix ))
    
  • Environments migrated from v1.x now correctly retain the original NATS user
    credentials. Upstream used a different username, and as such, when
    upgrading to v2.0.x, there was a loss of connectivity to NATS. Migrated
    environments now retain the original v1.x username.

    If you have already upgraded your environment from v1.x to 2.0.x, you can
    specify feature v2-nats-credentials to prevent NATS username from
    switching back and causing further availability outage during deployment.

Release updates:

Name Old Version Version Changed
binary-buildpack 1.0.36 1.0.40 yes
bosh-dns-aliases 0.0.3 0.0.4 yes
bpm 1.1.9 1.1.14 yes
capi 1.107.0 1.119.0 yes
cf-cli 1.32.0 1.34.0 yes
cf-networking 2.35.0 2.39.0 yes
cf-smoke-tests 41.0.2 no
cflinuxfs3 0.229.0 0.262.0 yes
credhub 2.9.0 2.11.1 yes
diego 2.49.0 2.53.0 yes
dotnet-core-buildpack 2.3.24 2.3.34 yes
garden-runc 1.19.19 1.19.30 yes
go-buildpack 1.9.27 1.9.36 yes
haproxy 9.8.0 no
java-buildpack 4.36 4.42 yes
log-cache 2.11.4 2.11.4 yes
loggregator 106.5.0 106.6.0 yes
loggregator-agent 6.2.0 6.3.4 yes
metrics-discovery 3.0.3 3.0.6 yes
migrate-postgres 1.0.1 yes
nats 39 40 yes
nginx-buildpack 1.1.21 1.1.32 yes
nodejs-buildpack 1.7.44 1.7.62 yes
php-buildpack 4.4.33 4.4.46 yes
postgres 43 no
pxc 0.33.0 0.39.0 yes
python-buildpack 1.7.32 1.7.46 yes
r-buildpack 1.1.13 1.1.22 yes
routing 0.212.0 0.225.0 yes
ruby-buildpack 1.8.33 1.8.47 yes
silk 2.35.0 2.39.0 yes
staticfile-buildpack 1.5.16 1.5.25 yes
statsd-injector 1.11.15 1.11.16 yes
uaa 75.0.0 75.14.0 yes