Akka.Discovery.Azure 1.5.19

The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org. Prefix Reserved
dotnet add package Akka.Discovery.Azure --version 1.5.19
NuGet\Install-Package Akka.Discovery.Azure -Version 1.5.19
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Akka.Discovery.Azure" Version="1.5.19" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Akka.Discovery.Azure --version 1.5.19
#r "nuget: Akka.Discovery.Azure, 1.5.19"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Akka.Discovery.Azure as a Cake Addin
#addin nuget:?package=Akka.Discovery.Azure&version=1.5.19

// Install Akka.Discovery.Azure as a Cake Tool
#tool nuget:?package=Akka.Discovery.Azure&version=1.5.19

Azure Table Storage Based Discovery

This module can be used as a discovery method for any cluster that has access to an Azure Table Storage service.

Configuring Using Akka.Hosting

You can programmatically configure Akka.Discovery.Azure using Akka.Hosting.

using var host = new HostBuilder()
    .ConfigureServices((hostContext, services) =>
    {
        services.AddAkka("actorSystem", (builder, provider) =>
        {
            builder.WithAzureDiscovery("your-azure-conection-string");
        });
    })
    .Build();

await host.RunAsync();

Configuring Using HOCON

You will need to include these HOCON settings in your HOCON configuration:

akka.discovery {
  method = azure
  azure {
    # The service name assigned to the cluster.
    service-name = "default"
    
    # The connection string used to connect to Azure Table hosting the cluster membership table
    # MANDATORY FIELD: MUST be provided, else the discovery plugin WILL throw an exception.
    connection-string = "<connection-string>"
  }
}

Notes

  • The akka.discovery.azure.connection-string setting is mandatory
  • For Akka.Discovery.Azure to work with multiple clusters, each cluster will have to have different akka.discovery.azure.service-name settings.

Configuring Using ActorSystemSetup

You can programmatically configure Akka.Discovery.Azure using the AzureDiscoverySetup class.

var config = ConfigurationFactory.ParseString(File.ReadAllText("app.conf"));

var bootstrap = BootstrapSetup.Create()
    .WithConfig(config) // load HOCON
    .WithActorRefProvider(ProviderSelection.Cluster.Instance); // launch Akka.Cluster
                
var azureSetup = new AzureDiscoverySetup()
    .WithConnectionString(connectionString);

var actorSystemSetup = bootstrap.And(azureSetup);

var system = ActorSystem.Create("my-system", actorSystemSetup);

Using Discovery Together with Akka.Management and Cluster.Bootstrap

All discovery plugins are designed to work with Cluster.Bootstrap to provide an automated way to form a cluster that is not based on hard wired seeds configuration.

Configuring using Akka.Hosting

With Akka.Hosting, you can wire them together like this:

using var host = new HostBuilder()
    .ConfigureServices((hostContext, services) =>
    {
        services.AddAkka("actorSystem", (builder, provider) =>
        {
            builder
                // Add Akka.Remote support
                .WithRemoting(hostname: "", port: 4053)
                // Add Akka.Cluster support
                .WithClustering()
                // Add Akka.Management.Cluster.Bootstrap support
                .WithClusterBootstrap()
                // Add Akka.Discovery.Azure support
                .WithAzureDiscovery("your-azure-conection-string");
        });
    })
    .Build();

await host.RunAsync();

Configuring using HOCON configuration

Some HOCON configuration is needed to make discovery work with Cluster.Bootstrap:

akka.discovery.method = azure
akka.discovery.azure.connection-string = "UseDevelopmentStorage=true"
akka.management.http.routes = {
    cluster-bootstrap = "Akka.Management.Cluster.Bootstrap.ClusterBootstrapProvider, Akka.Management.Cluster.Bootstrap"
}

You then start the cluster bootstrapping process by calling:

await AkkaManagement.Get(system).Start();
await ClusterBootstrap.Get(system).Start();

A more complete example:

var config = ConfigurationFactory
    .ParseString(File.ReadAllText("app.conf""))
    .WithFallback(ClusterBootstrap.DefaultConfiguration())
    .WithFallback(AkkaManagementProvider.DefaultConfiguration());

var bootstrap = BootstrapSetup.Create()
    .WithConfig(config) // load HOCON
    .WithActorRefProvider(ProviderSelection.Cluster.Instance); // launch Akka.Cluster

var azureSetup = new AzureDiscoverySetup()
    .WithConnectionString(connectionString);

var actorSystemSetup = bootstrap.And(azureSetup);

var system = ActorSystem.Create("my-system", actorSystemSetup);

var log = Logging.GetLogger(system, this);

await AkkaManagement.Get(system).Start();
await ClusterBootstrap.Get(system).Start();

var cluster = Cluster.Get(system);
cluster.RegisterOnMemberUp(() => {
  var upMembers = cluster.State.Members
      .Where(m => m.Status == MemberStatus.Up)
      .Select(m => m.Address.ToString());

  log.Info($"Current up members: [{string.Join(", ", upMembers)}]")
});
Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.5.19 242 4/17/2024
1.5.18-beta2 49 3/27/2024
1.5.18-beta1 61 3/20/2024
1.5.17.1 2,131 3/4/2024
1.5.15 4,667 1/12/2024
1.5.7 12,216 5/23/2023
1.5.5 364 5/8/2023
1.5.0 2,818 3/2/2023
1.5.0-beta6 114 3/1/2023
1.5.0-alpha4 110 2/17/2023
1.0.3 381 2/13/2023
1.0.2 238 2/8/2023
1.0.1 330 1/31/2023
1.0.0 343 1/18/2023
1.0.0-beta2 171 1/7/2023
1.0.0-beta1 113 1/6/2023
0.3.0-beta4 785 12/2/2022
0.3.0-beta3 294 11/7/2022
0.3.0-beta2 716 10/20/2022
0.3.0-beta1 163 10/6/2022
0.2.5-beta4 830 8/31/2022
0.2.5-beta3 351 8/16/2022
0.2.5-beta2 143 8/8/2022
0.2.5-beta1 144 8/1/2022

Update to [Akka.NET v1.5.19](https://github.com/akkadotnet/akka.net/releases/tag/1.5.19)
[Discovery.KubernetesApi: Add option to query pods in all namespaces](https://github.com/akkadotnet/Akka.Management/pull/2421)
[Coordination.KubernetesApi: Change lease expiration calculation to be based on DateTime.Ticks instead of DateTime.TimeOfDay.TotalMilliseconds](https://github.com/akkadotnet/Akka.Management/pull/2474)
[Coordination.KubernetesApi: Fix KubernetesSettings configuration bug](https://github.com/akkadotnet/Akka.Management/pull/2475)
[Management: Fix host name IPV6 detection](https://github.com/akkadotnet/Akka.Management/pull/2476)
Update dependency NuGet package versions to latest versions
[Bump Akka.Hosting to 1.5.19](https://github.com/akkadotnet/Akka.Management/pull/2478)
[Bump Google.Protobuf to 3.26.1](https://github.com/akkadotnet/Akka.Management/pull/2436)
[Bump KubernetesClient to 13.0.26](https://github.com/akkadotnet/Akka.Management/pull/2405)
[Bump Petabridge.Cmd to 1.4.1](https://github.com/akkadotnet/Akka.Management/pull/2418)
[Bump AWSSDK.S3 to 3.7.307](https://github.com/akkadotnet/Akka.Management/pull/2412)
[Bump AWSSDK.CludFormation to 3.7.305.4](https://github.com/akkadotnet/Akka.Management/pull/2430)
[Bump AWSSDK.ECS to 3.7.305.21](https://github.com/akkadotnet/Akka.Management/pull/2414)
[Bump AWSSDK.EC2 to 3.7.318](https://github.com/akkadotnet/Akka.Management/pull/2417)
Breaking Change Warning**
This release introduces a breaking change on how `Akka.Coordination.KubernetesApi` calculates lease expiration.**
If you're upgrading `Akka.Coordination.KubernetesApi` from v1.5.18-beta2 or lower to 1.5.19, do not attempt to do a Kubernetes cluster rolling update. Instead, you will have to down the whole Akka.NET cluster (or scale everything to 0) first, then deploy the newly upgraded nodes.