feat: add .NET Aspire integration for KubeOps operators#1135
Conversation
bcc5a36 to
65fe4b5
Compare
|
Addressed the sample separation feedback: I also updated the Aspire docs/README snippets to use |
kimpenhaus
left a comment
There was a problem hiding this comment.
that looks pretty good to me in general - there are some minor things I'd like to recover
- the added debug processor in the operator sample as that fixes an unused using in release configuration.
- the two comments on the readme which were more precisely than the original text segments
thanks for your time @msexxeta
Add Aspire service defaults, AppHost hosting integration, Kubernetes run/publish support, examples, tests, and docs for local, Azure, and standalone publish scenarios. Co-authored-by: Marcus Kimpenhaus <kimpenhaus@devil-engineering.de>
65fe4b5 to
dc246a6
Compare
|
Restored the more precise README wording from the review:
I also put the plain operator sample's |
|
that's awesome - thanks 😄 |
|
Nice! This makes developing operaters much easier imo, especially when they are part of a bigger system. |
Summary
KubeOps.Aspireservice defaults for operator telemetry, service discovery, resilience, and health checksKubeOps.Aspire.HostingwithAddKubeOps<TProject>,RunWithKubernetes(...), andPublishAsKubernetesOperator(...)Validation
dotnet test test\KubeOps.Aspire.Hosting.Test\KubeOps.Aspire.Hosting.Test.csproj --no-restoredotnet test test\KubeOps.Aspire.Test\KubeOps.Aspire.Test.csproj --no-restorenpm run buildindocssucceeds; it still reports a pre-existing unrelated broken anchor indocs/operator/deploymente98c800b-fa26-4a4e-85c1-cd4aafbf5facwith temporary resources cleaned up afterwardscloses #926