Skip to content
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.

0.20.0
Compare
Choose a tag to compare
@lulf lulf released this 24 May 10:34
· 2790 commits to master since this release
0.20.0
08b91d1

  • REST API now served by a new component, api-server, code moved from the old address-controller. The intention is to have this act as a kubernetes API server, allowing custom resource support for address spaces and addresses. This is experimental at present and not ready for production use[2]. An example ansible inventory file that can be used with the ansible install procedure[3] is provided.

  • REST API paths have changed in preparation for custom resources support. An API reference available at [4]. A short summary:

    • The /apis/enmasse.io/v1 prefix has changed to /apis/enmasse.io/v1alpha1 which better reflects the state of our APIs in terms of breaking changes.
    • Address spaces are now namespaced, which means that you can create address spaces with the same name in different namespaces. This means the path to address space resources are now /apis/enmasse.io/v1alpha1/namespaces/[:namespace]/addressspaces
    • The path /apis/enmasse.io/v1/addresses API has 'moved' to /apis/enmasse.io/v1alpha/addressspaces/[:addressspace]/addresses`.
    • A new API under /apis/enmasse/v1alpha1/namespaces/[:namespace]/addresses have been introduced to support custom resources for addresses.

  • address-controller renamed to address-space-controller

  • Kubernetes and OpenShift resources/templates are no longer split into separate folders, but now categorized by component. This means that the different components like authentication service, address space controller, rest api etc. can be managed and upgraded individually if desired which simplifies operations in cases where you want more control.

  • Performance improvements to handling large number of addresses in agent

  • Removal of per-address resource limits in broker as there was a lower limit than expected on how many addresses and limit settings a broker could handle

  • Bug fixes and enhancements to console, address space controller, agent and more

[1] https://github.com/EnMasseProject/enmasse/releases/download/0.20.0/enmasse-0.20.0.tgz
[2] #1265
[3] http://enmasse.io/documentation/0.20.0/#installing_enmasse_using_ansible
[4] http://enmasse.io/documentation/0.20.0/#rest_api_reference

See the CHANGELOG

Known issues:

  • To use custom resources, the user must be cluster admin. Currently no cluster-role is provided to allow creating address spaces and addresses.
Assets 3