Skip to content

Commit

Permalink
Merge pull request #149 from Azure/mosabami-patch-4
Browse files Browse the repository at this point in the history
Update README.md
  • Loading branch information
mosabami authored Sep 30, 2024
2 parents 0d84775 + 7bdde27 commit 9187bd1
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions Scenarios/AKS-Secure-Baseline-PrivateCluster/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,9 @@
# AKS Secure Baseline with Private Cluster

A deployment of AKS-hosted workloads typically requires a separation of duties and lifecycle management in different areas, such as prerequisites, the host network, the cluster infrastructure, the shared services and finally the workload itself. This reference implementation is no different. Also, be aware that our primary purpose is to illustrate the topology and decisions involved in the deployment of an AKS cluster. We feel a "step-by-step" flow will help you learn the pieces of the solution and will give you insight into the relationship between them. Ultimately, lifecycle/SDLC management of your cluster and its dependencies will depend on your situation (organizational structures, standards, processes and tools), and will be implemented as appropriate for your needs.
Deploy this scenario using the button below.

[![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#view/Microsoft_Azure_CreateUIDef/CustomDeploymentBlade/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FAKS-Landing-Zone-Accelerator%2Fmain%2FScenarios%2FAKS-Secure-Baseline-PrivateCluster%2FBicep%2FAll-in-One-Bicep%2Fmain.json/uiFormDefinitionUri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FAKS-Landing-Zone-Accelerator%2Fmain%2FScenarios%2FAKS-Secure-Baseline-PrivateCluster%2FBicep%2FAll-in-One-Bicep%2Fmain.portal.ui.json)

There are various ways to secure your AKS cluster. From a network security perspective, these can be classified into securing the control plane and securing the workload. When it comes to securing the control plane, one of the best ways to do that is by using a private cluster, where the control plane or API server has internal IP addresses that are defined in the [RFC1918 - Address Allocation for Private Internet](https://datatracker.ietf.org/doc/html/rfc1918) document. By using a private cluster, you can ensure network traffic between your API server and your node pools remains on the private network only. For more details about private clusters, check out the [documentation](https://learn.microsoft.com/azure/aks/private-clusters).

Expand Down

0 comments on commit 9187bd1

Please sign in to comment.