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.

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

[#1086] use cr.name as broker name in restricted mode #1087

Merged
merged 2 commits into from
Jan 23, 2025

Conversation

gtully
Copy link
Contributor

@gtully gtully commented Jan 22, 2025

No description provided.

@gtully gtully requested a review from brusdev January 22, 2025 17:05
@brusdev
Copy link
Contributor

brusdev commented Jan 23, 2025

Another limitation of the non-restricted deployment is that all broker instances related to a single ActiveMQArtemis CR have the same broker name. Is it a limitation also in restricted mode?

@gtully
Copy link
Contributor Author

gtully commented Jan 23, 2025

in restricted mode, the plan size will be restricted to 1. I have raised #1089 to enforce this. good catch

@gtully
Copy link
Contributor Author

gtully commented Jan 23, 2025

I have updated this PR with the fix to #1089 thanks!

@gtully
Copy link
Contributor Author

gtully commented Jan 23, 2025

Another limitation of the non-restricted deployment is that all broker instances related to a single ActiveMQArtemis CR have the same broker name. Is it a limitation also in restricted mode?

yes. but even more restricted in that the deployment size should always be the default of 1. It should be ignored.

@brusdev brusdev merged commit 7f03be4 into arkmq-org:main Jan 23, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants