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

feat(multi-cluster): add multi-cluster support for all node commands #1416

Open
wants to merge 26 commits into
base: main
Choose a base branch
from

Conversation

instamenta
Copy link
Contributor

@instamenta instamenta commented Feb 17, 2025

Description

  • Modify all node commands

Related Issues

Copy link
Contributor

github-actions bot commented Feb 17, 2025

Unit Test Results - Linux

  1 files  ±0   62 suites  ±0   3s ⏱️ -1s
241 tests ±0  241 ✅ ±0  0 💤 ±0  0 ❌ ±0 
250 runs  ±0  250 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 4b6a5ed. ± Comparison against base commit d2f7b21.

♻️ This comment has been updated with latest results.

Copy link
Contributor

github-actions bot commented Feb 17, 2025

Unit Test Results - Windows

  1 files  ±0   62 suites  ±0   2s ⏱️ -2s
241 tests ±0  241 ✅ ±0  0 💤 ±0  0 ❌ ±0 
250 runs  ±0  250 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 4b6a5ed. ± Comparison against base commit d2f7b21.

♻️ This comment has been updated with latest results.

…r-prevent-nodes-from-being-deployed-to-all-clusters-instead-of-the-one-specified
@instamenta instamenta marked this pull request as draft February 18, 2025 08:46
…r-prevent-nodes-from-being-deployed-to-all-clusters-instead-of-the-one-specified
@instamenta instamenta marked this pull request as ready for review February 19, 2025 11:57
@instamenta instamenta changed the title feat(multi-cluster): modify the node commands 'updateChartWithConfigMap' task to work with multi-cluster setup feat(multi-cluster): add multi-cluster support for all node commands Feb 19, 2025
… adding node to the remote config

Signed-off-by: instamenta <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
…r-prevent-nodes-from-being-deployed-to-all-clusters-instead-of-the-one-specified
Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
@jeromy-cannon jeromy-cannon added the PR: Checks Failed A pull request where the checks have failed. label Feb 20, 2025
Signed-off-by: Zhan Milenkov <[email protected]>
…r-prevent-nodes-from-being-deployed-to-all-clusters-instead-of-the-one-specified
…r-prevent-nodes-from-being-deployed-to-all-clusters-instead-of-the-one-specified

# Conflicts:
#	src/commands/network.ts
#	test/e2e/commands/node_upgrade.test.ts
#	test/e2e/commands/separate_node_upgrade.test.ts
Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
…r-prevent-nodes-from-being-deployed-to-all-clusters-instead-of-the-one-specified
Signed-off-by: Zhan Milenkov <[email protected]>
@JeffreyDallas
Copy link
Contributor

Some E2E test failed, and it is hard to pin down what changes broke the tests.
I am trying to split the PR to a few small ones so it will be easier to debug.

@JeffreyDallas
Copy link
Contributor

Some tests failed because there were some insistencies in the code how context is retrieved.
Some times it got from local config as cluster-1, for E2E tests, it is hard coded in test/data/local_config.yaml

userEmailAddress: [email protected]
soloVersion: '0.0.0'
deployments:
  deployment:
    clusters:
      - cluster-1
    namespace: solo-e2e
clusterRefs:
  cluster-1: context-1
  cluster-2: context-2

sometimes context is retrieved from flag value which is kind-solo-e2e

Then this led to unexisted key in the map this.localConfig.clusterRefs

@JeffreyDallas JeffreyDallas requested review from a team as code owners February 22, 2025 20:51
…xmulti-cluster-prevent-nodes-from-being-deployed-to-all-clusters-instead-of-the-one-specified
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: Checks Failed A pull request where the checks have failed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fix(multi-cluster): prevent nodes from being deployed to all clusters instead of the one specified
3 participants