Set the namespace in generated kubeconfig

[l0rd]

Is your enhancement related to a problem? Please describe

The Dashboards generates a ~/.kube/config at workspace startup. But the context in the generated kubeconfig is missing the namespace:

{
  "apiVersion": "v1",
  "kind": "Config",
   (...)
  "contexts": [
    {
      "name": "logged-user",
      "context": {
        "user": "developer",
        "cluster": "inCluster",
        "name": "logged-user"
      }
    }
  ],
  "preferences": {},
  "current-context": "logged-user"
}

This can have some side effects because clients rely on kubeconfig to find the current namespace:

$ oc project
No project has been set. Pass a project name to make that the default.

Note that workspace Pod namespace is available at /var/run/secret/kubernetes.io/serviceaccount/namespace.

Describe the solution you'd like

The namespace should be set in the context

[ibuziuk]

PR has been merged. Closing

[dmytro-ndp]

There was "namespace": "admin-devspaces" in ~/.kube/config of workspace started using Eclipse Che Next:

quarkus-api-example (main) $ cat ~/.kube/config
{
  "apiVersion": "v1",
  "kind": "Config",
  "clusters": [
    {
      "name": "inCluster",
      "cluster": {
        "server": "https://172.30.0.1:443",
        "certificate-authority": "/var/run/secrets/kubernetes.io/serviceaccount/ca.crt",
        "insecure-skip-tls-verify": false
      }
    }
  ],
  "users": [
    {
      "name": "developer",
      "user": {
        "token": "sha256~jN9zZr"
      }
    }
  ],
  "contexts": [
    {
      "name": "logged-user",
      "context": {
        "user": "developer",
        "cluster": "inCluster",
        "name": "logged-user",
        "namespace": "admin-devspaces"
      }
    }
  ],
  "preferences": {},
  "current-context": "logged-user"
}
quarkus-api-example (main) $ oc project
Using project "admin-devspaces" from context named "logged-user" on server "https://172.30.0.1:443".

As a result, oc project command was using user namespace.

Issue looks fixed as expected.

[max-cx]

sync'd to Red Hat JIRA https://issues.redhat.com/browse/CRW-4344

[nickboldt]

Given this is for .kube and not openshift... is this a Che only N&N item? @l0rd

[devstudio-release]

sync'd to Red Hat JIRA https://issues.redhat.com/browse/CRW-4344

• feat: Set the namespace in generated kubeconfig che-dashboard#771

[l0rd]

Given this is for .kube and not openshift... is this a Che only N&N item? @l0rd

No this issue if for Dev Spaces too. kubeconfig is used by oc too.