Support one global team config with multiple clusters

[hlascelles]

We have multiple clusters, with multiple services in each cluster. We'd like to add just one config file to source control for all clusters. I see the config file has been designed with that in mind in the future (I think?) but it currently errors if more than one cluster is provided.

eg, we would like to define:

{
  "_clusters": [
    {
      "name": "arn:aws:eks:eu-west-1:12345678:cluster/foo",
      "_services": [
        {
          "alias": "foo-baz",
          "namespace": "kube-system",
          "workloadType": "service",
          "workloadName": "prometheus",
          "forwards": [
            {
              "localPort": 6600,
              "remotePort": 80,
              "id": "38cdf30d-062d-499d-87f0-f60b0e91dcdf"
            }
          ]
        }
      ]
    },
    {
      "name": "arn:aws:eks:eu-west-1:12345678:cluster/bar",
      "_services": [
        {
          "alias": "bar-baz",
          "namespace": "kube-system",
          "workloadType": "service",
          "workloadName": "prometheus",
          "forwards": [
            {
              "localPort": 6800,
              "remotePort": 80,
              "id": "6678abc7-cfb2-461f-921e-336a92b9e80b"
            }
          ]
        }
      ]
    }
  ]
}

I'd like to start kube-forwarder pointing at this one file. Then, a dev just pulls our git repo and it (optionally) hot reloads.

I think a couple of other issues touch on this, but I've not seen a request for "one file multiple cluster" support.

[proAlexandr]

Hi @hlascelles, thanks for using the app! Do I properly understand that you want to be able to export multiple clusters in one file?

[hlascelles]

Yes, essentially, that's it. :+1: Also somehow start the app pointing at a file one disk (ie in our team repo).