0.0.8

Version 0.0.8 is the eight Alpha-quality release of the service catalog. Below are some highlights from this release:

• Cleaning up and fixing bugs in TPR backed storage (#723, #836, #720, #600 )
• More conformance to the OSB spec:
  • Sending arguments in query parameters vs. parameters, no bodies on deletes, etc. (#884, #883)
• General cleanup and bug fixes

0.0.7

Version 0.0.7 is the seventh Alpha-quality release of the service catalog. Below are some highlights from this release:

• We've made quite a few modifications to our data types, in preparation for the backward compatibility in the upcoming 0.1.0. Here are some of the PRs that made such changes: #862, #861, #859, #846, #843, #839
• We've made the controller be multi-node aware. When multiple controller pods start up, they all elect a single leader
• We've added infrastructural support for admission controllers to our API server. We've also added an initial admission controller in this release. We plan on expanding the scope of our admission controllers in future releases

0.0.6

Version 0.0.6 is the sixth Alpha-quality release of the service catalog. Below are some highlights from this release:

• We've promoted third party resource storage for the API server to alpha. It is still in development, but we've amended the walkthrough to indicate how to use this storage mode
• We now only allow Bindings to Instances that are ready, and to Instances that point to ServiceClasses that are marked as bindable: true
• We've made further investments into our test suites, including:
  • Go-based end-to-end tests running in Jenkins
  • Full integration test support for third party resource storage
  • Improved unit coverage for third party resource storage

0.0.5

Version 0.0.5 is the fifth Alpha-quality release of the service catalog. Below are some highlights from this release:

• service-catalog now supports asynchronous provision and deprovision responses from brokers
• We've added an end-to-end testing framework (based on the one that Kubernetes core uses), and started building more tests on top of it
• We've improved the update function in third party resource backed storage
• We've disabled bindings on services that are not bindable
• We've thoroughly documented how to configure and run the server and your client in "secure mode"

0.0.4

Version 0.0.4 is the fourth Alpha-quality release of the service catalog. Much of the release was focused on:

• Making the controller more generally robust
• Adding logic to emit events from the controller
• Added preliminary code and documentation standards
• Added support in the controller for arbitrary authn/authz when talking to the core API server

0.0.3

Version 0.0.3 is the third Alpha-quality release of the service catalog. Much of the release was focused on:

• Fixing flaky tests and adding more logging to better be able to diagnose test failures
• adding context-profile support
• adding lastTransitionTime to API conditions
• Documentation / code comments cleanup
• removing old examples and dead code

0.0.2

Version 0.0.2 is the second Alpha-quality release of the service catalog. It has many small fixes such as correctly supporting asynchronous provision and deprovision and passing descriptions of ServiceClass and ServicePlan correctly. Additionally, the vendor directory is now checked in to source control to ensure that we will be able to build future versions even if dependencies move. Version 0.0.2 is based on the kubernetes 1.6 machinery.

Version 0.0.1

Version 0.0.1 is the first Alpha quality release of the service catalog. It has minor improvements over version 0.0.1-RC2, including more documentation refinements and a naming fix for ServiceClass third party resources.

0.0.1 (Release Candidate 2)

This is the second release candidate for version 0.0.1. Here are the major additions we've made since the first release candidate:

• We've moved the walk through to its own file and improved it. It's still incomplete, but you can expect to have it finished prior to version 0.0.1
• The system now allows _ (underscore) characters in plan names
• The controller now can talk to broker servers that have improperly configured certificates. See #605 for more details on exactly what it does now
• We've made a few fixes to chart documentation

0.0.1 (Release Candidate 1)

This is the first release candidate for version 0.0.1. It contains a basic service catalog implementation, intended for initial testing by SIG-Service-Catalog contributors before KubeCon EU 2017.

This release candidate contains the API server and Controller Manager, with support for the following resources:

• Broker
• ServiceClass (created from Broker submissions)
• Instance
• Binding

The API server stores each of these resources in its own data storage system, which can either be backed by Third Party Resources or an on-cluster etcd.

Please see the service-catalog helm chart for details on how to install the entire service-catalog system with either storage system.