[EnMasse] EnMasse 0.31.1 RC4 available

[Keith Wall]

+1

My testing was:

* Installed from YAML bundle on CRC (4.3.8)
* Created a standard and brokered address space with addresses
* Sent messages to/from those addresses
* Kicked the tyres in the Console.

* Installed from YAML bundle on minikube (v1.9.2)
* Created a standard and brokered address space with addresses
* Sent messages to/from those addresses


On Tue, Apr 21, 2020 at 5:51 PM Keith Wall <kwall at redhat.com> wrote:
>
> Hi all
>
> EnMasse version 0.31.1 RC4 is available for testing:
>
> https://github.com/EnMasseProject/enmasse/releases/tag/0.31.4-rc4
>
> The changes since 0.31.0 are as follows:
>
> * #4046: add network-only as fetch policy for all queries
> * #4090: Provide per-address space support credentials facilitating
> support access to the broker(s) (#4276)
> * #4184: Sometimes controller crashes when reconciling authentication service
> * #4241: Fix a race in upgrader logic that prevented upgrade from continuing
> * #4242: #4246: Delegate authentication vrtx worker thread pool making
> authentication multi threaded.  Improve error handling.
> * #4245: standard-auth - use AMQP port probe rather than keycloak HTTP endpoint
> * #4252: Add idleTimeout, role and maxFrameSize settings for connectors
> * #4266: Add broker.globalMaxSize to the infraconfig CRDs
> * #4269: bump Netty dependency from netty-4.1.45.Final to netty-4.1.48.Final
> * #4279: handled null check for address space plan (#4277)
> * #4280: Edit Address Space dialogue subtitle misleading
> * #4282: add null check for links in address links page (#4262)
> * #4287: Address links not displayed if address resource name suffix
> does not match address name
> * #4292: Escape forbidden chars in filters
> * #4317: Addresses with different casing is not becoming ready
> * #4331: Issues installing monitoring resources (#4200) (#4222)
> * #4332: Unable to drain kube node when broker pod is deployed there
>
> Best regards