KubeConfigMerger object poorly structured when KUBECONFIG is a list of files.

[ralberrto]

I'm new around here and I was exploring the configuration flow/data structures and I ran into the realization that when I have the following set of config files:

KUBECONFIG=~/.kube/config-1:~/.kube/config-2:~/.kube/config-3

A KubeConfigMerger is constructed as follows (I went for a JSON representaiton of the object):

{
  "KubeConfigMerger.config": {
    "ConfigNode": {
      "name": "path-1",
      "path": "path-1",
      "value": {
        "clusters": [
          {
            "ConfigNode": {
              "name": "path-1/{\"cluster\": {\"server\": \"server-1\"}, \"name\": \"cluster-name-1\"}\n",
              "path": "path-1",
              "value": {
                "cluster": {
                  "server": "server-1"
                },
                "name": "cluster-name-1"
              }
            }
          },
          {
            "ConfigNode": {
              "name": "path-2/{\"cluster\": {\"server\": \"server-2\"}, \"name\": \"cluster-name-2\"}\n",
              "path": "path-2",
              "value": {
                "cluster": {
                  "server": "server-2"
                },
                "name": "cluster-name-2"
              }
            }
          },
          {
            "ConfigNode": {
              "name": "path-3/{\"cluster\": {\"server\": \"server-3\"}, \"name\": \"cluster-name-3\"}\n",
              "path": "path-3",
              "value": {
                "cluster": {
                  "server": "server-3"
                },
                "name": "cluster-name-3"
              }
            }
          }
        ],
        "contexts": [
          {
            "ConfigNode": {
              "name": "path-1/{\"context\": {\"cluster\": \"server-1\", \"namespace\": \"namespace-1\", \"user\": \"user-1\"}, \"name\": \"context-name-1\"}\n",
              "path": "path-1",
              "value": {
                "context": {
                  "cluster": "server-1",
                  "namespace": "server-1",
                  "user": "user-1"
                },
                "name": "context-name-1"
              }
            }
          },
          {
            "ConfigNode": {
              "name": "path-2/{\"context\": {\"cluster\": \"server-2\", \"namespace\": \"namespace-2\", \"user\": \"user-2\"}, \"name\": \"context-name-2\"}\n",
              "path": "path-2",
              "value": {
                "context": {
                  "cluster": "server-2",
                  "namespace": "server-2",
                  "user": "user-2"
                },
                "name": "context-name-2"
              }
            }
          },
          {
            "ConfigNode": {
              "name": "path-3/{\"context\": {\"cluster\": \"server-3\", \"namespace\": \"namespace-3\", \"user\": \"user-3\"}, \"name\": \"context-name-3\"}\n",
              "path": "path-3",
              "value": {
                "context": {
                  "cluster": "server-3",
                  "namespace": "server-3",
                  "user": "user-3"
                },
                "name": "context-name-3"
              }
            }
          }
        ],
        "users": [
          {
            "ConfigNode": {
              "name": "path-1/{\"user\": {\"token\": \"token-1\"}, \"name\": \"user-name-1\"}\n",
              "path": "path-1",
              "value": {
                "user": {
                  "token": "token-1"
                },
                "name": "user-name-1"
              }
            }
          },
          {
            "ConfigNode": {
              "name": "path-2/{\"user\": {\"token\": \"token-2\"}, \"name\": \"user-name-2\"}\n",
              "path": "path-2",
              "value": {
                "user": {
                  "token": "token-2"
                },
                "name": "user-name-2"
              }
            }
          },
          {
            "ConfigNode": {
              "name": "path-3/{\"user\": {\"token\": \"token-3\"}, \"name\": \"user-name-3\"}\n",
              "path": "path-3",
              "value": {
                "user": {
                  "token": "token-3"
                },
                "name": "user-name-3"
              }
            }
          }
        ],
        "current_context": "current-context"
      }
    }
  }
}

So now the question is: Is the main ConfigNode whose atributes path and name take the name of the first file structured as intended?

[ralberrto]

I can see that the KubeConfigMerger.config is consumed by KubeConfigLoader as a ConfigNode, so I'm guessing those two attributes are just a consequence of the ConfigNode requiring them and are probably set there to not much purpose?

[yliaog]

/assign @ralberrto