You have the use case of accessing an Azure Key Vault through a private endpoint from your own machine. One solution is to combine Azure VPN Gateway with Azure DNS Private Resolver.
The VPN Gateway provides the network path to Azure.
DNS Private Resolver makes sure the Key Vault name resolves to its private IP.
Setting up this architecture took me some time. Here are the things worth knowing before creating the resources, using a point-to-site VPN as the main example.
When you create an RBAC role assignment on Azure from your Infrastructure-as-Code scripts, you might run into the “The role assignment already exists. The ID of the existing role assignment is xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.” error.
The question now is which identity (managed identity, user, etc.) is behind that ID. Let us first see what this ID from the error message is all about.
Flux is a set of Kubernetes controllers that keeps your cluster in sync, based on configuration changes you do in a Git repository instead of running kubectl by hand.
A simple Flux setup can be explained with three resources, each one answering a different question:
A forked repository on GitHub is a copy of an upstream repository at a specific point in time. Git does not keep your forked repository in sync automatically, since the upstream repository continues to receive commits while your fork remains unchanged.
In this article, I show you how to sync your forked repository with the upstream repository in the following steps.
Azure has three services that all move messages from one place to another: Event Grid, Service Bus and Event Hubs. In this article we are going to see which one fits better your use case.
In this article, I will start with a simple three-question rule, follow it with a side-by-side comparison, and then explain the differences that actually matter when choosing between them.