.NET & C#
18 articles in The Mesh Series by Arshad Badar Khan cover .NET & C#.
Filter with other topics-
Kubernetes in Five Boxes
You've decided to move to Kubernetes. Good. Then you open the documentation and meet forty resource types, three networking layers, and a YAML file that wants to know your pod's DNS policy. This is the moment most people quietly…
-
Your First .NET 8 Service on Kubernetes
You have the mental model now. Article 2 gave you a .NET 8 minimal API and the Deployment plus Service YAML that fronts it. Both sit on your disk, doing nothing. A YAML file is not a running service. A cluster does not care about…
-
What a Service Mesh Actually Does (and What It Doesn't)
A service mesh is a layer of proxies. That's the whole idea, stripped of the conference-stage mystique. Next to every pod, you run a second container — an Envoy proxy, the "sidecar" — and you route all of that pod's traffic…
-
Istio Without the Overwhelm
Istio has a reputation problem. You open the docs and drown: control planes, sidecars, gateways, virtual services, destination rules, telemetry pipelines, a CRD zoo that reads like someone was paid per resource kind. Most…
-
Identity 101 — OAuth2, OIDC, and Tokens
Ask five engineers on your team which OAuth flow their service uses. You will get three shrugs, one confident wrong answer, and one person who actually knows. That last person is the one who has read a token expiry error at 2am.…
OAuth 2.0 & OIDCJWT validation.NET & C#Microsoft Entra IDScopes & app roles
-
Microsoft Entra ID in plain language
You moved your web apps to Kubernetes and the authentication story fell apart on the way in.
Microsoft Entra ID.NET & C#Scopes & app rolesAzureKubernetes
-
Workload identity — how machines prove who they are
A user proves who they are with something they know, something they have, or something they are — a password, a passkey, a fingerprint. A service has none of those. It has no fingers, no phone, no memory between restarts. Yet the…
-
Terminating user identity at the mesh edge
A bug that ships to production quietly, in regulated shops, all the time:
Microsoft Entra IDJWT validationOAuth 2.0 & OIDCAuthorizationPolicy.NET & C#
-
Validating Entra JWTs in C#
An unverified token is just a string. A HALF-verified one is worse — it looks trusted, gets waved through, and carries an authority it never earned.
-
Egress control and the locked-down cluster
You locked the front door of your Kubernetes cluster. Ingress gateway, token validation, default-deny — the works.
-
Threat-modelling a meshed .NET API
You've spent a dozen articles building controls. Now ask the question nobody budgets for: what does each one do when it BREAKS?
Threat modellingAuthorizationPolicyCompliance evidenceJWT validationCERT-In & DPDP
-
If you can’t prove it, it didn’t happen — audit logging in the mesh
Your service mesh is already logging every request. Method, path, status code — for free.
-
The LGTM stack for compliance evidence
Loki, Grafana, Tempo, Mimir. Four letters everyone treats as one observability blob. To a regulator they answer four different questions — and putting the wrong one in the wrong store is how evidence quietly disappears.
LGTM stackCompliance evidenceDistributed tracingMulti-cluster & residencyOpenTelemetry
-
Tracing identity through a request
You turned on distributed tracing. Grafana draws the pretty waterfall. You feel covered.
Distributed tracingLGTM stackCompliance evidenceIstioOpenTelemetry
-
DORA for platform engineers — what the Act actually asks of your cluster
You have spent thirty‑three articles building one system: a regulated .NET platform on AKS, Istio and Entra, where every request is authenticated, authorised, encrypted and logged, and where the logs are signed and the posture is…
-
Designing the ComplianceProfile operator — compliance is a reconcile loop with a different noun
You have a PeerAuthentication that says STRICT. You have a Gatekeeper constraint that says every namespace must carry a default‑deny AuthorizationPolicy . You have Envoy access logs with SPIFFE identities, signed evidence packs…
Kubernetes operatorsCompliance evidencePolicy as code.NET & C#Supply-chain signing
-
Building a Kubernetes operator in C# — Kubernetes has no opinion about Go
The platform team reviews the Article 43 design and says, kindly, that operators are written in Go. Kubebuilder, controller‑runtime, the Operator SDK, the language the API server itself is written in. They are not wrong about the…
-
Shipping continuous evidence as a product — a report is something you send; evidence is something an auditor comes and takes
The ComplianceProfile status says Satisfied. It is signed. It is in the cluster. An external auditor from the FMA's appointed firm arrives, and the first thing she does is decline the dashboard, decline the kubectl session, and…
Compliance evidenceSupply-chain signing.NET & C#Kubernetes operatorsMicrosoft Entra ID