-
**Describe the bug**
Now that address-space-controller is deployed from enmasse-operator uninstalling enmasse doing `oc delete -f ...` over the bundle leaves the address-space-controller deployment. …
-
I have set up a large OpenShift cluster using Ansible, and then deploying EnMasse with a secured connection (mTLS) between the master and the EnMasse API server.
Even though the cluster appears to…
-
At present, we have the group 'user.enmasse.io' for MessagingUser APIs. For consistency, I think we should consider introduce the API group 'address.enmasse.io' for AddressSpace and Address resources.
-
**Describe the bug**
It is currently possible to create two messaging users sharing the same metadata name but with distinct usernames.
```Oslo:enmasse keith$ oc get messagingusers
NAME …
-
**Describe the bug**
When installing EnMasse using OLM, the purge feature does not work.
This is due to missing permissions for the agent service account to create tokenreviews.
-
**Describe the bug**
When creating a lot of addresses, the enmasse-operator will start crashing due to OOM. A working theory is that the operator is watching configmaps and not doing the appropriate …
-
Maybe it's something related to the underlying Artemis broker but if I try to subscribe with MQTT just on "#" (for getting ALL the messages, as it's possible due to the MQTT 3.1.1 specification) I get…
-
The AddressSpace and Address APIs allow the user to put arbitrary metadata annotations on the objects. This presumably to allow the user to add business domain specific annotations to drive business …
-
Broker failed while testPubSubLong is running with message "Terminating due to java.lang.OutOfMemoryError: Java heap space"
test is io.enmasse.systemtest.marathon.StandardMarathonTest.testTopicPubS…
-
The current implementation of the Device Registry doesn't provide any security, meaning the API can be accessed without authentication. Therefore it cannot be used in production. Originally it was pla…