A couple of teams I am currently worked with on dotnet-monitor integration have expressed that there is a non-zero amount of friction when attempting to deploy dotnet-monitor into multiple environments. This friction is in the form of a bunch of duplicated configuration, and while that is not normally a problem, during an upgrade or modification of settings, it results in a ton of error prone copy paste work.

To help reduce this burden our team is attempting to validate if there is interest in using Kubernetes mutating admission webhook to aid in simplifying your Kubernetes deployments. Mutating admission can modify or accept/reject objects that are being created within Kubernetes. One typical use case is to inject a sidecar (like dotnet-monitor) to every pod that is being launched on a cluster. We are soliciting feedback in this discussion here, please vote and comment.


Comment Section

Comments are closed.