RepoJournal
.NET

@dotnet

The .NET runtime, ASP.NET, and the C# tooling

Keep up with .NET in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: .NET Full archive →

The Wire · Showcase

OPERATOR SDK 13.0 BREAKS CONTROLLER ARCHITECTURE, ANDROID TESTS GO LOCAL

By RepoJournal · Filed · About .NET

The dotnet-operator-sdk ships a major breaking change that fundamentally rewrites how multiple controllers target the same entity, while the Android team closes external test dependencies to fix certificate export failures on macOS.

The operator SDK v13.0.0-prerelease.1 [1] introduces a breaking change that restructures controller architecture: you can now run multiple controllers against the same entity type with independent label and field selectors [2]. This isn't a cosmetic API bump. Each controller gets its own watcher, queue, and reconciliation pipeline. You'll need to rewrite controller registration logic if you're targeting entities from multiple controllers, and the SDK now validates selector conflicts at compile time with error KOG001 [3]. Meanwhile, the Android team shipped a critical infrastructure fix: macOS Key Vault certificate exports were broken because PersistKeySet imports keys into the login Keychain where they can't be exported again, producing public-only PFX files [4]. The fix selects storage flags by OS, using Exportable-only on macOS so private keys stay in memory and survive export. The team also hardened test stability by replacing external HTTP services (httpbin.org, badssl.com) with local loopback servers [5], eliminating flaky remote dependencies. On the runtime front, TryParse APIs supporting AllowTrailingInvalidCharacters moved to explicit implementation to avoid breaking F# [6], and the .NET for Android build now excludes SourceLink runtime assets to prevent System.IO.Hashing version collisions in the SDK pack [7].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] v13.0.0-prerelease.1 ↗ dotnet/dotnet-operator-sdk
  2. [2] feat(operator)!: support multiple controllers and selectors per entity ↗ dotnet/dotnet-operator-sdk
  3. [3] feat(transpiler): add schema validation for CRD attributes ↗ dotnet/dotnet-operator-sdk
  4. [4] Load macOS Key Vault certs as Exportable only so private key survives export (#5259) dotnet/performance
  5. [5] [tests] Use local servers for networking tests ↗ dotnet/android
  6. [6] [main] Source code updates from dotnet/runtime (#7617) dotnet/dotnet
  7. [7] [build] Exclude SourceLink runtime assets to pin System.IO.Hashing ↗ dotnet/android

Quick answers

What shipped in .NET on July 11, 2026?
The dotnet-operator-sdk ships a major breaking change that fundamentally rewrites how multiple controllers target the same entity, while the Android team closes external test dependencies to fix certificate export failures on macOS. In total, 19 commits, 19 pull requests, and 2 releases landed.
Who contributed to .NET on July 11, 2026?
11 developers shipped this update, including github-actions[bot], kimpenhaus, renovate, Weihan Li, Viktor Hofer, dotnet-maestro[bot], Copilot, and dotnet-maestro, and 3 more.
What were the notable .NET updates?
v13.0.0-prerelease.1, feat(operator)!: support multiple controllers and selectors per entity, and feat(transpiler): add schema validation for CRD attributes.

More from @dotnet

Daily updates, in your inbox

Follow .NET

Keep up with .NET in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?

We use privacy-friendly analytics (Google Analytics, IP-anonymized) to see which pages help readers. No ads, and we never sell your data. See our Privacy Policy.