David Frappart
Cloud architect & IaC Geek
Soissons, France
Actions
IT guy since 2004
Cloud architect, (mainly on Azure) since 2015
Still exploring the Cloud platform capabilities (which get new stuff all the time)
Breath IaC and Automation (but more Hashicorp stuff than other ^^)
Still struggles in the K8S landscape
MVP Azure since 2019
MCT since 2020
https://www.linkedin.com/in/david-frappart-66625627/
https://blog.teknews.cloud
Links
Badges
Area of Expertise
Topics
Back to Basics - Managing Private DNS in Azure
Even in modern Infrastructure, people still need DNS, because it's way easier to find a human readable name than an IP.
The thing is, We tend to take for granted that everything is taken care of.
It's not!
In this session, we'll start from the most basic need: How do we manage private DNS in an Azure environment.
After a rapid view of the available options, we'll take a look at a somehow real life scenario:
Managing DNS resolution in Azure hybrid environment.
The objective of this session : to be clear on where DNS is configurable, when to use private dns zone or Private DNS resolver, or even a IaaS option
Basic knowledge of DNS in general, Azure network
Hub & spokes variations with Azure Virtual WAN
The most seen Azure network topology relies on Hub & Spokes, peering all vnets to the same central one, called the hub.
While this scenario works well, as witnessed by its wide adoption, there are now other options, on being to use Azure Virtual WAN.
In this session, we'll go back to what VWAN is and what it brings to the table.
Then we'll explore different topology variations using it instead of the "classic" hub & spokes.
At the end of the session, hopefully ^^, you'll know more about how VWAN works and how to change from the one and only hub & spoke as you know it
Get to know VWAN and some hub & spokes variations
Moving from the Ingress controller to Gateway API
Ingress has been used to expose application for some times now.
However, we have seen a shift preparing since kubernetes 1.28 with the release of Gateway API 1.0.
In this session, we'll take a look at the Gateway API, it's components and how to use it.
Theorical concepts will be demonstrated along the way on kubernetes environments, IaaS or cloud managed.
At this end of this session, you'll know the main concepts behind Gateway API and how to use it to expose applications
Prepare your move to Kubernetes Gateway API before Ingress becomes deprecated. Learn how Gateway API works in regards to apps exposition.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top