Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix typo #31

Merged
merged 1 commit into from
Jun 6, 2024
Merged

Fix typo #31

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/pods.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,10 @@
# NAME

Pods. Almost everything you need to know about the pods used by NITA.
``pods``. Almost everything you need to know about the pods used by NITA.

# SYNOPSIS

``nita-cmd kube [ pods | versions ] ``\
``nita-cmd [ ips | stats ]``\
``nita-cmd [ ansible | jenkins | robot | webapp ] cli <args>...``\
``kubectl [ get | exec | describe ]``

Expand Down Expand Up @@ -57,12 +56,14 @@ You can use the ``nita-cmd kube pods`` command to get information about the infr
If you read the nita-cmd documentation you will see that it is in fact just a wrapper for other shell scripts. When you run the ``nita-cmd kube pods`` command,
it is actually running the ``kubectl get pods -n nita`` command and filtering the output. For example, to see what pods are currently running on the NITA host, do this:

```
$ nita-cmd kube pods
NAME READY STATUS RESTARTS AGE
db-7cc98cd974-t4ppb 1/1 Running 3 (132m ago) 90d
jenkins-768f9cd99b-fprh8 1/1 Running 3 (132m ago) 90d
proxy-86dfdffcf5-zqzmq 1/1 Running 3 (133m ago) 90d
webapp-75d694ff55-xk252 1/1 Running 3 (132m ago) 90d
```

## Accessing a Container's Shell

Expand Down