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

fix: allow nats address to include a port #35

Merged
merged 1 commit into from
May 27, 2024
Merged

Conversation

protochron
Copy link
Contributor

Feature or Problem

This fix omits the preset NATS leaf node port 7422 from being automatically set if the natsAddress field is set in the CRD. This allows you to specify the port if it is not using the default at the cost of making it required.

Related Issues

Release Information

next

Consumer Impact

Testing

Tested locally with kind connected to a NATS cluster serving leaf node connections on a different port than the default

Copy link

github-actions bot commented May 27, 2024

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails

Scanned Manifest Files

This fix omits the preset NATS leaf node port `7422` from being
automatically set if the `natsAddress` field is set in the CRD. This
allows you to specify the port if it is not using the default at the
cost of making it required.

Signed-off-by: Dan Norris <protochron@users.noreply.github.com>
@protochron protochron merged commit 178ee27 into main May 27, 2024
5 checks passed
@protochron protochron deleted the fix_port_spec branch May 27, 2024 19:07
protochron added a commit that referenced this pull request May 28, 2024
PR #35 introduced a small regression which only impacts clients who are
trying to use nonstandard ports. This fixes the problem by allowing the
NATS leaf node and client ports to be configured separately in the CRD.
protochron added a commit that referenced this pull request May 28, 2024
PR #35 introduced a small regression which only impacts clients who are
trying to use nonstandard ports. This fixes the problem by allowing the
NATS leaf node and client ports to be configured separately in the CRD.

Signed-off-by: Dan Norris <protochron@users.noreply.github.com>
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.

3 participants