End-users of Tectonic are expected to deploy applications directly in Kubernetes. For first-time users of Kubernetes, familiarize yourself with the building blocks of Kubernetes by reading through the official Kubernetes User Guide.
Your application's architecture will drive how you assemble these components together.
Tectonic supports three different methods of interacting with Kubernetes:
See below for more information on how to use each of these.
The primary method of access control for Kubernetes is client certificates issued to you by your administrator. These certificates can be used to access the Kubernetes API and configured for use with
The Tectonic Console gives end-users an easy-to-navigate view of the live event stream and workload of the Tectonic cluster. The Console may not be exposed to the internet. Your administrator may have placed it behind a VPN or other restricted location.
End-users more familiar with command-line tools will find
kubectl a productive method of deploying their Kubernetes-aware applications.
In order to use kubectl, an end-user must be authenticated and populate a valid kubeconfig file. The easiest way to this is with the simple one-time setup process outlined below.
Once you've downloaded your kubeconfig you are ready to start using the kubectl CLI. Keep your kubeconfig file in a safe location because it contains your access credentials.
Onscreen instructions will also provide you links to download kubectl for your operating system. Download the binary appropiate for your platform.
In order to configure kubectl CLI to use kubeconfig permenantly, copy kubeconfig file to $HOME/.kube/config.
$ cp kubeconfig $HOME/.kube/config
Alternatively, you can follow one of the steps below to use kubeconfig at runtime:
kubectl --kubeconfig=/path/to/kubeconfig get pods
Once kubectl is properly configured, it can be used to explore Kubernetes entities:
$ kubectl get nodes NAME LABELS STATUS 10.0.0.197 kubernetes.io/hostname=10.0.0.197 Ready 10.0.0.198 kubernetes.io/hostname=10.0.0.198 Ready 10.0.0.199 kubernetes.io/hostname=10.0.0.199 Ready
See the upstream kubectl CLI documentation for more details on kubectl syntax.
An end-user may integrate external tools and applications with Kubernetes directly via a swagger-based API. After being issued certificates to the Kubernetes API by an administrator, an end-user should be able to make direct API requests.
See the upstream Kubernetes documentation for more information about the API semantics.