emdo-pa / epiphany

Epiphany is a full industrialized automation of Kubernetes and Docker plus additional builtin services/components like: - Kafka or RabbitMQ for high speed messaging/events - Prometheus and Alertmanager for monitoring with Graphana for visualization - Elasticsearch and Kibana for centralized logging - HAProxy for loadbalancing - Postgress for storage - KeyCloak for authentication

Epiphany Platform

Overview

Epiphany at its core is a full automation of Kubernetes and Docker plus additional builtin services/components like:

• Kafka or RabbitMQ for high speed messaging/events
• Prometheus and Alertmanager for monitoring with Graphana for visualization
• Elasticsearch and Kibana for centralized logging (OpenDistro)
• HAProxy for loadbalancing
• Postgres and Elasticsearch for data storage
• KeyCloak for authentication
• Vault (MVP) for protecting secrets and other sensitive data
• Helm as package manager for Kubernetes

The following target platforms are available: AWS, Azure and on-prem installation.

Epiphany can run on as few as one node (laptop, desktop, server) but the real value comes from running 3 or more nodes for scale and HA. Everything is data driven so simply changing the manifest data and running the automation will modify the environment. Kubernetes hosts (masters, nodes) and component VMs can be added depending on data in the initial manifest. More information here.

Please note that currently Epiphany supports only creating new masters and nodes and adding them to the Kubernetes cluster. It doesn't support downscale. To remove them from Kubernetes cluster you have to do it manually.

We currently use Terraform and Ansible for our automation orchestration. All automation is idempotent so you can run it as many times as you wish and it will maintain the same state unless you change the data. If someone makes a "snow flake" change to the environment (you should never do this) then simply running the automation again will put the environment back to the desired state.

Note about documentation

• The documentation is a moving target. Always check the latest documentation on the develop branch. There is a big chance that whatever you are looking for is already added/updated or improved there.

Quickstart

Epicli

Use the following command to see a full run-down of all commands and flags:

epicli --help

Generate a new minimum cluster definition:

epicli init -p aws -n demo

This minimum file definition is fine to start with, if you need more control over the infrastructure created you can also create a full definition:

epicli init -p aws -n demo --full

You will need to modify a few values (like your AWS secrets, directory path for SSH keys). Once you are done with demo.yml you can start cluster deployment by executing:

epicli apply -f demo.yml

You will be asked for a password that will be used for encryption of some of build artifacts. More information here

Since version 0.7 epicli has an option to backup/recovery some of its components. More information here

epicli backup -f <file.yml> -b <build_folder>
epicli recovery -f <file.yml> -b <build_folder>

To delete all deployed components following command should be used

epicli delete -b <build_folder>

Find more information using table of contents below - especially the How-to guides.

Documentation

• Platform
  • Resources
  • How-to guides
  • Components
  • Security
  • Troubleshooting
  • Changelog
  • Release policy and lifecycle
• Architecture
  • Logical View
  • Process View
  • Physical View
• Contributing
  • Governance model
  • Development environment
  • GIT Workflow