Skip to content

Releases: cloudfoundry/bosh-aws-cpi-release

v105.0.1

01 Nov 20:20
Compare
Choose a tag to compare

Fixed CVEs:

What's Changed

New Contributors

Full Changelog: v105...v105.0.1

v105

14 Aug 06:04
Compare
Choose a tag to compare

What's Changed

  • New NVMe instance types by @svrc in #164
  • Use the dualstack support of the aws-sdk to support IPv6 by @max-soe in #163
  • Add a config parameter to enable dualstack if needed by @max-soe in #166

New Contributors

Full Changelog: v104...v105

v104

24 Apr 15:07
Compare
Choose a tag to compare

Feature

  • Support for EFI based stemcells

Full Changelog: v103...v104

v103

18 Apr 23:34
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v102...v103

v102

09 Apr 17:19
Compare
Choose a tag to compare

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

16 Nov 17:42
Compare
Choose a tag to compare

What's Changed

  • Add support for 7th gen compute optimized vm types by @nimeshjm in #153
  • add 6th gen general purpose instance stores by @nimeshjm in #154
  • Allow use of "deprecated" stemcell AMIs (see fe649d3 for details)

Full Changelog: v100...v101

v100

22 Sep 14:31
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v99...v100

v99

23 Jun 12:42
Compare
Choose a tag to compare
v99

What's Changed

  • adding x2iezn for gp3 support with nvme by @blyles in #150
  • Updated gems and bumped Ruby to 3.1.4

Full Changelog: v98...v99

v98

26 Apr 19:10
Compare
Choose a tag to compare
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

New Contributors

Full Changelog: v97...v98

v97

15 Feb 11:10
Compare
Choose a tag to compare
v97

What's Changed

Full Changelog: v96...v97