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

Add support for using the load balancer address as the external gossip address #1402

Closed
nathanklick opened this issue Feb 15, 2025 · 2 comments · Fixed by #1405
Closed

Add support for using the load balancer address as the external gossip address #1402

nathanklick opened this issue Feb 15, 2025 · 2 comments · Fixed by #1405
Labels
Feature Enhancement Enhancing an existing feature driven by business requirements. Typically backwards compatible. P0 An issue impacting production environments or impacting multiple releases or multiple individuals. released on @0.35.x released

Comments

@nathanklick
Copy link
Member

nathanklick commented Feb 15, 2025

Feature to Enhance

Consensus Node Deployment (network deploy)

Requested Enhancement

The network deploy command currently uses the cluster internal DNS name for the external gossip address in the config.txt and genesis-network.json address books.

This needs to be changed to use the loadBalancerIP address from the haproxy Service endpoint when the --load-balancer switch is enabled on the network deploy command.

Business Need

Required to support deployments using load balancers.

Additional Context

No response

@nathanklick nathanklick added Feature Enhancement Enhancing an existing feature driven by business requirements. Typically backwards compatible. Pending Triage New issue that needs to be triaged by the team P0 An issue impacting production environments or impacting multiple releases or multiple individuals. and removed Pending Triage New issue that needs to be triaged by the team labels Feb 15, 2025
@swirlds-automation
Copy link
Contributor

🎉 This issue has been resolved in version 0.35.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@swirlds-automation
Copy link
Contributor

🎉 This issue has been resolved in version 0.35.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Enhancement Enhancing an existing feature driven by business requirements. Typically backwards compatible. P0 An issue impacting production environments or impacting multiple releases or multiple individuals. released on @0.35.x released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants