# WebTTY, Logs, Shell Access

## ✅ Prepare your WebTTY

{% content-ref url="/pages/6Lt7THKcrasjl5i7evFj" %}
[Create WebTTY](/stackos-docs/operations/create-webtty.md)
{% endcontent-ref %}

## ✅ List your Pods

Use command `kubectl get pods` to see the list of all pods.

## ✅ Exec a shell (ssh-like access)

To execute the shell, use command `kubectl exec -ti`` `<mark style="color:blue;background-color:orange;">**`appname-0xADDRESS-random`**</mark> `-- bash`

Your WebTTY will now switch to a command line for your pod.

## ✅ Get the logs

`kubectl logs -f appname-0xADDRESS-random`&#x20;

## ✅ `Quickly Check HTTP`

`curl appname-0xADDRESS`

`This is really helpful for checking function internally before trying to debug external access`

## ✅ Working with ReplicaSets

ReplicaSets "manage" the pods/containers that you ultimately interact with.

Sometimes after changing configurations on the WebUI, you may have an old replica set that does not automatically go away.  It could be waiting on a shutdown or some other resource.

**You can list replica sets,** look for the oldest one matching the application you are managing and delete the old ReplicaSet

`kubectl get rs`

**Locate the "rs" you wish to delete**

`kubectl delete rs  rsname-0xADDRESS-random`&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.stackos.io/stackos-docs/operations/webtty-logs-shell-access.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.