Skip to content

Update solo network deploy --deployment to support multiple clusters #1357

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.

Sign up for GitHub

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

Jump to bottom
Closed
jeromy-cannon opened this issue Feb 11, 2025 · 2 comments · Fixed by #1389
Closed

Update solo network deploy --deployment to support multiple clusters #1357

jeromy-cannon opened this issue Feb 11, 2025 · 2 comments · Fixed by #1389
Assignees
@leninmehedy @jeromy-cannon
Labels
Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. P0 An issue impacting production environments or impacting multiple releases or multiple individuals. released on @0.35.x released

Comments

@jeromy-cannon
Copy link
Contributor

jeromy-cannon commented Feb 11, 2025 •
edited by leninmehedy
Loading 

### Tasks
- [ ] update Network Deploy to use the remote config to determine which node aliases go to which cluster-ref
- [ ] update Network Deploy for each task to be able to run against the correct cluster for cluster commands and which cluster/node for node comands
- [ ] make updates so that Network Deploy is only running its commands for the correct nodes on the correct cluster-ref
- [ ] add a user message stating which cluster-ref is currently being ran
- [x] be able to take a values file override for each cluster-ref
- [ ] be able to handle this: `solo network deploy --deployment(*) --values-file aws-cluster=aws/solo-values.yaml,aws-cluster=aws/solo-values2.yaml,gcp-cluster=gcp/solo-values.yaml,gcp-cluster=gcp/solo-values2.yaml`
@jeromy-cannon jeromy-cannon added Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. P0 An issue impacting production environments or impacting multiple releases or multiple individuals. labels Feb 11, 2025
This was referenced Feb 11, 2025
Merged
Merged
@leninmehedy leninmehedy mentioned this issue Feb 12, 2025
Merged
@jeromy-cannon jeromy-cannon mentioned this issue Feb 13, 2025
Merged
@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
Assignees

@leninmehedy leninmehedy

@jeromy-cannon jeromy-cannon

Labels
Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. P0 An issue impacting production environments or impacting multiple releases or multiple individuals. released on @0.35.x released
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: add basic multi-cluster support to solo network deploy hiero-ledger/solo
3 participants
@leninmehedy @jeromy-cannon @swirlds-automation