Polyaxon v1.16: CLI Operation shell & inspection

Improved inspection and monitoring capabilities and Container Shell debugging capabilities in the CLI.

CLI container shell

Previously we pushed a shell debugging feature to Polyaxon UI. The shell tab allows to access an operation’s container without the need for a kubeconfig on the user’s machine. Additionally these new capabilities work natively with Polyaxon’s AuthN/AuthZ as well as respects any additional RBAC configured on the cluster.



In this release we added the same feature to Polyaxon CLI with polyaxon ops shell.


CLI operation’s inspection

Previously we released a feature that allows users to completely monitor, watch, inspect, and debug their workload without having any access to the Kubernetes cluster.

Users can inspect their runs directly from the statuses page without the need to have access to the Kubernetes cluster:



In this release we added the same feature to Polyaxon CLI with polyaxon ops inspect.

# Starting a shell for an already running operations
$ polyaxon ops inspect [-p] [-uid] > op-inspection.json

Learn More about Polyaxon

This blog post just goes over a couple of features that we shipped in v1.16. To learn more about all the features, fixes, and enhancements, please visit the release notes and the short term roadmap.

Polyaxon continues to grow quickly and keeps improving and providing the simplest machine learning abstraction. We hope that these updates will improve your workflows and increase your productivity, and again, thank you for your continued feedback and support.

Subscribe to Polyaxon Blog

Get the latest posts delivered right to your inbox