github/dokku
0
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

chore: fix some typos in comment

Browse Source 
Signed-off-by: fmtappendf <fmtappendf@gmail.com>
This commit is contained in:
fmtappendf
2026-10-08 16:20:11 +08:00
parent 8f78c37bfd
commit d82d0088a1
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/deployment/schedulers/k3s.md
View File

@@ -1090,7 +1090,7 @@ See the [Kustomize](https://kustomize.io/) website for more details on how to us
### Using kubectl remotely
> [!WARNING]
> Certain ports must be open for interacting with the remote kubernets api. Refer to the [K3s networking documentation](https://docs.k3s.io/installation/requirements?os=debian#networking) for the required open ports between servers prior to running the command.
> Certain ports must be open for interacting with the remote kubernetes api. Refer to the [K3s networking documentation](https://docs.k3s.io/installation/requirements?os=debian#networking) for the required open ports between servers prior to running the command.
By default, Dokku assumes that all it controls all actions on the cluster, and thus does not expose the `kubectl` binary for administrators. To interact with kubectl, you will need to retrieve the `kubeconfig` for the cluster and configure your client to use that configuration.

2
docs/deployment/schedulers/scheduler-management.md
View File

@@ -123,7 +123,7 @@ At this time, the following dokku commands are used to implement a complete sche
- triggers: post-app-clone-setup
- `cron`: generates cron tasks for the app
- triggers: scheduler-uses-host-cron, scheduler-cron-write
- `deploy`: deploys app proceses and checks the status of a deploy
- `deploy`: deploys app processes and checks the status of a deploy
- triggers: scheduler-app-status, scheduler-deploy, scheduler-is-deployed, scheduler-logs-failed
- `enter`: enters a running container
- triggers: scheduler-enter