-
Notifications
You must be signed in to change notification settings - Fork 99
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(cluster): use external_address in cql_ip_address #6382
Conversation
Replace usage of ip_address with external_address as it more suitable for purpose to be a public address.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I'll need more information here, where did we see an issue with this code, with siren ? I thought we were using VPC peering and not using public addresses ? Anyhow please run azure artifact test to validate this doesn't break it. |
Yes, siren-tests is the case when we use False for INTRA_NODE_COMM_PUBLIC and True for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixing the changes introduced in #6062 for the case if INTRA_NODE_COMM_PUBLIC is False.
Note, that it's not required to replace second occurrence of
ip_address
withexternal_address
.PR pre-checks (self review)
backport
labelsNew configuration option are added and documented (insdcm/sct_config.py
)I have added tests to cover my changes (Infrastructure only - underunit-test/
folder)