78fc17f7ea
* update aks module to output identities * formatting tests and updating kubernetes version * fix outputs in aks module |
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| cluster | ||
| docs | ||
| gitops | ||
| pipelines | ||
| test | ||
| tools | ||
| .gitignore | ||
| LICENSE | ||
| README.md | ||
| azure-pipelines.yml | ||
| security.md | ||
README.md
Bedrock
Bedrock provides patterns, implementation, and automation for operating production Kubernetes clusters based on a GitOps workflow, building on the best practices we have discovered in working with dozens of deployments with customers in operationalizing Kubernetes clusters.
Bedrock helps you:
- Define and maintain infrastructure deployments across multiple clusters.
- Deploy and automate a secure end to end GitOps workflow.
- Deploy and manage service workloads from source code to their deployment in-cluster.
- Observe ongoing deployments across multiple services and their revisions and multiple clusters deploying those services.
Quick Start
Getting Started
Infrastructure Management
- Walkthrough: Single Cluster Infrastructure Deployment
- Deep Dive: Multicluster and "Day 2" Infrastructure Scenarios
- CLI Reference
- Managed Identity Reference
GitOps Pipeline
Service Management
- Walkthrough: Service Management
- Deep Dive: Helm Charts
- Configuring A Service through Fabrikate configurations
- CLI Reference
- Managed Identity Reference
Rings Management
Deployment Observability
Community
Please join us on Slack for discussion and/or questions.
Contributing
We do not claim to have all the answers and would greatly appreciate your ideas, issues, and pull requests.
If you'd like to contribute, start by searching through the issues and pull requests to see whether someone else has raised a similar idea or question.
If you don't see your idea listed, and you think it fits into the goals of this project, do one of the following:
- If your contribution is minor, such as a typo or grammar fix, open a pull request.
- If your contribution is major, such as a new guide or feature we suggest starting by opening an issue first. That way, there is more visiblity to other contributors.
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 opencode@microsoft.com with any additional questions or comments.
For project level questions, please contact Tim Park.