Releases: genesis-community/cf-genesis-kit
v0.1.10
Updates to something similar to cf-release v258. Compatible from 0.1.9, and can migrate from v0.2.x if your subkits match.
All job properties are specified at the template level now instead of as globals. This is to get on the path towards migrating to something more cf-deployment-esque.
For a list of release changes, here is a commit: b7b056d
v0.2.9
v0.2.8
V 0.2.7
v0.2.6
New Feature
- Though recommended to use the default structure, it is now possible to specify alternate domains for the system, api and app domains. This allows legacy systems to be migrated to use this kit.
v0.2.5
v0.2.4
Bug Fix
- Erroneous naming of smoke-tests instance group as smoke_tests fixed.
Breaking Change
This kit uses a version of the Cloud Controller that has privileged access to Diego turned off by default, so if you rely on root access inside Diego containers, you will need to manually enable them: https://github.com/cloudfoundry/cf-deployment/blob/e82d67dd5d2de88d4c4d307da0dffd52ecd849b6/operations/enable-privileged-container-support.yml
v0.1.9
Improvements
- Bumped nfs-volume-services to 1.0.7
- Based on cf-release
v0.2.0
New Features
cf-genesis-kit
is now based directly (instead of loosely) on cf-deployment. It is currently using v0.22.0 of cf-deployment.- TCP routing is now supported via the
tcp-router
subkit - An internal MySQL db cluster is supported for the CF databases, using the
db-internal-mysql
subkit - OpenStack's Swift blobstore is now available via the
blobstore-swift
subkit
Bug Fixes
- Fixed a couple issues that were causing problems when
cells
were updating
v0.1.8
Improvements
Bumped nfs-volume release to v1.0.5 for the Volume Services nfsv3driver