{"id":248,"date":"2024-06-23T07:27:27","date_gmt":"2024-06-23T07:27:27","guid":{"rendered":"https:\/\/dotnetconfig.org\/blog\/?p=248"},"modified":"2024-07-01T07:36:51","modified_gmt":"2024-07-01T07:36:51","slug":"leveraging-etcd-in-kubernetes-for-effective-net-configuration-management-across-containerized-applications","status":"publish","type":"post","link":"https:\/\/dotnetconfig.org\/blog\/leveraging-etcd-in-kubernetes-for-effective-net-configuration-management-across-containerized-applications\/","title":{"rendered":"Leveraging etcd in Kubernetes for Effective .NET Configuration Management Across Containerized Applications"},"content":{"rendered":"

\"LeveragingManaging configurations efficiently is paramount. Combining the power of etcd, Kubernetes, and .NET Core, developers can orchestrate robust distributed key-value stores tailor-made for dynamic environments. This article delves into the intricacies of using etcd within Kubernetes to manage .NET Configuration settings effectively for containerized applications.<\/span><\/p>\n

Setting Up a Kubernetes Cluster with etcd<\/b><\/h3>\n

To harness etcd in managing .NET configurations, the first step involves setting up a Kubernetes cluster provisioned with etcd. Kubernetes, by default, utilizes etcd as its primary data store for cluster state management. However, leveraging etcd for application configurations requires additional steps.<\/span><\/p>\n

# kube-etcd.yaml<\/span><\/p>\n

apiVersion: v1<\/span><\/p>\n

kind: Pod<\/span><\/p>\n

metadata:<\/span><\/p>\n

\u00a0\u00a0name: etcd<\/span><\/p>\n

spec:<\/span><\/p>\n

\u00a0\u00a0containers:<\/span><\/p>\n

\u00a0\u00a0– name: etcd<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0image: quay.io\/coreos\/etcd:v3.4.15<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0ports:<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0– containerPort: 2379<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0– containerPort: 2380<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0volumeMounts:<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0– name: etcd-data<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0mountPath: \/etcd-data<\/span><\/p>\n

\u00a0\u00a0volumes:<\/span><\/p>\n

\u00a0\u00a0– name: etcd-data<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0emptyDir: {}<\/span><\/p>\n

Deploy the etcd Pod in your Kubernetes cluster with the above YAML file.<\/span><\/p>\n

kubectl apply -f kube-etcd.yaml<\/span><\/p>\n

Configuring .NET Applications to Use etcd<\/b><\/h3>\n

.NET Core provides a robust configuration API, allowing developers to easily integrate multiple configuration sources. To incorporate etcd as a configuration source, we’ll leverage the ETCD Client for .NET, <\/span>dotnet-etcd<\/span>. First, install the necessary package in your .NET Core application.<\/span><\/p>\n

dotnet add package dotnet-etcd<\/span><\/p>\n

Next, adjust the application\u2019s Startup class to include etcd as a configuration provider.<\/span><\/p>\n

using dotnet_etcd;<\/span><\/p>\n

using Microsoft.Extensions.Configuration;<\/span><\/p>\n

 <\/p>\n

public class Startup<\/span><\/p>\n

{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0public Startup(IConfiguration configuration)<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Configuration = configuration;<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0}<\/span><\/p>\n

 <\/p>\n

\u00a0\u00a0\u00a0\u00a0public IConfiguration Configuration { get; }<\/span><\/p>\n

 <\/p>\n

\u00a0\u00a0\u00a0\u00a0public void ConfigureServices(IServiceCollection services)<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0var etcdClient = new EtcdClient(“http:\/\/<etcd-service-ip>:2379”);<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0var etcdConfigurationSource = new EtcdConfigurationSource(etcdClient, “dotnet-config”);<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0var builder = new ConfigurationBuilder()<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0.AddConfiguration(Configuration)<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0.Add(etcdConfigurationSource);<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0IConfigurationRoot configuration = builder.Build();<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0services.AddSingleton<IConfiguration>(configuration);<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\/\/ Add other services required for your application<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0}<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0public void Configure(IApplicationBuilder app, IWebHostEnvironment env)<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\/\/ Configure the HTTP request pipeline<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0}<\/span><\/p>\n

}<\/span><\/p>\n

Implement an <\/span>EtcdConfigurationSource<\/span> to fetch the configurations from etcd.<\/span><\/p>\n

using dotnet_etcd;<\/span><\/p>\n

using Microsoft.Extensions.Configuration;<\/span><\/p>\n

using System.Threading;<\/span><\/p>\n

using System.Threading.Tasks;<\/span><\/p>\n

 <\/p>\n

public class EtcdConfigurationSource : IConfigurationSource<\/span><\/p>\n

{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0private readonly EtcdClient _client;<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0private readonly string _key;<\/span><\/p>\n

 <\/p>\n

\u00a0\u00a0\u00a0\u00a0public EtcdConfigurationSource(EtcdClient client, string key)<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0_client = client;<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0_key = key;<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0}<\/span><\/p>\n

 <\/p>\n

\u00a0\u00a0\u00a0\u00a0public IConfigurationProvider Build(IConfigurationBuilder builder)<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0return new EtcdConfigurationProvider(_client, _key);<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0}<\/span><\/p>\n

}<\/span><\/p>\n

 <\/p>\n

public class EtcdConfigurationProvider : ConfigurationProvider<\/span><\/p>\n

{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0private readonly EtcdClient _client;<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0private readonly string _key;<\/span><\/p>\n

 <\/p>\n

\u00a0\u00a0\u00a0\u00a0public EtcdConfigurationProvider(EtcdClient client, string key)<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0_client = client;<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0_key = key;<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0}<\/span><\/p>\n

 <\/p>\n

\u00a0\u00a0\u00a0\u00a0public override void Load()<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0var etcdResponse = _client.GetStringAsync(_key).Result;<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Data = new Dictionary<string, string><\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{ _key, etcdResponse }<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0};<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0}<\/span><\/p>\n

 <\/p>\n

\u00a0\u00a0\u00a0\u00a0public override void Set(string key, string value)<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0_client.PutAsync(key, value).Wait();<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0base.Set(key, value);<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0}<\/span><\/p>\n

}<\/span><\/p>\n

Managing Configuration Changes in etcd<\/b><\/h3>\n

One of the significant advantages of using etcd is its capability to handle dynamic configuration changes without restarting the application. You can monitor changes and update configurations dynamically.<\/span><\/p>\n

public class EtcdConfigurationProvider : ConfigurationProvider<\/span><\/p>\n

{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0private readonly EtcdClient _client;<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0private readonly string _key;<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0private CancellationTokenSource _cancellationTokenSource;<\/span><\/p>\n

 <\/p>\n

\u00a0\u00a0\u00a0\u00a0public EtcdConfigurationProvider(EtcdClient client, string key)<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0_client = client;<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0_key = key;<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0_cancellationTokenSource = new CancellationTokenSource();<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0WatchEtcdKey(_key);<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0}<\/span><\/p>\n

 <\/p>\n

\u00a0\u00a0\u00a0\u00a0private void WatchEtcdKey(string key)<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Task.Run(async () =><\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0while (!_cancellationTokenSource.Token.IsCancellationRequested)<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0var watchResponse = await _client.WatchRangeAsync(key, _cancellationTokenSource.Token);<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0foreach (var watchEvent in watchResponse.Events)<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0switch (watchEvent.Type)<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0case Mvccpb.Event.Types.EventType.Put:<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Set(key, watchEvent.Kv.Value.ToStringUtf8());<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0OnReload();<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0break;<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0case Mvccpb.Event.Types.EventType.Delete:<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Data.Remove(key);<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0OnReload();<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0break;<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0}<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0}<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0}<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0});<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0}<\/span><\/p>\n

 <\/p>\n

\u00a0\u00a0\u00a0\u00a0public override void Load()<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0var etcdResponse = _client.GetAsync(_key).Result;<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0Data = etcdResponse.Kvs.ToDictionary(<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0kv => kv.Key.ToStringUtf8(),<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0kv => kv.Value.ToStringUtf8());<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0}<\/span><\/p>\n

 <\/p>\n

\u00a0\u00a0\u00a0\u00a0public override void Set(string key, string value)<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0_client.PutAsync(key, value).Wait();<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0base.Set(key, value);<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0}<\/span><\/p>\n

}<\/span><\/p>\n

Deploying and Managing the .NET Application in Kubernetes<\/b><\/h3>\n

Having configured your .NET application to leverage etcd, the next step is containerizing and deploying it into the Kubernetes cluster. Begin by creating a Dockerfile for your .NET application.<\/span><\/p>\n

# Dockerfile<\/span><\/p>\n

FROM mcr.microsoft.com\/dotnet\/aspnet:5.0 AS base<\/span><\/p>\n

WORKDIR \/app<\/span><\/p>\n

EXPOSE 80<\/span><\/p>\n

 <\/p>\n

FROM mcr.microsoft.com\/dotnet\/sdk:5.0 AS build<\/span><\/p>\n

WORKDIR \/src<\/span><\/p>\n

COPY [“MyApp\/MyApp.csproj”, “MyApp\/”]<\/span><\/p>\n

RUN dotnet restore “MyApp\/MyApp.csproj”<\/span><\/p>\n

COPY . .<\/span><\/p>\n

WORKDIR “\/src\/MyApp”<\/span><\/p>\n

RUN dotnet build “MyApp.csproj” -c Release -o \/app\/build<\/span><\/p>\n

 <\/p>\n

FROM build AS publish<\/span><\/p>\n

RUN dotnet publish “MyApp.csproj” -c Release -o \/app\/publish<\/span><\/p>\n

 <\/p>\n

FROM base AS final<\/span><\/p>\n

WORKDIR \/app<\/span><\/p>\n

COPY –from=publish \/app\/publish .<\/span><\/p>\n

ENTRYPOINT [“dotnet”, “MyApp.dll”]<\/span><\/p>\n

Build the Docker image.<\/span><\/p>\n

docker build -t myapp:latest .<\/span><\/p>\n

Push the Docker image to a container registry.<\/span><\/p>\n

docker tag myapp:latest <your-registry>\/myapp:latest<\/span><\/p>\n

docker push <your-registry>\/myapp:latest<\/span><\/p>\n

Create a Kubernetes deployment and service for your .NET application.<\/span><\/p>\n

# myapp-deployment.yaml<\/span><\/p>\n

apiVersion: apps\/v1<\/span><\/p>\n

kind: Deployment<\/span><\/p>\n

metadata:<\/span><\/p>\n

\u00a0\u00a0name: myapp-deployment<\/span><\/p>\n

spec:<\/span><\/p>\n

\u00a0\u00a0replicas: 3<\/span><\/p>\n

\u00a0\u00a0selector:<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0matchLabels:<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0app: myapp<\/span><\/p>\n

\u00a0\u00a0template:<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0metadata:<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0labels:<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0app: myapp<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0spec:<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0containers:<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0– name: myapp<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0image: <your-registry>\/myapp:latest<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0ports:<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0– containerPort: 80<\/span><\/p>\n

—<\/span><\/p>\n

apiVersion: v1<\/span><\/p>\n

kind: Service<\/span><\/p>\n

metadata:<\/span><\/p>\n

\u00a0\u00a0name: myapp-service<\/span><\/p>\n

spec:<\/span><\/p>\n

\u00a0\u00a0selector:<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0app: myapp<\/span><\/p>\n

\u00a0\u00a0ports:<\/span><\/p>\n

\u00a0\u00a0– protocol: TCP<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0port: 80<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0targetPort: 80<\/span><\/p>\n

\u00a0\u00a0type: LoadBalancer<\/span><\/p>\n

Deploy the configuration to your Kubernetes cluster.<\/span><\/p>\n

kubectl apply -f myapp-deployment.yaml<\/span><\/p>\n

Scaling and Updating Configuration<\/b><\/h3>\n

One of Kubernetes’ core features is scalability. The application scales seamlessly, and etcd ensures that configuration consistency is maintained across all instances. Any change in the etcd configuration is immediately propagated to all running instances of your application, ensuring uniform behavior.<\/span><\/p>\n

When you need to update configuration values, simply update them in etcd. The changes will be detected and applied dynamically across all relevant application instances without needing a restart.<\/span><\/p>\n

etcdctl put \/dotnet-config\/key “new-value”<\/span><\/p>\n

Strategically using etcd within Kubernetes for managing .NET application configurations allows developers to build highly scalable, fault-tolerant, and dynamically managed environments. By following the steps outlined, you can ensure that your application benefits from the robustness and scalability inherent in Kubernetes, while leveraging the distributed key-value store capabilities of etcd for efficient configuration management.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Managing configurations efficiently is paramount. Combining the power of etcd, Kubernetes, and .NET Core, developers can orchestrate robust distributed key-value stores tailor-made for dynamic environments. This article delves into the intricacies of using etcd within Kubernetes to manage .NET Configuration settings effectively for containerized applications. Setting Up a Kubernetes Cluster with etcd To harness etcd […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-248","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/dotnetconfig.org\/blog\/wp-json\/wp\/v2\/posts\/248","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dotnetconfig.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dotnetconfig.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dotnetconfig.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dotnetconfig.org\/blog\/wp-json\/wp\/v2\/comments?post=248"}],"version-history":[{"count":1,"href":"https:\/\/dotnetconfig.org\/blog\/wp-json\/wp\/v2\/posts\/248\/revisions"}],"predecessor-version":[{"id":250,"href":"https:\/\/dotnetconfig.org\/blog\/wp-json\/wp\/v2\/posts\/248\/revisions\/250"}],"wp:attachment":[{"href":"https:\/\/dotnetconfig.org\/blog\/wp-json\/wp\/v2\/media?parent=248"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dotnetconfig.org\/blog\/wp-json\/wp\/v2\/categories?post=248"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dotnetconfig.org\/blog\/wp-json\/wp\/v2\/tags?post=248"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}