docs -> learn migration

README.md

@@ -34,13 +34,13 @@ Finally, this implementation uses a small, custom application as an example work
 #### Azure platform
 
 * AKS v1.23
-  * System and User [node pool separation](https://docs.microsoft.com/azure/aks/use-system-pools)
-  * [AKS-managed Azure AD](https://docs.microsoft.com/azure/aks/managed-aad)
+  * System and User [node pool separation](https://learn.microsoft.com/azure/aks/use-system-pools)
+  * [AKS-managed Azure AD](https://learn.microsoft.com/azure/aks/managed-aad)
   * Managed Identities for kubelet and control plane
   * Azure CNI
-  * [Azure Monitor for containers](https://docs.microsoft.com/azure/azure-monitor/insights/container-insights-overview)
+  * [Azure Monitor for containers](https://learn.microsoft.com/azure/azure-monitor/insights/container-insights-overview)
   * Private Cluster (Kubernetes API Server)
-  * [Azure AD Pod Identity](https://docs.microsoft.com/azure/aks/use-azure-ad-pod-identity)
+  * [Azure AD Pod Identity](https://learn.microsoft.com/azure/aks/use-azure-ad-pod-identity)
 * Azure Virtual Networks (hub-spoke)
   * Azure Firewall managed egress
   * Hub-proxied DNS
@@ -53,10 +53,10 @@ Finally, this implementation uses a small, custom application as an example work
 
 #### In-cluster Open-Source Software components
 
-* [Secrets Store CSI Driver for Kubernetes](https://docs.microsoft.com/azure/aks/csi-secrets-store-driver)
+* [Secrets Store CSI Driver for Kubernetes](https://learn.microsoft.com/azure/aks/csi-secrets-store-driver)
 * [Falco](https://falco.org)
 * [Flux 2 GitOps Operator](https://fluxcd.io)
-* [Kured](https://docs.microsoft.com/azure/aks/node-updates-kured)
+* [Kured](https://learn.microsoft.com/azure/aks/node-updates-kured)
 * [NGINX Ingress Controller](https://kubernetes.github.io/ingress-nginx/)
 * [Open Service Mesh](https://openservicemesh.io/)
 
@@ -137,7 +137,7 @@ Most of the Azure resources deployed in the prior steps will have ongoing billin
 
 All workloads that find themselves in compliance scope usually require a documented separation of duties/concern implementation plan. Kubernetes poses an interesting challenge in that it involves a significant number of roles typically found across an IT organization. Networking, identity, SecOps, governance, workload teams, cluster operations, deployment pipelines, any many more. If you're looking for a starting point on how you might consider breaking up the roles that are adjacent to the AKS cluster, consider **reviewing our [Azure AD role guide](./docs/rbac-suggestions.md)** shipped as part of this reference implementation.
 
-> :notebook: See [Azure Architecture Center guidance for PCI-DSS 3.2.1 Requirement 7, 8, and 9 in AKS](https://docs.microsoft.com/azure/architecture/reference-architectures/containers/aks-pci/aks-pci-identity).
+> :notebook: See [Azure Architecture Center guidance for PCI-DSS 3.2.1 Requirement 7, 8, and 9 in AKS](https://learn.microsoft.com/azure/architecture/reference-architectures/containers/aks-pci/aks-pci-identity).
 
 ## Is that all, what about … !?
 
@@ -160,9 +160,9 @@ Kubernetes is a very flexible platform, giving infrastructure and application op
 ## Related documentation
 
 * [Azure Kubernetes Service Baseline Architecture](https://aka.ms/architecture/aks-baseline)
-* [Azure Kubernetes Service Documentation](https://docs.microsoft.com/azure/aks/)
-* [Microsoft Azure Well-Architected Framework](https://docs.microsoft.com/azure/architecture/framework/)
-* [Microservices architecture on AKS](https://docs.microsoft.com/azure/architecture/reference-architectures/containers/aks-microservices/aks-microservices)
+* [Azure Kubernetes Service Documentation](https://learn.microsoft.com/azure/aks/)
+* [Microsoft Azure Well-Architected Framework](https://learn.microsoft.com/azure/architecture/framework/)
+* [Microservices architecture on AKS](https://learn.microsoft.com/azure/architecture/reference-architectures/containers/aks-microservices/aks-microservices)
 
 ## Contributions
 

cluster-manifests/README.md

@@ -19,4 +19,4 @@ This is the root of the GitOps configuration directory. These Kubernetes object
 
 ### Kured
 
-Kured is included as a solution to handle occasional required reboots from daily OS patching. This open-source software component is only needed if you require a managed rebooting solution between weekly [node image upgrades](https://docs.microsoft.com/azure/aks/node-image-upgrade). Building a process around deploying node image upgrades [every week](https://github.com/Azure/AKS/releases) satisfies most organizational weekly patching cadence requirements. Combined with most security patches on Linux not requiring reboots often, this leaves your cluster in a well supported state. If weekly node image upgrades satisfies your business requirements, then remove Kured from this solution by removing [`- kured.yaml` from `kustomization.yaml`](./cluster-baseline-settings/kustomization.yaml). If however weekly patching using node image upgrades is not sufficient and you need to respond to daily security updates that mandate a reboot ASAP, then using a solution like Kured will help you achieve that objective. **Kured is not supported by Microsoft Support.**
+Kured is included as a solution to handle occasional required reboots from daily OS patching. This open-source software component is only needed if you require a managed rebooting solution between weekly [node image upgrades](https://learn.microsoft.com/azure/aks/node-image-upgrade). Building a process around deploying node image upgrades [every week](https://github.com/Azure/AKS/releases) satisfies most organizational weekly patching cadence requirements. Combined with most security patches on Linux not requiring reboots often, this leaves your cluster in a well supported state. If weekly node image upgrades satisfies your business requirements, then remove Kured from this solution by removing [`- kured.yaml` from `kustomization.yaml`](./cluster-baseline-settings/kustomization.yaml). If however weekly patching using node image upgrades is not sufficient and you need to respond to daily security updates that mandate a reboot ASAP, then using a solution like Kured will help you achieve that objective. **Kured is not supported by Microsoft Support.**