k9s-commando: opties en 11 voorbeelden

Dit deel is nog niet vertaald. Je ziet de Engelse tekst.

Wat het doet

k9s shows your cluster live in the terminal. Type : and a resource name (:pods, :deploy, :svc, :events) to jump there; / filters; Enter goes inside. It uses your kubeconfig and your RBAC rights, like kubectl.

It is fast for troubleshooting: see a crashing pod, press l for logs, d to describe, s for a shell.

Zo schrijf je het

k9s [OPTIONS]

Opties 17

Meest gebruikt

Start options

-n, --namespace NS: Start in a namespace.
-A, --all-namespaces: Start with all namespaces.
--context NAME: Use another kubeconfig context.
-c, --command RES: Start in a view (for example -c deploy).
--readonly: No delete, edit or shell (safe on production).
--kubeconfig FILE: Use another kubeconfig.
-l, --logLevel debug: Log level of k9s itself.
info: Show where k9s keeps config and logs.

Keys

: RES: Go to a resource view (pods, deploy, svc, ns, events, ctx).
/ TEXT: Filter the list.
l / p: Logs / previous logs of the pod.
d / y / e: Describe / YAML / edit.
s: Shell into the container.
shift-f: Port-forward.
ctrl-d / ctrl-k: Delete / kill.
0 / 1-9: All namespaces / favourite namespaces.
? / esc / ctrl-c: Help / back / quit.

Voorbeelden 11

$ als gewone gebruiker# als root (of met sudo)

1Start in a namespace
```
$k9s -n shop
```
2Safe view on production
```
$k9s --context prod --readonly
```
3Start in the Deployments view
```
$k9s -c deploy -A
```
4Find crashing pods
```
$k9s -n shop -c pods
```
Type /Crash to filter, then l for the logs and p for the logs before the restart.
5Look at events of the namespace
```
$k9s -n shop -c events
```
Sort by age with shift-a.
6Restart a deployment
```
$k9s -n shop -c deploy
```
Select it, press r (rollout restart).
7Port-forward to a service
```
$k9s -n shop -c svc
```
Select it, press shift-f and choose the port.
8Change the context
```
$k9s -c ctx
```
Select the cluster, press Enter.
9Where are the k9s config and logs?
```
$k9s info
```
10Use another kubeconfig file
```
$k9s --kubeconfig ~/.kube/lab.yaml
```

11Debug a k9s problem

$k9s -l debug
$tail -f "$(k9s info | awk '/Logs/{print $2}')"

Let op

k9s can delete and edit with one key; use --readonly or a read-only RBAC user on production.
It shows only what your RBAC allows; missing views often mean missing rights.

Bestanden

~/.config/k9s/: Config, skins, aliases (see k9s info).

Tips om te onthouden

Learn kubectl first (exams have no k9s), then use k9s for speed at work.

Exitcodes

`0`	Normal exit.
`1`	Error (for example the cluster cannot be reached).

`k9s`

Wat het doet

Zo schrijf je het

Opties 17

Start options

Keys

Voorbeelden 11

1Start in a namespace

2Safe view on production

3Start in the Deployments view

4Find crashing pods

5Look at events of the namespace

6Restart a deployment

7Port-forward to a service

8Change the context

9Where are the k9s config and logs?

10Use another kubeconfig file

11Debug a k9s problem

Let op

Bestanden

Tips om te onthouden

Exitcodes

Volledige handleiding

k9s

Wat het doet

Zo schrijf je het

Opties 17

Start options

Keys

Voorbeelden 11

1Start in a namespace

2Safe view on production

3Start in the Deployments view

4Find crashing pods

5Look at events of the namespace

6Restart a deployment

7Port-forward to a service

8Change the context

9Where are the k9s config and logs?

10Use another kubeconfig file

11Debug a k9s problem

Let op

Bestanden

Tips om te onthouden

Exitcodes

Verwante commando's

Gebruikt in deze lessen

Volledige handleiding

`k9s`