Gravity features the following CLI commands:
||The build tool.
||Used for remotely connecting to Gravity/Kubernetes Clusters via SSH or Kubernetes API.|
||The Cluster manager which runs on every Cluster node. It abstracts away complexities of Kubernetes management.
The typical Gravity workflow is as follows:
- Start by building a Cluster Image with
- Distribute a Cluster Image to a target environment.
- Create a new Gravity/Kubernetes Cluster using the built-in Cluster installer.
- Manage the Cluster from by using
gravitycommand on Cluster nodes and/or using Kubernetes tools like
tele is the Gravity CLI client and can run on macOS and Linux. With
tele you can:
- Package Kubernetes Clusters into self-installing Cluster Images.
- Publish Cluster Images into the Gravity Hub. (Enterprise version only)
- Download Cluster Images from the Gravity Hub. (Enterprise version only)
You can think of
tele as "docker for Clusters". Just as
build, push and pull containers,
tele does the same with entire Clusters. See
more details in Building Cluster Images section.
tsh allows to remotely connect to any Gravity Cluster using SSH and
Kubernetes API. It runs on MacOS and Linux. You can use
tsh to remotely
login into any node in a Gravity Cluster, even those located behind firewalls.
Gravity uses Teleport for remotely accessing Clusters. See more details in the Teleport User Manual.
gravity only runs on Linux and is only available on the Cluster nodes where
your applications are running.
gravity is responsible for mostly abstracting
away low-level Kubernetes management.
gravity provides commands for easy
version upgrades, adding and removing nodes to a Cluster, and other common
See more details in Cluster Management section