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

Use kubernetes ingress feature #16

Closed
lulf opened this issue Mar 30, 2017 · 4 comments
Closed

Use kubernetes ingress feature #16

lulf opened this issue Mar 30, 2017 · 4 comments

Comments

@lulf
Copy link
Member

lulf commented Mar 30, 2017

To allow EnMasse to work with kubernetes, routes needs to be replaced with ingress. OpenShift can be configured to create routes automatically based on ingress resources.

@lulf
Copy link
Member Author

lulf commented Mar 30, 2017

openshift/origin#12416

@lulf
Copy link
Member Author

lulf commented Mar 31, 2017

Using https://github.com/fabric8io/exposecontroller is also an alternative for supporting older openshift versions

@lulf
Copy link
Member Author

lulf commented Apr 3, 2017

@lulf lulf closed this as completed Apr 5, 2017
@lulf
Copy link
Member Author

lulf commented Apr 5, 2017

Ingress is now created for console and address controller

lulf pushed a commit that referenced this issue Jun 29, 2017
Add dockerized version of activemq 5.13
lulf pushed a commit that referenced this issue Jun 29, 2017
Add support for mqtt-style wildcards and hierarchical topics
lulf pushed a commit that referenced this issue Jun 29, 2017
Use reply_to instead of JMSReplyTo to work with broker
lulf pushed a commit that referenced this issue Jun 30, 2017
[#2] Added right message identifier handling
lulf pushed a commit that referenced this issue Jun 30, 2017
fix router requests after reconnection
vbusch pushed a commit to vbusch/enmasse that referenced this issue Nov 27, 2019
…-status-phase

Expose AddressSpace and Address Status Phase
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant