<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ugur Mendi on Medium]]></title>
        <description><![CDATA[Stories by Ugur Mendi on Medium]]></description>
        <link>https://medium.com/@ugur.mendi?source=rss-db629fb1060a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*hj3JC8vF4NrsUCy2</url>
            <title>Stories by Ugur Mendi on Medium</title>
            <link>https://medium.com/@ugur.mendi?source=rss-db629fb1060a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 19:12:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ugur.mendi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Elastic APM with Fleet Agents]]></title>
            <link>https://medium.com/@ugur.mendi/elastic-apm-with-fleet-agents-9efc3691fa96?source=rss-db629fb1060a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9efc3691fa96</guid>
            <category><![CDATA[kibana]]></category>
            <category><![CDATA[elastic-apm]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[elasticsearch]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Ugur Mendi]]></dc:creator>
            <pubDate>Mon, 06 Nov 2023 12:28:45 GMT</pubDate>
            <atom:updated>2023-11-06T12:28:45.959Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Wadcwnm-KKj2wyq9.png" /></figure><p>Greetings to everyone.</p><p>This guide is aiming to help you about your Elastic APM journey.I am sharing the problems and the solutions which I faced through the journey.</p><p>So we can start!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KwDPyDWjNyrYTP0Z.png" /><figcaption>Example architecture of the system(taken from Elastic official documentation)</figcaption></figure><p>First of all,we need to install Elasticsearch and Kibana on the servers.</p><p>You can use official documentation for it:</p><p>Elastic:<a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/install-elasticsearch.html">https://www.elastic.co/guide/en/elasticsearch/reference/current/install-elasticsearch.html</a>(from official documentation)</p><p>Kibana:<a href="https://www.elastic.co/guide/en/kibana/current/install.html">https://www.elastic.co/guide/en/kibana/current/install.html</a>(from official documentation)</p><p>ElasticAgents:<a href="https://www.elastic.co/guide/en/fleet/current/install-fleet-managed-elastic-agent.html">https://www.elastic.co/guide/en/fleet/current/install-fleet-managed-elastic-agent.html</a>(from official documentation)</p><p>For my setup I run these(Elasticsearch and Kibana) as a service in the same server and also Fleet Server has been deployed on the same server.</p><p>Basically you are deploying an ElasticAgent into the application to gather tracing and logs and connecting it to Fleet Server.To do that you need to add integration both in your application and Agent Policy into Fleet Server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/441/1*nx64NNlE3Kf5_0OQrjCusw.png" /><figcaption>Example of my architecture</figcaption></figure><p>In Integrations page there are various of them and you can add/remove for your needs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*slzT8YyMqV4Zwohd8BnpXQ.png" /><figcaption>I added apm integration to the Fleet Server Agent</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OOLh7suefpovIqsxph4h_g.png" /><figcaption>Adding agents and Fleet Server agent can be done here</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sCt79qTQ2dPWHXIMcVJHZw.png" /><figcaption>This is the example of Fleet Server Agent Policy.</figcaption></figure><p>During the integration process there are various options you can optimize it by yourself.Also there are different programming languages which you can integrate agent with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OGlZbenPAw4vdJoW6B4fFQ.png" /></figure><p>For my needs I use this agent for .NetCore.</p><p>Add the agent to the application</p><p>In case of ASP.NET Core with the Elastic.Apm.NetCoreAll package, call the UseAllElasticApm method in the Configure method within the Startup.cs file.(from official documentation)</p><pre>public class Startup<br>{<br>  public void Configure(IApplicationBuilder app, IHostingEnvironment env)<br>  {<br>    app.UseAllElasticApm(Configuration);<br>    //…rest of the method<br>  }<br>  //…rest of the class<br>}</pre><p>Generally there is no Startup.cs in the projects so you can integrate it with example Program.cs:</p><pre>using Microsoft.AspNetCore.Builder;<br>using Microsoft.Extensions.DependencyInjection;<br>using Sample.ElasticApm.WebApi.Core.Extensions;<br>using Serilog;<br><br>var builder = WebApplication.CreateBuilder(args);<br>builder.AddSerilog(builder.Configuration, &quot;API Elastic APM&quot;);<br>Log.Information(&quot;Starting API&quot;);<br><br>builder.Services.AddApiConfiguration();<br><br>builder.Services.AddElasticsearch(builder.Configuration);<br>builder.Services.AddSqlDatabase(builder.Configuration);<br>builder.Services.AddSwagger(builder.Configuration);<br><br>builder.Services.AddEndpointsApiExplorer();<br>builder.Services.AddSwaggerGen();<br><br>var app = builder.Build();<br><br>app.UseApiConfiguration(app.Environment);<br><br>app.UseSwaggerDoc();<br>app.UseElasticApm(builder.Configuration);<br><br>app.MapControllers();<br><br>app.Run();<br><br></pre><p>After you made changes in Program.cs you need to make changes in appsettings.json for the connectivity of the agent.Here is example appsettings.json:</p><pre>  &quot;ElasticApm&quot;: {<br>    &quot;SecretToken&quot;: &quot;apm-server-secret-token&quot;,<br>    &quot;ServerUrl&quot;: &quot;http://localhost:8200&quot;,<br>    &quot;ServiceName&quot;: &quot;Sample ElasticApm&quot;,<br>    &quot;CaptureBody&quot;: &quot;all&quot;,<br>    &quot;ElasticApm:LogLevel&quot;: &quot;Debug&quot;<br>  },<br>  &quot;AllowedHosts&quot;: &quot;*&quot;<br>}</pre><p>You can specify the names of environment and service.Also you can specify the loglevel of ElasticApm, CaptureBody type and more.</p><p>Here is from official the code block for appsettings.json from official documentation you can customize it :</p><pre>{<br>  &quot;ElasticApm&quot;: {<br>    &quot;ServiceName&quot;: &quot;my-service-name&quot;,<br>    &quot;SecretToken&quot;: &quot;&quot;,<br>    &quot;ServerUrl&quot;: &quot;http://localhost:8200&quot;,<br>    &quot;Environment&quot;: &quot;my-environment&quot;,<br>  }<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*55oSY_pfx3Dbfo3aSsOidw.jpeg" /><figcaption>If you successfully deploy your agent you should able to see it in Services.</figcaption></figure><p>Congratulations! You have successfully completed the setup.These are example what you should see:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HrfQJ1JUShZbeyV7dNZe8w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ZbnaPPwA4JQ54hynRBKuA.png" /><figcaption>Traces are very helpful to identify the errors</figcaption></figure><p>Note:</p><p>You can also customize agent configuration from Kibana with this you can update agent configuration from the central it will deploy the changes selected/all agents with respect to your configuration:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sKo_5A0fzStgihPhAyAipA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZVTmjGBlTfMXJz8dsdqURw.png" /></figure><p>Thank you for your time and I hope this guide will helpfull.</p><p>Links:</p><ul><li><a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/install-elasticsearch.html">Installing Elasticsearch | Elasticsearch Guide [8.10] | Elastic</a></li><li><a href="https://www.elastic.co/guide/en/kibana/current/install.html">Install Kibana | Kibana Guide [8.10] | Elastic</a></li><li><a href="https://www.elastic.co/guide/en/observability/8.10/traces-get-started.html">Get started with application traces and APM | Elastic Observability [8.10] | Elastic</a></li><li><a href="https://www.elastic.co/guide/en/fleet/current/fleet-overview.html">Fleet and Elastic Agent overview | Fleet and Elastic Agent Guide [8.10] | Elastic</a></li><li><a href="https://www.elastic.co/guide/en/apm/guide/current/apm-overview.html">Free and open application performance monitoring | APM User Guide [8.10] | Elastic</a></li><li><a href="https://www.elastic.co/guide/en/apm/agent/dotnet/current/intro.html">Introduction | APM .NET Agent Reference [1.x] | Elastic</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9efc3691fa96" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Talos Linux with Vcenter Integration]]></title>
            <link>https://medium.com/paramtech/talos-linux-with-vcenter-integration-9174ce55b428?source=rss-db629fb1060a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9174ce55b428</guid>
            <category><![CDATA[vmware]]></category>
            <category><![CDATA[vcenter]]></category>
            <category><![CDATA[system]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Ugur Mendi]]></dc:creator>
            <pubDate>Tue, 26 Sep 2023 09:05:32 GMT</pubDate>
            <atom:updated>2023-09-26T09:05:32.886Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LxiFaQwgiOG40IFU.jpg" /></figure><p>Greetings to everyone.</p><p>This guide is aiming to help you about your Talos journey.I will share the problems and the solutions which I faced through this journey.</p><p>So we can start!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/490/1*WGxDKjvXQ7SJ6fcTcgsHNg.png" /><figcaption>Basic Architecture of the system</figcaption></figure><p>First of all,we need to have talosctl in bastion(for my architecture) which can be downloaded with the command:</p><pre>curl -sL https://talos.dev/install | sh</pre><p>We are using the bastion machine for external load-balancer,talosctl and kubectl hosts.</p><p>For the Vcenter side we are mounting the live iso of the talos linux which can be downloaded with this link:</p><p>X86: <a href="https://github.com/siderolabs/talos/releases/download/v1.5.0/metal-amd64.iso">https://github.com/siderolabs/talos/releases/download/v1.5.0/metal-amd64.iso</a> (for my architecture I use x86 image)</p><p>ARM64: <a href="https://github.com/siderolabs/talos/releases/download/v1.5.0/metal-arm64.iso">https://github.com/siderolabs/talos/releases/download/v1.5.0/metal-arm64.iso</a></p><p>I use the recommend system requirements for my setup:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/541/1*noIHz2JR4h7aKAcIMbpQtw.png" /></figure><p>(From official documentation)</p><h4>After We have mounted the Talos live iso to our hosts we need to make initial configuration from Vcenter Cli for the static ips,dns and ntp server connection!</h4><p>For the endpoint configuration of the talos we have multiple options,</p><h3>Decide the Kubernetes Endpoint</h3><p>The Kubernetes API Server endpoint, in order to be highly available, should be configured in a way that uses all available control plane nodes. There are three common ways to do this: using a load-balancer, using Talos Linux’s built in VIP functionality, or using multiple DNS records.</p><h3>Dedicated Load-balancer</h3><p>If you are using a cloud provider or have your own load-balancer (such as HAProxy, Nginx reverse proxy, or an F5 load-balancer), a dedicated load balancer is a natural choice. Create an appropriate frontend for the endpoint, listening on TCP port 6443, and point the backends at the addresses of each of the Talos control plane nodes. Your Kubernetes endpoint will be the IP address or DNS name of the load balancer front end, with the port appended (e.g. <a href="https://myk8s.mydomain.io:6443/">https://myK8s.mydomain.io:6443</a>).</p><blockquote><em>Note: an HTTP load balancer can’t be used, as Kubernetes API server does TLS termination and mutual TLS authentication.</em></blockquote><h3>Layer 2 VIP Shared IP</h3><p>Talos has integrated support for serving Kubernetes from a shared/virtual IP address. This requires Layer 2 connectivity between control plane nodes.</p><p>Choose an unused IP address on the same subnet as the control plane nodes for the VIP. For instance, if your control plane node IPs are:</p><ul><li>192.168.0.10</li><li>192.168.0.11</li><li>192.168.0.12</li></ul><p>you could choose the IP 192.168.0.15 as your VIP IP address. (Make sure that 192.168.0.15 is not used by any other machine and is excluded from DHCP ranges.)</p><p>(From official documentation)</p><p>For my setup I didn’t handle endpoint configuration with loadbalancer or virtualIP I only provide the master nodes ip as shown below in my talosconfig :</p><pre>context: mycluster<br>contexts:<br>    mycluster:<br>        endpoints:<br>            - 127.0.0.1<br>            - controlplaneip<br>        nodes:<br>            - controlplaneip<br>            - worker1<br>            - worker2</pre><p>For the generation of the config files run the following command(command endpoint depends on virtual ip and loadbalancer usage) :</p><pre>$ talosctl gen config mycluster https://192.168.0.2:6443<br><br>generating PKI and tokens<br><br>created /Users/taloswork/controlplane.yaml<br><br>created /Users/taloswork/worker.yaml<br><br>created /Users/taloswork/talosconfig</pre><p>When you run this command, three files are created in your current directory:</p><ul><li>controlplane.yaml</li><li>worker.yaml</li><li>talosconfig</li></ul><p>The .yaml files are Machine Configs: they describe everything from what disk Talos should be installed on, to network settings. The controlplane.yaml file also describes how Talos should form a Kubernetes cluster.</p><p>The talosconfig file is your local client configuration file, used to connect to and authenticate access to the cluster.</p><p>(From the official documentation)</p><p>Note:For the globalconfig file you can add talosconfig to the path as config to /root/.talos/config (it is optional if you do not add this you need to specify config file with each command with — talosconfig parameter)</p><p>Here comes to tricky part in here for Vcenter When you execute the command for applying the machine config to Talos Linux live iso so can face with this problem I will show the command execution and error below:</p><pre>$ talosctl apply-config --insecure -n 192.168.0.2(change it with controlplaneip) --file controlplane.yaml<br><br>error applying new configuration: rpc error: code = InvalidArgument desc = configuration validation failed: 1 error occurred:<br><br>    * specified install disk does not exist: &quot;/dev/sda&quot;</pre><p>Normally you need to change the disk partition from controlplane.yaml with respect to the output of the following command:</p><pre>$ talosctl -n 192.168.0.2(change it with controlplaneip) disks --insecure<br><br>DEV        MODEL   SERIAL   TYPE   UUID   WWID  MODALIAS                    NAME   SIZE    BUS_PATH<br>here<br>/dev/vda   -       -        HDD    -      -      virtio:d00000002v00001AF4   -      69 GB   /pci0000:00/0000:00:06.0/virtio2/</pre><p>In my case when I executed this command it returns empty prompt,after I made reseach about it I realise that I needed to add following configuration into my machine settings via Vcenter:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*RvRE_0AJLW5C_w_GBCTl0g.png" /><figcaption>Add Sata controller and SCSI controller</figcaption></figure><p>After that you can execute the command:</p><pre>$ talosctl apply-config --insecure -n 192.168.0.2(change it with controlplaneip) --file controlplane.yaml</pre><p>It will take sometime and after that you finish controlplane installation:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M-hAh17mxwSMQZeNUwDpNg.png" /></figure><p>During the installation there is a warning that you should execute the command for bootstrapping:</p><pre>talosctl bootstrap --nodes 192.168.0.2(controlplaneip) --endpoint 192.168.0.2(controlplaneip) \<br>  --talosconfig=./talosconfig</pre><p>After that you can continue with the worker nodes:</p><pre>  talosctl apply-config --insecure \<br>    --nodes 192.168.0.2(workernodeip) \<br>    --file worker.yaml</pre><p>It will also take sometime.</p><p>Finally with this command you can extract kubeconfig and you can start using kubectl commands:</p><pre> talosctl kubeconfig --nodes 192.168.0.2 --endpoint 192.168.0.2</pre><p>Thank you for your time and I hope this guide will helpfull.</p><p>Links:</p><ul><li><a href="https://www.talos.dev/v1.5/introduction/getting-started/">Getting Started</a></li><li><a href="https://www.talos.dev/v1.5/introduction/prodnotes/">Production Clusters</a></li><li><a href="https://www.talos.dev/v1.5/introduction/system-requirements/">System Requirements</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9174ce55b428" width="1" height="1" alt=""><hr><p><a href="https://medium.com/paramtech/talos-linux-with-vcenter-integration-9174ce55b428">Talos Linux with Vcenter Integration</a> was originally published in <a href="https://medium.com/paramtech">ParamTech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>