
Transfer files to Polyaxon workspaces over SSH
Use Polyaxon's generated SSH host with native SCP and SFTP to move files into and out of a running service workspace.
Practical guides to building, running, and improving ML and AI in production.
Page 3 of 22

Use Polyaxon's generated SSH host with native SCP and SFTP to move files into and out of a running service workspace.

Fine-tune an open Qwen model for bounded support-routing decisions with Polyaxon jobs, track the adapter, and serve the reviewed version through vLLM.

Serve the open Laya typed-decisions checkpoint through Polyaxon, with a CPU classifier endpoint, explicit model scope, and a review path for uncertain classifications.

Deploy an open Qwen model behind a typed classification API on Polyaxon, then check the decision schema and calibration before routing real work.

Adapt Google's Gemma-on-Kubernetes deployment choices to Polyaxon with a DiffusionGemma vLLM service, a batch evaluation job, and an explicit compatibility checklist.

Start a background process, save its execution ID, reconnect to status and logs, and distinguish command limits from the lifetime of a Polyaxon sandbox.

Use an ordered Polyaxon mapping for a curated list of experiments, control concurrency, and distinguish scheduling order from dependencies and completion order.

Compare old and new application outputs under both evaluator versions, inspect changed decisions, and retain the four comparisons in Polyaxon.

Understand exact prefix reuse in vLLM, structure repeated context, account for replica routing, and compare cold and warm workloads with Polyaxon.

Use Kubernetes in-place resource resizing for running workloads, inspect whether changes took effect, and understand the limits for Polyaxon services.

Explore native gang scheduling in Kubernetes 1.37, its potential for Polyaxon training and sandboxes, and how it compares with KAI, Kueue, and Volcano.

Reconcile evaluation results against an expected candidate manifest, preserve failed and missing outcomes, and separate pipeline reporting from release approval.

Scope Polyaxon Python clients and CLI commands to a team, review runs across its projects, and keep explicit project targets and saved defaults clear.

Use Polyaxon matrices to choose parameter scales, separate meaningful combinations, and control the size of a hyperparameter sweep.

Use Polyaxon data references, artifact logging, and registered versions to retain the dataset and split behind each evaluation.

Understand native topology-aware workload scheduling, combine rack locality with gang placement, and assess the tradeoff between waiting and communication.

Build recoverable PyTorch training jobs with complete checkpoints, durable storage, and explicit restoration. Practice recovery locally and with Polyaxon.

Choose between sandbox shells and exec, understand PTY lifetime and output replay, and manage terminal attachment explicitly through the Python SDK.

Confirm hyperparameter finalists across matched training seeds, compare variation and paired differences, and reserve compute for a defensible final choice.

Connect native terminals and IDEs to a Polyaxon service, forward application ports, and use tmux explicitly when you want to resume a shell.

Choose evaluation boundaries, keep related examples together, audit duplicate overlap, and retain reproducible split manifests for ML and LLM experiments.

Use projected ServiceAccount tokens and refresh-aware clients so long-running training, notebooks, and services can keep authenticating without static credentials.

Learn how ordinary ops shells differ from tmux sessions, then detach and reconnect to the same Polyaxon shell from the CLI or UI.

Use Kubernetes ValidatingAdmissionPolicy to check workload ownership and image references, with scoped warning and enforcement stages for ML namespaces.