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

docs: expand det abbreviation in docs #9652

Merged
merged 1 commit into from
Jul 16, 2024
Merged

docs: expand det abbreviation in docs #9652

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
4 changes: 2 additions & 2 deletions docs/setup-cluster/k8s/internal-task-gateway.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,8 +126,8 @@ that your Gateway API is going to use.

If you're running Determined outside of the Kubernetes (K8s) cluster, for example on your local
machine for testing and development, it's possible to test this feature using just a single
Kubernetes (K8s) cluster. All that is needed is for Det master to be sitting external to the target
cluster.
Kubernetes (K8s) cluster. All that is needed is for Determined master to be sitting external to the
target cluster.

For allowing Determined tasks to connect to master that's running locally on your machine, you can
use services like ngrok or a reverse SSH tunnel if you have access to a public IP like so: `ssh -R
Expand Down
Loading