@lulf lulf released this Sep 12, 2018 · 28 commits to master since this release

Assets 3
  • New address type ‘subscription’ available in standard address space. This can be used to create durable subscription queues.
  • New API for managing users in standard authentication service using custom resources (kubectl/oc).
  • Routers static config from configmap
  • Several bugfixes to mqtt components

@lulf lulf released this Aug 15, 2018 · 126 commits to master since this release

Assets 3
  • Upgrade to Apache Qpid Dispatch Router 1.3.0
  • Upgrade to Apache ActiveMQ Artemis 2.6.2
  • Enable native OpenSSL support in Artemis
  • Use one connection in each direction between router and broker
  • Split Ansible playbooks into a project admin and cluster admin playbook

@lulf lulf released this Aug 15, 2018 · 128 commits to master since this release

Assets 3
  • Upgrade to Apache Qpid Dispatch Router 1.3.0
  • Upgrade to Apache ActiveMQ Artemis 2.6.2
  • Enable native OpenSSL support in Artemis
  • Use one connection in each direction between router and broker
  • Split Ansible playbooks into a project admin and cluster admin playbook

See the Changelog

@lulf lulf released this Jun 21, 2018 · 195 commits to master since this release

Assets 3
  • Upgrade to dispatch router 1.1.0 + some extra bugfixes
  • Add support for web sockets in standard address space
  • Set common name and subject alternative names for self-signed route certs on OpenShift
  • Experimental RBAC support for Kubernetes
  • Bug fixes to allow console and rest api to work better on addresses created by the other
  • Bug fix to topic-forwarder allowing queues and topics with multiple shards to work again
  • Allow kubernetes - api server connection to be secured using mutual TLS

See the CHANGELOG

Jun 20, 2018
Update version to 0.21.0-rc2
Jun 20, 2018
Update version to 0.21.0-rc1

@lulf lulf released this May 24, 2018 · 287 commits to master since this release

Assets 3
  • 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.