An Application is a domain space for an organized group of Components that should be designed to serve a purpose for your organization.
A Component runs a singular function, such as a database or search appliance. An Application can be made up of many Components.
A Container holds a Docker image with RAM and CPU allocations, ports, and environment variables. A Component requires at least one Container to run.
A running Container. A Component may be configured to run multiple Container Instances for application resiliency.
Core actions control the install and management of the Supergiant core application on your Kubernetes cluster.
The Supergiant GUI, accessible through a web browser.
Docker containers allow software to be containerized into complete, runnable filesystems, containing code, system tools, and linked libraries.
Container environment actions allows the user to manage container environment variables for a component container.
From kubernetes.io: "Kubernetes is an open-source system for automating deployment, operations, and scaling of containerized applications. It groups containers that make up an application into logical units for easy management and discovery."
A mount is the point that a volume is attached to a Container.
The Packing Algorithm provisions the right resources when needed, lowering cost and increasing hardware utilization, and ensuring you never have to worry about managing servers directly.
A Container may be accessed via network ports, configured when you create a Container with the Dashboard UI or when you create a release with the CLI.
The spacetime provider control tool allows the user to define cloud credentials to use while performing supergiant actions. Spacetime maintains a separate provider database in your spacetime config, because often a user may have or want Kubernetes clusters to reside in multiple Regions, Zones, Accounts, or Clouds using unique credentials.
Spacetime actions control Kubernetes clusters on which your supergiant core will run. The spacetime controller on it's own is a useful way to manage multiple Kubernetes clusters across multiple environments.
[Supergiant][supergiant.io] is an open-source container orchestration system, based on Kubernetes. It is built and maintained by the Qbox.io team to make it easy to deploy stateful, distributed apps at scale.
- 5. FAQ
- 0. README
- 4.2. ECLA
- 4.1. ICLA
- 4. Agreements
- 3. Supergiant CLI Reference
- 3.3. Applications
- 3.3.1. Components
- 3.3.2. Containers
- 184.108.40.206. Container Commands
- 220.127.116.11. Environment Variables
- 18.104.22.168. Mounts
- 22.214.171.124. Ports
- 3.3.3. Volumes
- 3.2. Core
- 3.1. Spacetime
- 3.1.2. Import
- 3.1.1. Providers
- 1. Community
- 1.2. Code of Conduct
- 1.1. Contribution Guidelines
- 1.3. GitHub Issues Guidelines
- 2.1. Installation
- 6. Troubleshooting
The core of a Supergiant instance. The API exposes control of the general provisioning of services and allocation of resources.
A volume is persistent storage, like a solid state drive, IOPS drive, or traditional disk drive. It is where data is stored.