Deploy Applications to Hybrid Kubernetes Clusters with Azure Arc

1. Deploy the GitOps (Flux) Extension to all Kubernetes Clusters using Azure Policy, the built-in Policy definition named Configure installation of Flux extension on Kubernetes cluster can be used.
   • Scope the policy assigment to the Resource Group.
   • Use the existing managed identity named id-policyremediation for policy remediation.

Note: You can ignore the warning about permission assignments when assigning the managed identity for policy remediation. The existing managed identity has the required permissions.

1. Remediate any non-compliant Policy assignments using remediation tasks.

Note: Change the Scope of the remediation tasks blade to the Resource Group to remove the Access is denied to the requested resource... when the remediation tasks list is scoped to the Subscription. You have access to the resource group in this lab, not the entire subscription.

1. Deploy a Flux configuration to all Kubernetes clusters in the resource group using Policy. The built-in policy named Configure Kubernetes clusters with Flux v2 configuration using public Git repository can be used to deploy the application, with the following parameters:
   • Configuration Instance Name: guestbook
   • Configuration Namespace: default
   • Configuration Scope: cluster
   • Repository Url: https://github.com/pluralsight-cloud/azure-arc-hybrid-management-implementing
   • Repository Reference Branch: main
   • Kustomization Name: kustomize
   • Kustomization Path: ./kustomize-guestbook
   • Kustomization Prune: true

Note: You can ignore the warning about permission assignments when assigning the managed identity for policy remediation. The existing managed identity has the required permissions.

1. Review GitOps configuration of hybrid Kubernetes clusters using the Azure portal.