day-jeff / bedrock

Automation for production quality Kubernetes clusters with a GitOps workflow

bedrock

Bedrock is a set of automation, tooling, and infrastructue stacks for deploying production-level Kubernetes clusters with a secure and auditable GitOps workflow.

This project is our humble attempt to combine the collective wisdom of the cloud native community for building best practice cloud native Kubernetes clusters, based on real world experiences deploying and operating applications in Kubernetes clusters.

What's in the box?

Bedrock, by default, includes the workflow, platforms, and tools that we believe are the best in class for operating a Kubernetes cluster. It includes Terraform scripts for creating the core infrastructure for your cluster and also, by default, includes a cloud native set of observability infrastructure via a set of "batteries removable" Fabrikate stacks.

Cluster Creation

• Cluster Deployment: Automated cluster creation
• Flux: Secure GitOps Kubernetes operator

Cluster Maintainance

• Kured: Automatic node reboot when OS is patched. (via fabrikate-kured)

Metrics Monitoring (via fabrikate-prometheus-grafana)

• Prometheus Metrics aggregation
• Grafana Visualization with Kubernetes monitoring dashboards preconfigured

Log Management (via fabrikate-elasticsearch-fluentd-kibana)

• Fluentd: Collection and forwarding
• Elasticsearch: Aggregation and query execution
• Kibana: Full text query UI and visualization

Service Mesh (via fabrikate-istio)

• Istio: Connect, secure, control, and observe services.

Distributed Tracing (via fabrikate-jaeger)

• Jaeger: Distributed transaction, latency, and dependency tracing

Getting Started

1. Instructions for creating and deploying a cluster environment.

Contributing

We do not claim to have all the answers and would greatly appreciate your ideas and pull requests.

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

For project related questions or comments, please contact Tim Park.