2.6.11

Coerce registry values for published helm charts

- Change the registry from something to the correct value on production
  deploys of the helm charts.
- Update changelog

Code reviewed by Mark

2.6.1-rc1

• Updated buildpacks
• Switched buildpacks from offline to online buildpacks. That means the shipped images are smaller and dependencies are downloaded on demand during application staging time
• Use SLE stack by default
• Cleaned up variable names. There is a more consistent naming scheme now. You might need to adjust some configuration if you see error messages about unknown names.

2.5.0-beta4

• CF v280
• Fix BOSH Caching
• Remove Consul and ETCD
• Workaround for Kube/Docker bug where hostname -i return nothing
• cf-usb no longer downloads all of mysql
• Rename CA cert for UAA (affects install commands)

v2.4.1-beta3

• Fixed an issue with stateful set upgrades so they automatically upgrade now

2.4.0-beta3

Upgrade-ability

The main theme of this release was to address the ability to upgrade the system. This was done by the inclusion of the secret generator job which detects what secrets must be generated and how by looking at the role manifest and the secrets provided by the user via helm.

Other notable Changes

• Bump to CF v278
• Bump to UAA v52
• Bump grootfs to v0.30.0
• RBAC Compatibility for newer kubes
• Helm charts are now generated not templatized
• Increase blobstore volume size to accomodate large buildpacks
• Increase send_timeout for blobstore uploads to accomodate large buildpacks
• Re-add cf-usb tests
• Use NA blobstore for cf-usb mariadb binaries
• Add a cached libvirt option that will download all images

2.3.1-beta2

• CF v272
• Persi with NFS driver
• .NET Core Buildpack
• Default anti-affinity rules
• Support for private and secure Docker registries
• Better support for HA configuration from the end-user

Known issues:
Vagrant is currently having trouble building, if it fails with an overlay2 device busy kind of message simply run make compile again.

2.2.0-beta

• high availability deployments are possible

2.1.0-alpha

• cf-usb is now available for use

2.0.3-alpha

• Fix an issue where the permissions on the newly separated grootfs volume were wrong

2.0.2-alpha

• Correct issue where volumes were tagged with the same tag (and therefore didn't end up separate)