Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PEM certificate generation: support multiple replicas #192

Closed
lavocatt opened this issue Jun 21, 2024 · 1 comment · Fixed by #271
Closed

PEM certificate generation: support multiple replicas #192

lavocatt opened this issue Jun 21, 2024 · 1 comment · Fixed by #271
Assignees
@lavocatt
Labels
bug Something isn't working task/feature
Milestone
Stabilize the UI

Comments

@lavocatt
Copy link
Collaborator

lavocatt commented Jun 21, 2024 •
edited
Loading

ATM there aren't correct support for multiple replicas on the reducer. An easy way could be to simply add a host in the patch for every pod in the deployment:

image

This has for effect to spawn two ingresses:

image

Which is functional. However, using this strategy we can't use the ingress round robin for load balancing.

So I'm wondering, is this the right approach?

@brusdev and @gtully I'm pinging you here to have your opinion on the matter.
@lavocatt lavocatt added the question Further information is requested label Jun 21, 2024
@lavocatt
Copy link
Collaborator Author

After chatting with @brusdev let's implement this solution.

@lavocatt lavocatt added bug Something isn't working task/feature and removed question Further information is requested labels Jun 26, 2024
@lavocatt lavocatt added this to the stabilize the UI milestone Jul 5, 2024
@lavocatt lavocatt self-assigned this Jul 5, 2024
lavocatt added a commit to lavocatt/activemq-artemis-self-provisioning-plugin that referenced this issue Aug 13, 2024
@lavocatt
[artemiscloud#192] support multiple hosts for the PEM case
b2ccc5a 
Add support for multiple hosts to be exposed via an ingress when the
user selects several replicas. Each pod gets exposed and has its own url
to get connected to.

The connectivity helper shows the url of the currently selected pod.

fixes artemiscloud#192
@lavocatt lavocatt mentioned this issue Aug 13, 2024
Merged
lavocatt added a commit to lavocatt/activemq-artemis-self-provisioning-plugin that referenced this issue Aug 14, 2024
@lavocatt
[artemiscloud#192] support multiple hosts for the PEM case
2704da0 
Add support for multiple hosts to be exposed via an ingress when the
user selects several replicas. Each pod gets exposed and has its own url
to get connected to.

The connectivity helper shows the url of the currently selected pod.

fixes artemiscloud#192
lavocatt added a commit to lavocatt/activemq-artemis-self-provisioning-plugin that referenced this issue Aug 14, 2024
@lavocatt
[artemiscloud#192] support multiple hosts for the PEM case
63588d4 
Add support for multiple hosts to be exposed via an ingress when the
user selects several replicas. Each pod gets exposed and has its own url
to get connected to.

The connectivity helper shows the url of the currently selected pod.

fixes artemiscloud#192
lavocatt added a commit to lavocatt/activemq-artemis-self-provisioning-plugin that referenced this issue Aug 19, 2024
@lavocatt
[artemiscloud#192] support multiple hosts for the PEM case
001dd94 
Add support for multiple hosts to be exposed via an ingress when the
user selects several replicas. Each pod gets exposed and has its own url
to get connected to.

The connectivity helper shows the url of the currently selected pod.

fixes artemiscloud#192
lavocatt added a commit to lavocatt/activemq-artemis-self-provisioning-plugin that referenced this issue Aug 19, 2024
@lavocatt
[artemiscloud#192] support multiple hosts for the PEM case
2055498 
Add support for multiple hosts to be exposed via an ingress when the
user selects several replicas. Each pod gets exposed and has its own url
to get connected to.

The connectivity helper shows the url of the currently selected pod.

fixes artemiscloud#192
lavocatt added a commit to lavocatt/activemq-artemis-self-provisioning-plugin that referenced this issue Aug 19, 2024
@lavocatt
[artemiscloud#192] support multiple hosts for the PEM case
e280d75 
Add support for multiple hosts to be exposed via an ingress when the
user selects several replicas. Each pod gets exposed and has its own url
to get connected to.

The connectivity helper shows the url of the currently selected pod.

fixes artemiscloud#192
lavocatt added a commit to lavocatt/activemq-artemis-self-provisioning-plugin that referenced this issue Aug 19, 2024
@lavocatt
[artemiscloud#192] support multiple hosts for the PEM case
06d0fee 
Add support for multiple hosts to be exposed via an ingress when the
user selects several replicas. Each pod gets exposed and has its own url
to get connected to.

The connectivity helper shows the url of the currently selected pod.

fixes artemiscloud#192
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lavocatt lavocatt

Labels
bug Something isn't working task/feature
Projects
None yet
Milestone
Stabilize the UI
Development

Successfully merging a pull request may close this issue.

[#192] support multiple hosts for the PEM case lavocatt/activemq-artemis-self-provisioning-plugin
1 participant
@lavocatt