Project STC is the effort driven by the Red Hat EMEA Openshift Specialist Solution Architects team to create reusable assets for the deployment of Red Hat Openshift environments for

• Demos

• Proof of Technologies

• Proof of Concepts

• non Productive Openshift environments

The leading idea behind STC is to start with a Minimal Viable Setup (MVS) consisting of:

• 1 Bastion

• 3 Master

• 3 Nodes

deployed with standard Red Hat Openshift capabilities. The topology is now dynamic in terms of 3 possible STC Flavor to be used for the setup (standard, mini and full)

MVS includes following services:

• Container registry

• Routing layer

• Prometheus

• Ansible and Template service brokers

• Hawkular based metrics

• EFK stack log aggregation for apps

• Openshift Containers Storage (OCS)

• Grafana

STC is an abbreviation from the tabletop game Warhammer 40K and stands for Standard Template Construct

In the context of this repository, it represents a predefined set of Building Blocks, which can be used to achieve predefined setups and use-cases.

Each Building Block represents a certain capability, which can be used either singular, in combination or dependency of another Building Block.

Please check the following list of existing and planned Building Blocks

• BB0 - Validate and prepare infrastructure

• BB1 - Install Minimal Viable Product

• BB4 - Disconnected Installation with Docker Distribution

An archive of BB not yet tested nor updated for newest versions is available inside the archive directory

Check prerequirements for executing STC from here.

Once prerequirements are in place start validating your environment with BB0

Check basic information about contributing building blocks from Check basic information about contributing building blocks from Contributing to STC