ISiloBuilder and Orleans 2.3.0 HostBuilder Extensions
See original GitHub issueI upgraded to the latest Orleans 2.3.0 build today in hopes of using the new HostBuilder
extensions. However, I noticed the HostBuilder.UseOrleans
method expects an action with a parameter of ISiloBuilder
instead of ISiloHostBuilder
that Orleans.Clustering expects.
The change to support this looks to be a straightforward addition to the extensions class where the this
parameter is of ISiloBuilder
type.
public static ISiloBuilder UseKubeMembership(this ISiloBuilder builder,
Action<KubeClusteringOptions> configureOptions)
{
return builder.ConfigureServices(services => services.UseKubeMembership(configureOptions));
}
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
GenericHostExtensions.UseOrleans Method
Configures the host builder to host an Orleans silo. UseOrleans(IHostBuilder, Action<HostBuilderContext,ISiloBuilder>). Configures the host builder to host an ...
Read more >SiloHostBuilderExtensions.Configure Method
The options type to be configured. Parameters. builder: ISiloHostBuilder. The host builder. configureOptions: Action<TOptions>.
Read more >Parameter Null Exception when calling Microsoft. ...
Exception when creating Host builder. Our Cronjob was working before that date ... Extensions.Hosting.HostBuilder.ConfigureServices(Action`2 ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
While moving the code over, I forgot to include the key piece:
Thanks for your patience and for this great library.
Edit: Leaving this here for posterity, but see next comment.
Odd, none of the endpoint options were necessary using the
SiloHostBuilder
.In any case, here is my solution:
Then use the downward api in the deployment manifest to get the pod IP: