Skip to content

docs: document service-mesh support for porter app run #307

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

Open
mintlify wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: document service-mesh support for porter app run #307

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions standard/cli/command-reference/porter-app.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,7 @@ porter app run [application] -- COMMAND [args...] [flags]
| `--allow-concurrent` | Allow concurrent job runs when using `--job` (overrides job config if concurrency is disabled) |
| `--cpu` | CPU allocation in millicores (1000 millicores = 1 vCPU) |
| `--ram` | RAM allocation in Mi (1024 Mi = 1 GB) |
| `-c`, `--container` | Name of the container inside the pod to run the command in. If omitted, the first non-sidecar application container is selected automatically |
|`-v` | Print verbose output |

<Warning>
Expand Down Expand Up @@ -72,6 +73,14 @@ porter app run my-app --cpu 500 --ram 512 -- python heavy_script.py
In these examples, we use `bash` and `python`, but those commands need to actually be present within the container to run. With very lightweight containers, you may find that none of these are available. If you run into trouble here, feel free to reach out to the support team.
</Info>

<Info>
**Service mesh support:** `porter app run` works on services with Linkerd injected without any extra flags. The CLI automatically skips the `linkerd-proxy` sidecar when picking a container, and ephemeral copy pods are created without the proxy injected. If you need to target a specific container explicitly, use `-c` / `--container`:

```bash
porter app run my-app -c my-container -- bash
```
</Info>

---

## `porter app run cleanup`
Expand Down