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: add options for setting NATS leaf and client ports separately #37

Merged
merged 1 commit into from
May 28, 2024

Conversation

protochron
Copy link
Contributor

Feature or Problem

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.

Related Issues

Release Information

next

Consumer Impact

Testing

Works locally in kind

Unit Test(s)

Acceptance or Integration

Manual Verification

@protochron protochron requested a review from joonas May 28, 2024 13:50
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>
Copy link

github-actions bot commented May 28, 2024

Dependency Review

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

OpenSSF Scorecard

PackageVersionScoreDetails

Scanned Manifest Files

@protochron protochron merged commit cfc139f into main May 28, 2024
5 checks passed
@protochron protochron deleted the fix_nats_ports branch May 28, 2024 13:57
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