Enable AOT compatibility for Yarp.Kubernetes.Controller

[Copilot]

Yarp.Kubernetes.Controller emits IL2026/IL3050 warnings due to reflection-based JSON serialization and configuration binding, blocking use in Native AOT/trimmed applications.

Changes

JSON Source Generator (System.Text.Json)

• New KubernetesJsonSerializerContext — JsonSerializerContext with [JsonSerializable] for Message, List<RouteConfig>, and List<ClusterConfig>; transitive types are handled automatically
• Message.cs — switched [JsonConverter(typeof(JsonStringEnumConverter))] to the generic JsonStringEnumConverter<MessageType> (introduced in .NET 8, required for source-gen compatibility)
• DispatchConfigProvider, DispatchActionResult, Receiver, Reconciler — all JsonSerializer.* calls now pass the generated JsonTypeInfo<T> from KubernetesJsonSerializerContext.Default:

// Before
var bytes = JsonSerializer.SerializeToUtf8Bytes(message);
var message = JsonSerializer.Deserialize<Message>(json);

// After
var bytes = JsonSerializer.SerializeToUtf8Bytes(message, KubernetesJsonSerializerContext.Default.Message);
var message = JsonSerializer.Deserialize<Message>(json, KubernetesJsonSerializerContext.Default.Message);

ConfigurationBinder Source Generator

• KubernetesReverseProxyServiceCollectionExtensions — replaced services.Configure<YarpOptions>(config.GetSection("Yarp")) with an explicit Bind call so the Microsoft.Extensions.Configuration.Binder source generator can intercept and emit AOT-safe binding code:

// Before — hides the Bind call inside the extension, generator can't intercept
services.Configure<YarpOptions>(config.GetSection("Yarp"));

// After — explicit Bind call is intercepted by the source generator
services.Configure<YarpOptions>(o => config.GetSection("Yarp").Bind(o));

AOT Compatibility Test

• <IsAotCompatible>true</IsAotCompatible> added to Yarp.Kubernetes.Controller.csproj — enables build-time Roslyn trim/AOT static analysis on the library, surfacing any future violations as build errors.

• New testassets/Kubernetes.AotCompatibility.TestApp — a PublishAot=true console app targeting net10.0 (following the dotnet/extensions pattern) that references all three AOT-compatible YARP assemblies with TrimmerRootAssembly for each:

  • Yarp.Kubernetes.Controller: Combined (AddKubernetesReverseProxy + UseKubernetesReverseProxyCertificateSelector), Monitor (AddKubernetesIngressMonitor + AddKubernetesDispatchController), and Receiver (Configure<ReceiverOptions> + Receiver + LoadFromMessages) scenarios
  • Yarp.ReverseProxy: Standalone reverse proxy scenario (AddReverseProxy().LoadFromConfig(...))
  • Yarp.Telemetry.Consumption: Telemetry listener scenario (AddTelemetryListeners())

  Publishing this app with AOT will flag any trim/AOT regressions introduced in the future across all AOT-compatible YARP libraries.

[eerhardt]

@copilot - also add an AOT compatibility test like described in

https://devblogs.microsoft.com/dotnet/creating-aot-compatible-libraries/#analyzing-.net-libraries

See https://github.com/dotnet/extensions/tree/main/test/Libraries/Microsoft.Extensions.AotCompatibility.TestApp for an example

[Copilot]

@copilot - also add an AOT compatibility test like described in

https://devblogs.microsoft.com/dotnet/creating-aot-compatible-libraries/#analyzing-.net-libraries
...

Done in dd0c957. Added two things:

1. <IsAotCompatible>true</IsAotCompatible> to Yarp.Kubernetes.Controller.csproj — enables build-time Roslyn trim/AOT analyzers on the library itself, surfacing any future violations as build errors.

2. testassets/Kubernetes.AotCompatibility.TestApp/ — a PublishAot=true console app (patterned after the dotnet/extensions example) that exercises the three main usage scenarios: combined (AddKubernetesReverseProxy), monitor (AddKubernetesIngressMonitor + AddKubernetesDispatchController), and receiver (Configure<ReceiverOptions> + Receiver + LoadFromMessages). Publishing this app with AOT will flag any trim/AOT regressions.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• devblogs.microsoft.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[eerhardt]

@copilot Just make this the latest TFM - net10.0.

[Copilot]

Done in b5bf7f6 — changed to <TargetFramework>net10.0</TargetFramework> (singular).

[eerhardt]

@copilot - this should reference all the projects that are AOT compatible in teh repo.

Also, it needs TrimmerRootAssembly for each one. see https://github.com/dotnet/extensions/blob/b3f2f408fe70f0d8e1f8fb2385bcfc8e9e81158d/test/Libraries/Microsoft.Extensions.AotCompatibility.TestApp/Microsoft.Extensions.AotCompatibility.TestApp.csproj for an example

[Copilot]

Done in b5bf7f6. The csproj now references all three AOT-compatible YARP assemblies with TrimmerRootAssembly for each, and Program.cs adds scenarios for AddReverseProxy().LoadFromConfig(...) and AddTelemetryListeners().