2. CLUSTER TYPE
Tectonic cluster can be setup
on AWS or Bare metal at the
moment. Bare metal process
needs some additional work in
the datacenter/bare metal part
You can save progress anytime
or load from a saved file
earlier.
3. AWS CREDS
Enter the AWS keys or use a
temporary session token and
provide the zone
4. DNS & LICENSING
The “cluster name” here
becomes the endpoint for your
cluster and an equivalent “A”
entry is made in ROute53 in
the hosted zone you choose.
The license key and pull secret
are available in your tectonic
account.
5. You will be asked a few more
details around keys, certs etc.
before you can submit the
definition to built. You can also
save the progress as a
template for future
6. It takes a while before the
cluster is ready. You can
download the assets and look
at CloudFormation template
used for installing the cluster.
7. Finally, you need to copy a few
files from downloaded assets
to the tectonic cluster & run a
script.
These files contain a set of
objects that tectonic deploys
for example prometheus, your
user credentials etc. You can
choose to skip some if you
want to customize it.
8. CLUSTER UI
The Cluster is up and running.
You can see pretty much all
Kubernetes objects on left side
menu and some additional
menu items around
adminstration below
9. ADDITIONAL SERVICES
Tectonic creates three namespaces 1)
Kube system for components which
kubernetes installs for ex. Heapster &
Kube-dns here
2) Tectonic - for things like
prometheus, tectonic components
etc.
3) Default - for apps that you want to
deploy
You can customize these components
as part of assets that you download
10. ALL NODES
You can see details of nodes
that are part of your cluster
11. MORE DETAILS - NODE
Additional details about an
individual node such as
resource consumption, pods
running on that container etc.
12. OBJECT CREATION
You can us the GUI to create
Kubernetes objects or if you
prefer you can use the Kubectl
CLI.
13. RBAC
Tectonic builds in a fine
grained and action based role
system which you can assign to
certain type of resources only.
This allows you to create roles
and limit the level of access
assigned to users