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

Backport 1.9: Support go-sockaddr templates in top-level cluster_addr config (#13678) #13706

Merged
merged 3 commits into from
Jan 20, 2022

Conversation

ncabatoff
Copy link
Collaborator

In doing some testing I found that the listener clusteraddr isn't really used, or at least isn't as important as the top-level clusteraddr setting. As such, go-sockaddr templating needs to be implemented for the top-level cluster_addr setting or it's unusable for HA.

Also fix a nil pointer panic I discovered at the same time.

In doing some testing I found that the listener clusteraddr isn't really used, or at least isn't as important as the top-level clusteraddr setting.  As such, go-sockaddr templating needs to be implemented for the top-level `cluster_addr` setting or it's unusable for HA.

Also fix a nil pointer panic I discovered at the same time.
@ncabatoff ncabatoff requested a review from a team January 19, 2022 16:07
@vercel vercel bot temporarily deployed to Preview – vault January 20, 2022 13:33 Inactive
@vercel vercel bot temporarily deployed to Preview – vault-storybook January 20, 2022 13:33 Inactive
@ncabatoff ncabatoff merged commit 4e1213e into release/1.9.x Jan 20, 2022
@ncabatoff ncabatoff deleted the backport-pr-13705-1.9 branch January 20, 2022 13:56
akshya96 pushed a commit that referenced this pull request Jan 20, 2022
… (#13706)

In doing some testing I found that the listener clusteraddr isn't really used, or at least isn't as important as the top-level clusteraddr setting.  As such, go-sockaddr templating needs to be implemented for the top-level `cluster_addr` setting or it's unusable for HA.

Also fix a nil pointer panic I discovered at the same time.
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.

None yet

2 participants