Validate a RemoteConfig with a deployment that has one cluster instance

[jeromy-cannon]

• design: Create design for RemoteConfig #657
• list of mutable commands: Create design for RemoteConfig #657 (comment)
• See: details about parsing to/from YAML in: Create a Local Config for storing configurations on the users machine #590
• NOTES:
  • The RemoteConfig Kubernetes ConfigMap which is namespace specific will be called solo-remote-config with a label of solo.hedera.com/type: remote-config

Feature: during the constructor after invoking read we validate a RemoteConfig with a deployment that has one cluster instance (exclude: mirror-node, mirror-node-explorer, relay)

  The RemoteConfig instance will be stored in each Kubernetes cluster defined in the deployment.  The LocalConfig will have the mappings to get the cluster and context mapping.  The RemoteConfig in the given deployment(namespace)/cluster/context will be read and converged into a RemoteConfig instance.  Then it will be validated to ensure it is usable for Solo.  This is a simple deployment with running consensus nodes, and their supporting HAProxy and Envoy proxy services.

  Scenario: the RemoteConfig validation for a single cluster does not match the name or number of consensus nodes (network node services)
    Given the RemoteConfig has been read
    And the deployment is for a single cluster
    When the the consensus node services name, cluster, or number of for the given namespace/cluster/context does not match the RemoteConfig
    Then a SoloError will be thrown explaining that the expected name, cluster, or number of consensus node services and the actual consensus node services for the namespace/cluster/context does not match
    And the user will need to manually bring it back into sync

  Scenario: the RemoteConfig validation for a single cluster does not match the name, cluster, or number of HAProxy services
    Given the RemoteConfig has been read
    And the deployment is for a single cluster
    When the name, cluster, or number of HAProxy services for the given namespace/cluster/context does not match the RemoteConfig
    Then a SoloError will be thrown explaining that the expectedname, cluster, or number of HAProxy services and the actual HAProxy services for the namespace/cluster/context does not match
    And the user will need to manually bring it back into sync

  Scenario: the RemoteConfig validation for a single cluster does not match the name, cluster, or number of Envoy proxy services
    Given the RemoteConfig has been read
    And the deployment is for a single cluster
    When the name, cluster, or number of Envoy proxy services for the given namespace/cluster/context does not match the RemoteConfig
    Then a SoloError will be thrown explaining that the expected name, cluster, or number of Envoy proxy services and the actual Envoy proxy services for the namespace/cluster/context does not match
    And the user will need to manually bring it back into sync

  Scenario: the RemoteConfig validation for a single cluster does not match the name or number of clusters listed
    Given the RemoteConfig has been read
    And the deployment is for a single cluster
    When the name or number of clusters for the given namespace/cluster/context does not match the RemoteConfig
    Then a SoloError will be thrown explaining that the expected name or number of clusters and the actual clusters for the namespace/cluster/context does not match
    And the user will need to manually bring it back into sync

[jeromy-cannon]

closed this as completed in #922