This repo is a WORK IN PROGRESS.
Hello, and welcome to the workshop. This is a 2-day hands-on workshop focused on setting up AKS along with additional technologies to make it adhere to the governance and security needs of highly regulated customers.
The workshop runs over 2 days and is mean to take an outside in approach. Meaning, we will start from the outside and make our way inwards. It starts with focusing on Governance and Security decisions that need to get made before a single Azure resource is even provisioned. We will then focus on decisions that need to get made prior to provisioning the cluster. Next we will actually provision the cluster along with focusing on how to deploy common components post-provisioning. Now that the clsuter is configured, the next steps is to actually deploy some workloads. Once the workloads are deployed we will focus in on some Day 2 operations when it comes to managing, maintaining and provising observability into the cluster.
The end goal is to take you from having a kubernetes setup that is unsecure by default, to an Enterprise ready configuration that is secure by default. To help understand what that means please see the following illustrations showing a before and after setup.
- Customer Scenario
- Governance and Security Setup
- Cluster Pre-Provisioning
- Cluster Provisioning
- Post-Provisioning
- Cost Governance
- Deploy Sample App
- Service Mesh - Do I need it?
- Validate Scenarios
- Thought Leadership & Next Steps
The following are the requirements to start.
-
Azure Account Azure Portal
-
Azure CLI Install CLI
-
Kubectl CLI Install kubectl with Azure CLI
-
Git Git SCM
-
Terraform Terraform Download
-
Docker Community Edition (CE)Install CE
-
Code Editor Install VS Code
It is important to Fork this repo, not just clone it. You will be creating Personal Access Tokens, which in turn will be creating SSH keys, and they will be used to make changes to a GitHub repo.
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.opensource.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., status check, 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.
Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the Creative Commons Attribution 4.0 International Public License, see the LICENSE file, and grant you a license to any code in the repository under the MIT License, see the LICENSE-CODE file.
Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.
Privacy information can be found at https://privacy.microsoft.com/en-us/
Microsoft and any contributors reserve all other rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.