These docs are deprecated while they are being migrated to Red Hat. For the most up to date docs, please see the corresponding GitHub repository.

We’re integrating Tectonic with Red Hat OpenShift

We are bringing the best of Tectonic to Red Hat OpenShift to build the most secure, hybrid Kubernetes application platform.

Getting Started

Installing Tectonic

AWS

Bare Metal

Azure

Clusters

Using cluster services

Tectonic multi-cluster (alpha)

Monitoring clusters

Metering and Chargeback (alpha)

Managing clusters

TLS Certificates

Deleting clusters

Open Cloud Services

Users

Authenticating users

Managing users

Troubleshooting

Resources

The vault-operator creates the following Kubernetes resources to set up a Vault cluster:

A Custom Resource for the etcd cluster storage backend
A Deployment for Vault instances
A Service to serve Vault client requests
TLS Secrets for the etcd-cluster and Vault
A Configmap to store the Vault configuration

Labels

All of the above resources created for a Vault cluster have the following labels:

app=vault
vault_cluster=<cluster-name>

where <cluster-name> is the name of the Vault cluster to which that resource belongs.

Ownership

For all the above resources their metadata.ownerReferences field points to the Vault Custom Resource to which they belong.