Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

CHE_WORKSPACE_NAMESPACE value set in workspace does not match the CHE_INFRA_KUBERNETES_NAMESPACE_DEFAULT pattern

See original GitHub issue

If CHE_INFRA_KUBERNETES_NAMESPACE_DEFAULT=foo-<username> then the runtime value for CHE_WORKSPACE_NAMESPACE on has the <username> part.

The namespace itself is correct; just the env variable value is wrong.

Issue Analytics

State:
Created 4 years ago
Comments:14 (7 by maintainers)

Top GitHub Comments

1reaction

mingfangcommented, Mar 13, 2020

@metlos @mingfang Does it mean that the issue is solved?

What is the reason you don’t expose the name of the Kubernetes namespace?

I workaround this issue using the Downwards API like this https://github.com/mingfang/terraform-provider-k8s/blob/master/devfile.yaml#L33

1reaction

metloscommented, Mar 12, 2020

We don’t expose the name of the Kubernetes namespace (or OpenShift project) the workspace runs in. The CHE_WORKSPACE_NAMESPACE environment variable contains what can basically be described as the name of the owner of the workspace. I’ve created a PR to the Che documentation to clarify the meaning of that environment variable.

Top Results From Across the Web

Angular workspace configuration

Angular CLI configuration optionslink. The following configuration properties are a set of options that customize the Angular CLI. Property, Details, Value type ...