In this video, I had the chance to speak with Jason Hansen (Principal Program Manager at Microsoft) about how you can use Azure Arc to standardize DevOps practices across hybrid and multicloud environments.
In relation to Kubernetes, GitOps is the practice of declaring the desired state of Kubernetes cluster configurations (deployments, namespaces, etc.) in a Git repository. This declaration is followed by a polling and pull-based deployment of these cluster configurations using an operator. The Git repository can contain:
Flux, a popular open-source tool in the GitOps space, can be deployed on the Kubernetes cluster to ease the flow of configurations from a Git repository to a Kubernetes cluster. Flux supports the deployment of its operator at both the cluster and namespace scopes. A flux operator deployed with namespace scope can only deploy Kubernetes objects within that specific namespace. The ability to choose between cluster or namespace scope helps you achieve multi-tenant deployment patterns on the same Kubernetes cluster.
With Azure Arc-enabled Kubernetes, you can attach and configure Kubernetes clusters located either inside or outside Azure. When you connect a Kubernetes cluster to Azure Arc, it will:
To connect a Kubernetes cluster to Azure, the cluster administrator needs to deploy agents. These agents:
azure-arcKubernetes namespace as standard Kubernetes deployments.
Azure Arc-enabled Kubernetes supports industry-standard SSL to secure data in transit. Also, data at rest is stored encrypted in an Azure Cosmos DB database to ensure data confidentiality.
Azure Arc-enabled Kubernetes works with any Cloud Native Computing Foundation (CNCF) certified Kubernetes clusters. The Azure Arc team has worked with key industry partners to validate conformance of their Kubernetes distributions with Azure Arc-enabled Kubernetes.
Azure Arc-enabled Kubernetes supports the following scenarios:
Connect Kubernetes running outside of Azure for inventory, grouping, and tagging.
Deploy applications and apply configuration using GitOps-based configuration management.
View and monitor your clusters using Azure Monitor for containers.
Enforce threat protection using Azure Defender for Kubernetes.
Apply policy definitions using Azure Policy for Kubernetes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.