Introduction

The Gravity Ops Center is a multi-cluster control plane available in the Enterprise version of Gravity. It reduces the operational overhead of managing multiple Gravity Clusters and Application Bundles by allowing users to:

Version Warning

The Ops Center is only available to users of Gravity Enterprise.

This chapter will guide you through the process of downloading and installing your own instance of the Ops Center.

Installing Ops Center

The Ops Center only works with the Gravity Enterprise Edition license key and the Application Bundle for the Ops Center. You can contact us to get a trial license key and the Ops Center Application Bundle.

As with any Gravity application, you will also need a Linux server to install the Ops Center.

Generating a Token

To establish trust between an Ops Center and multiple K8s clusters, a common shared hard-to-guess secret (token) must be generated first. Therefore, before installing an Ops Center, a shared token needs to be generated and stored in an environment variable named TOKEN:

$ export TOKEN="$(uuidgen)"

Next expand the Ops Center Application Bundle ops-center.tar and launch the installer:

$ tar xvf ./ops-center.tar
$ ./gravity install --advertise-addr=10.1.1.5 \
                    --token=$TOKEN \
                    --flavor=standalone \
                    --cluster=opscenter.example.com \
                    --ops-advertise-addr=opscenter.example.com:443

Post-provisioning

Setting up DNS

After provisioning, DNS records should be created with hostname at either the provisioned ELB load balancer (for AWS) or the IP of the virtual machine (for Vagrant).

Wildcard DNS name

The Ops Center DNS records should be wildcard, both *.opscenter.example.com and opscenter.example.com should point to the IP address of the Ops Center service or load balancer.

Setting up OIDC

After installation OIDC provider should be set up in order to log into the Ops Center.

Setting up TLS Key Pair

After installation, a valid TLS key pair should be set up in order to log into the Ops Center. The Ops Center has to use a valid, not self-signed TLS certificate to function properly.

Configuring endpoints

See Configuring Ops Center Endpoints for information on how to configure Ops Center management endpoints.

Upgrading Ops Center

Log into a root terminal on the Ops Center server.

Update the tele binary:

$ curl -LO https://get.gravitational.io/telekube/bin/{VERSION}/linux/x86_64/tele
$ chmod +x ./tele

Fetch the latest Ops Center application using tele:

$ ./tele pull opscenter:{VERSION} -o installer.tar

This will automatically download into the current directory as installer.tar.

This archive provides all dependencies required for the update, including new gravity binaries, install and upgrade scripts.

Extract the tarball:

$ tar xvf installer.tar

Start the upgrade procedure using upgrade script:

$ ./upgrade

Read more about upgrade procedure here.

Ports

Users who use an external load balancer may need to update their configuration after the upgrade to reference new port assignments.

Gravity Enterprise

Gravity Enterprise enhances Gravity Community, the open-source Kubernetes packaging solution, to meet security and compliance requirements. It is trusted by some of the largest enterprises in software, finance, healthcare, security, telecom, government, and other industries.

Demo Gravity Enterprise

Gravity Community

Gravity Community is an upstream Kubernetes packaging solution that takes the drama out of on-premise deployments. Gravity Community is open-source software that anyone can download and install for free.

Download Gravity Community