Create second deployment on google cluster got "Remote config already exists" error

[JeffreyDallas]

Describe the bug

Trying to create a second deployment so explorer can be deployed to different namespace vs mirror code

But got the following error

[solo:mirror-node] ******************************* Solo *********************************************
[solo:mirror-node] Version			: 0.34.0
[solo:mirror-node] Kubernetes Context	: gke_hashsphere-staging_us-central1_jeromy-sphere-load-test-us-central
[solo:mirror-node] Kubernetes Cluster	: gke_hashsphere-staging_us-central1_jeromy-sphere-load-test-us-central
[solo:mirror-node] Current Command		: deployment create --deployment explorer-deployment --namespace explorer-name-space --context gke_hashsphere-staging_us-central1_jeromy-sphere-load-test-us-central --email [email protected] --deployment-clusters gke_hashsphere-staging_us-central1_jeromy-sphere-load-test-us-central --dev
[solo:mirror-node] Kubernetes Namespace	: explorer-name-space
[solo:mirror-node] **********************************************************************************
[solo:mirror-node] ❯ Initialize
[solo:mirror-node] ✔ Initialize
[solo:mirror-node] ❯ Setup home directory
[solo:mirror-node] ✔ Setup home directory
[solo:mirror-node] ❯ Prompt local configuration
[solo:mirror-node] ↓ Prompt local configuration [SKIPPED: Prompt local configuration]
[solo:mirror-node] ❯ Add new deployment to local config
[solo:mirror-node] ✔ Add new deployment to local config
[solo:mirror-node] ❯ Resolve context for remote cluster
[solo:mirror-node] ✔ Resolve context for remote cluster
[solo:mirror-node] ❯ Validate context
[solo:mirror-node] ✔ Validate context- validated context gke_hashsphere-staging_us-central1_jeromy-sphere-load-test-us-central
[solo:mirror-node] ❯ Update local configuration
[solo:mirror-node] ✔ Update local configuration
[solo:mirror-node] ❯ Validate cluster connections
[solo:mirror-node] ❯ Testing connection to cluster: gke_hashsphere-staging_us-central1_jeromy-sphere-load-test-us-central
[solo:mirror-node] ✔ Testing connection to cluster: gke_hashsphere-staging_us-central1_jeromy-sphere-load-test-us-central
[solo:mirror-node] ✔ Validate cluster connections
[solo:mirror-node] ❯ Create remoteConfig in clusters
[solo:mirror-node] cluster = gke_hashsphere-staging_us-central1_jeromy-sphere-load-test-us-central, context = gke_hashsphere-staging_us-central1_jeromy-sphere-load-test-us-central, namespace = explorer-name-space
[solo:mirror-node] ❯ Create remote config in cluster: gke_hashsphere-staging_us-central1_jeromy-sphere-load-test-us-central
[solo:mirror-node] Remote config already exists
[solo:mirror-node] ✖ Create remote config in cluster: gke_hashsphere-staging_us-central1_jeromy-sphere-load-test-us-central [FAILED: Remote config already exists]
[solo:mirror-node] ✖ Create remoteConfig in clusters [FAILED: Remote config already exists]
[solo:mirror-node] *********************************** ERROR *****************************************
[solo:mirror-node] Error creating deployment
[solo:mirror-node] ***********************************************************************************

When creating two different deployment on local cluster does not have such error

If in file remote_config_manager.ts comment out the throw exception line in function createAndValidate,
then it worked.

    self.unload();
    if (await self.load()) {
      self.logger.showUser(chalk.red('Remote config already exists'));
      // throw new SoloError('Remote config already exists');
    }

Describe the expected behavior

Should not have error

To Reproduce

Create second deployment on google cluster

test branch 00929-D-mirror-proxy-second with solo-chart branch 09555-D-ingress-controller

Additional Context