Enterprise Kubernetes, delivered

Tectonic ships with CoreOS's signature automated operations, runs multi-cloud, and is the fastest, most secure path to Kubernetes.

Getting Started with Tectonic

At its core, Tectonic is built on top of 100% open-source Kubernetes. This means no lock-in for Tectonic customers and everyone benefits from timely releases of new features, bug fixes and security updates.

Install a New Cluster

Step 1: Deploy a supported Kubernetes cluster

Tectonic offers support, services and additional features that rely on a properly functioning Kubernetes cluster. The Kubernetes project offers conformance tests, and Tectonic is supported on any cluster that passes these tests and runs on CoreOS Linux.

To get started as quickly as possible, use an installer below. If you'd like to tinker and build one from scratch, follow the manual installation instructions.

Using an Installer

Manual Install

Anywhere you can run CoreOS Linux, you can run Kubernetes. The following instructions provide an overview of how a supported Kubernetes deployment should be installed. It is intended to be a generic guide that allows you to integrate with your existing configuration management and deployment tools.

Step 2: Configure Tectonic Services

Start by creating the tectonic-system Kubernetes namespace. This namespace will contain all Tectonic-related objects. Download the namespace manifest contained alongside this guide, then use kubectl to establish the namespace via the Kubernetes API:

$ kubectl create -f tectonic-namespace.yml
namespaces/tectonic-system

Now follow each of the guides below to prepare your Tectonic cluster with cluster-wide configuration and PKI artifacts:

Step 3: Deploy Tectonic Services

Tectonic Services are the Apps and Services that are installed onto your Kubernetes cluster. Running Tectonic Services will require a fully functioning Kubernetes API endpoint, TLS encryption, and Identity services, so be sure to complete Steps 1 and 2 before continuing.

Step 4: Finalize Deployment

Once services are deployed, Tectonic creates an initial password for the administrator user and stores it in a secret. Admins should retrieve this password in order to log in with it and change it to meet local policy. Retrieve the secret from the cluster and decode it into human-readable format:

$ kubectl --namespace=tectonic-system get secret tectonic-identity-admin-password -o template --template="{{ .data.password }}" | base64 --decode

Use the output from this command as the password to log in to the Tectonic Console.

Step 5: Deploy Additional Services to Cluster

Next up: Start deploying your applications onto your cluster.

For those new to Kubernetes, the official Kubernetes User Guide provides tutorials and guides that demonstrate how to get started with Kubernetes and deploy your first applications.

Follow the official Quay Enterprise installation guide to deploy a full-featured docker image registry onto your Kubernetes cluster.

Upgrade an Existing Cluster

Simply follow this documentation to upgrade your existing Tectonic cluster. Upgrades of the underlying Kubernetes cluster are not covered.