The intent of this article is to explain how we deployed widely Azure Private Link on PaaS Services and how we tackled the DNS part of this technology, both for on-premise and Azure machines/workstations. Azure Private Link Azure Private Link [https://docs.microsoft.com/en-US/azure/private-link/private-link-overview] is
This article will retrace Michelin journey around containers and container-orchestration (Kubernetes) systems over the last 3 years. We believe that this feedback is interesting because we made strong choices from both a technical and an operational point of views. First things first, why have Michelin invested efforts on such technologies?
Over the last decade, Michelin went from a big mainframe monolith to a choreography of micro services streaming business events to support its core business processes: the distribution of tires from our plants to our warehouses. At stake: our ability to deliver our tires to our customers on time and
Context Azure implementation at Michelin follows Microsoft recommendations: we have several virtual Data Centers (vDC) in different regions connected to our "on-premises" network through Express Route. In terms of network topology, we leverage the traditional hub and spoke model: The vast majority of the workload are Virtual Machines (VMs) with
Within Michelin, we have connections from several geographic points to Azure regions, through Express Route circuits. An important requirement from our Network and Security teams is the capability to inspect and analyze the network traffic between all our assets. We already had visibility of network traffic between "on-premise" and Azure