Releases: cloudfoundry/bosh-aws-cpi-release
Releases · cloudfoundry/bosh-aws-cpi-release
v105
v104
v103
v102
Known Issues
- Due to the way gems are bundled with Ruby 3.2, it's possible that deploying the CPI via a bosh director (i.e. using bosh to deploy bosh) may cause the CPI to not have access to the gems. This is fixed in v103.
What's Changed
- Add an example for aws metadata options by @scult in #157
- Update Ruby to version 3.2.3 by @mvach in #159
New Contributors
Full Changelog: v101...v102
v101
v100
v99
v98
Breaking Changes
This version of the CPI removes the ability to configure blobstore settings for a deployed VM using the CPI. The standard way to configure blobstore settings is to send them as part of the agent environment section, e.g:
env:
bosh:
blobstores: [
...
]
For bosh create-env
deployments, this configuration is under the resource_pools
section of the manifest. You can refer to this example in bosh-deployment.
If you do not set blobstore settings under the agent environment section, your deployment may go unresponsive when upgrading to this CPI.
What's Changed
- adding i4i and storage maps by @blyles in #145
- Remove blobstore info from IaaS metadata endpoints by @ystros in #147
- Add assume role support in the AWS CPI by @danielfor in #148
New Contributors
- @ystros made their first contribution in #147
- @danielfor made their first contribution in #148
Full Changelog: v97...v98