Supergiant is an open-source container orchestration system that lets developers easily deploy and manage apps as Docker containers using Kubernetes.
Supergiant aims to automate installation and simplify management of Kubernetes across different cloud accounts by providing an easy-to-use UI that exposes Kubernetes API. The system implements simple concepts that abstract Kubernetes API for pod and services deployment, storage, load-balancing, hardware auto-scaling, and more. Supergiant uses an efficient packing algorithm to enable seamless auto-scaling of Kubernetes clusters to minimize costs and improve resilience of applications. For a more detailed overview of Supergiant top-level concepts, see the docs folder.
- Fully compatible with native Kubernetes (works with existing setups)
- UI and CLI, both built on top of an API (with importable Go client lib)
- Launch and manage multiple Kubes across multiple cloud providers from the UI
- Works with multiple cloud providers (AWS, DigitalOcean, OpenStack, Packet.net, and actively adding more, in addition to on-premise hardware support)
- Deploy / Update / Restart containers with a few clicks
- Get instant access to apps from Helm Repositories
- Filterable container metrics views (RAM / CPU timeseries graphs)
- Get a comprehensive view of cluster resources with built-in monitoring and logging
- Automatic server management (manual addition of new nodes, background server autoscaling, up/down depending on container resource needs)
- Role-based Users, Session-based login, self-signed SSL, and API tokens for security (OAuth and LDAP support soon coming)
- Download the Supergiant server for your system (Windows, Mac, and Linux) and processor architecture from our releases page. For example, for Linux:
curl https://github.com/supergiant/supergiant/releases/download/v0.15.6/supergiant-server-linux-amd64 -L -o /usr/bin/supergiant
- Make sure to make the downloaded binary executable:
sudo chmod +x /usr/bin/supergiant
- Download the example config file and customize it:
curl https://raw.githubusercontent.com/supergiant/supergiant/master/config/config.json.example --create-dirs -o /etc/supergiant/config.json
In the configuration file, specify your paths to log and database locations and create corresponding directories for them.
{
...
"sqlite_file": "/var/lib/supergiant/development.db",
...
"log_file": "/var/log/supergiant/development.log",
...
}
- Run the binary with a config file and save the user/password for the admin user generated the first time Supergiant runs.
<supergiant-server-binary> --config-file /etc/supergiant/config.json
- Access Supergiant on default 8080 port on localhost.
If you want to easily install Supergiant on Amazon Web Services EC2 with Supergiant Amazon Machine Image (AMI), follow the Supergiant AWS Install Tutorial.
Supergiant allows deploying Kubernetes clusters (Kubes) via the easy-to-use interface with the minimal configuration required. The system manages Kubernetes installation and configuration under the hood enabling various master and nodes services and tools.
Supergiant provides access to Kubernetes curated helm charts with a broad choice of configured containers installable in one click.
Supergiant UI gives a comprehensive view of computer resources used by the cluster, running applications, services, and attached storages to get insights and simplify cluster administration.
Currently, the core team is working on the following:
- Add LDAP and OAuth user authentication
- Add support for new cloud providers
- Add support for local installations
We are grateful for any contribution to the Supergiant project be it in a form of a new GitHub issue, a GitHub feature Pull Request, social media engagement etc. Contributing to Supergiant projects requires familiarization with Community and our Contribution Guidelines. Please see these links to get started.
docker-compose build server
docker-compose run --rm --service-ports server
If you would like to contribute changes to Supergiant, first see the pages in the section above, Community and Contributing.
Note: Supergiant cloud installers have dependencies pre-installed and configured and will generate a self-signed cert based on the server hostname. These instructions are for setting up a local or custom environment.
Supergiant dependencies:
go get github.com/supergiant/supergiant
You can copy the example configuration:
cp config/config.json.example config/config.json
go run cmd/server/server.go --config-file config/config.json
open localhost:8080
This will allow for calling the CLI with the supergiant
command:
go build -o $GOPATH/bin/supergiant cmd/cli/cli.go
govendor test +local
If you make a change and import a new package, run this to vendor the imports.
govendor add +external
Supergiant uses go-bindata to compile assets directly into the code. You will need to run this command if you're making changes to the UI or if you're working with Provider code:
go-bindata -pkg bindata -o bindata/bindata.go config/providers/... ui/assets/... ui/views/...
Our AMI distribution automatically sets up self-signed SSL for Supergiant, but the default config/config.json.example does not enable SSL.
You can see our AMI boot file for an example of how that is done if you would like to use SSL locally or on your own production setup.
This software is licensed under the Apache License, version 2 ("ALv2"), quoted below.
Copyright 2016 Qbox, Inc., a Delaware corporation. All rights reserved.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.