kubens lists all namespaces to validate your choice, and your identity is not allowed to - common on Rancher and locked-down clusters. The misleading no namespace exists line is just kubens failing closed after the denied list. Work around it with kubens --force [name] (sets the namespace without verifying, per the atago spec), or get list on namespaces granted.

## The error
```text
Error from server (Forbidden): namespaces is forbidden: User "[user]" cannot list resource "namespaces" in API group "" at the cluster scope
error: no namespace exists with name "[name]".
```

## What to do
1. Confirm the RBAC gap:
```bash
kubectl auth can-i list namespaces
```
   Expected: Prints `no`.
2. Set the namespace without the list check:
```bash
kubens --force [name]
```
   Expected: Namespace set in the context without contacting the list API.
3. Verify it took:
```bash
kubectl config view --minify -o jsonpath='{.contexts[0].context.namespace}'
```
   Expected: Prints the namespace name.
4. Durable fix: have an admin grant list on namespaces, or at least get on the specific namespace.
   Expected: kubens works without --force.

## When this applies
- kubens failing with a Forbidden line on namespaces
- Rancher and other RBAC-heavy platforms
- single-namespace users who can not list

## When it does NOT apply
- plain typos where you CAN list namespaces (drop --force, fix the name)
- forbidden on pods or other resources

## Works with
kubens (ahmetb/kubectx) with --force

### interactive kubens picker shows nothing
Same denied list behind the picker. Use kubens --force [name] with the exact name.

## Why it happens
kubens validates names by listing namespaces, a cluster-scoped read. Users scoped to one namespace usually lack it, so the validation - not the namespace - is what fails.

## Edge cases
- --force skips validation entirely, so a typo lands you in a nonexistent namespace - double-check the name.
- kubectl config set-context --current --namespace=[name] never validates either, which is the same escape hatch.

## Resolved from
gh:ahmetb/kubectx#83 - https://github.com/ahmetb/kubectx/issues/83