<?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 Manokaran on Medium]]></title>
        <description><![CDATA[Stories by Manokaran on Medium]]></description>
        <link>https://medium.com/@mano.panneer94?source=rss-d9ce48bdb465------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Stories by Manokaran on Medium</title>
            <link>https://medium.com/@mano.panneer94?source=rss-d9ce48bdb465------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 13:04:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mano.panneer94/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[Migrating from Community NGINX Ingress to F5 NGINX Ingress Controller on AKS]]></title>
            <link>https://medium.com/@mano.panneer94/migrating-from-community-nginx-ingress-to-f5-nginx-ingress-controller-on-aks-0e1432b30524?source=rss-d9ce48bdb465------2</link>
            <guid isPermaLink="false">https://medium.com/p/0e1432b30524</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[ingress]]></category>
            <category><![CDATA[azure-kubernetes-service]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[f5]]></category>
            <dc:creator><![CDATA[Manokaran]]></dc:creator>
            <pubDate>Sat, 19 Sep 2026 20:57:52 GMT</pubDate>
            <atom:updated>2026-09-19T20:59:55.068Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi Good Day,</p><p>I am sharing my experience on migrating from the community NGINX to the F5 NGINX Ingress Controller in the AKS. This Article give some idea on migrating to f5 ingress what are the steps need to be followed.</p><p>Why i migrated from community ingress to the F5 Ingress???</p><p>Kubernetes retired the community nginx support on March this year that means no further releases, no bug fixes, no feature updates, no security patches and also compliance risks on the Production environments.<br><a href="https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/">https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/</a></p><p>To avoid the Trouble in more evolving environment we started looking for the alternative for the community nginx. After Evaluating the Options we decided to migrate to the F5 ingress controller because of the smooth migration pathway due to the configuration familiarity and dedicated backing support.</p><p>What F5 Nginx ingress offers:</p><ul><li>Native support for NGINX App Protect (WAF)</li><li>Advanced traffic management (rate limiting, circuit breaking,traffic splitting for canary deployments)</li><li>Provides Deep observability.</li><li>Support for TransportServer and VirtualServer CRDs.</li><li>Active-active and active-passive HA configurations.</li><li>Support seamless loadbalancing across different protocols.</li></ul><p>1. Audit your Current setup.<br>Understand your current setup and try to get all the configuration which is running currently for migration.</p><pre># Check current ingress controller<br>kubectl get pods -n ingress-nginx<br><br># List all ingress resources<br>kubectl get ingress -A<br><br># Check current ingress class<br>kubectl get ingressclass<br><br># Export all ingress configs<br>kubectl get ingress -A -o yaml &gt; ingress-backup.yaml<br><br># Check annotations used<br>kubectl get ingress -A \<br>  -o jsonpath=&#39;{range .items[*]}{.metadata.name}{&quot;\t&quot;}{.metadata.annotations}{&quot;\n&quot;}{end}&#39;</pre><p>2. Installing the F5 Ingress Controller.<br><em>“Key to the Zero Downtime During migration is running both Controllers Simultaneously with Different Ingress Classes”</em></p><p>Before Downloading the F5 Ingress try to update or pull the Latest Helm version to your working machine.</p><p>There are Two Options You can get the F5 Ingress added.</p><p>Option A: Install Direclty From the OCI Registry.</p><pre><br>helm version<br><br>helm install f5-nginx oci://ghcr.io/nginx/charts/nginx-ingress \<br>  --version 2.7.3 \<br>  --namespace f5-nginx \<br>  --create-namespace \<br>  --set controller.ingressClass=f5-nginx \<br>  --set controller.ingressClassResource.name=f5-nginx \<br>  --set controller.ingressClassResource.setAsDefaultIngress=false \<br>  --set controller.service.type=LoadBalancer \<br>  --set prometheus.create=true</pre><p>Option B: Install From Source</p><pre># Pull the chart first<br>helm pull oci://ghcr.io/nginx/charts/nginx-ingress \<br>  --untar \<br>  --version 2.7.3<br><br># Change into the chart directory<br>cd nginx-ingress<br><br># Install from local source<br>helm install f5-nginx . \<br>  --namespace f5-nginx \<br>  --create-namespace \<br>  --set controller.ingressClass=f5-nginx \<br>  --set controller.ingressClassResource.name=f5-nginx \<br>  --set controller.ingressClassResource.setAsDefaultIngress=false \<br>  --set controller.service.type=LoadBalancer</pre><p>Verify its running:</p><pre>kubectl get pods -n f5-nginx<br>kubectl get svc -n f5-nginx<br>kubectl get ingressclass</pre><p>3. Understanding the difference.<br>This is the most critical part in the migration. Community ingress and F5 Ingress uses different Class Names and Annotation, should be carefull on migrating these annotations.</p><p>some common annotations types:</p><pre>Community NGINX Annotation                          F5 NGINX Equivalent<br>--------------------------------------------------------------------<br>nginx.ingress.kubernetes.io/rewrite-target          nginx.org/rewrites<br>nginx.ingress.kubernetes.io/ssl-redirect            nginx.org/redirect-to-https<br>nginx.ingress.kubernetes.io/proxy-body-size         nginx.org/client-max-body-size<br>nginx.ingress.kubernetes.io/proxy-connect-timeout   nginx.org/proxy-connect-timeout<br>nginx.ingress.kubernetes.io/proxy-read-timeout      nginx.org/proxy-read-timeout<br>nginx.ingress.kubernetes.io/rate-limit              nginx.org/limit-req-rate<br>nginx.ingress.kubernetes.io/use-regex               Use VirtualServer CRD instead<br>nginx.ingress.kubernetes.io/backend-protocol        nginx.org/grpc-services</pre><p>4. Simple Ingress ClassName and Annotation migration.<br>Here is some examples for the simple ingress classname update and the Annotation migration.</p><p>Community Nginx:</p><pre>apiVersion: networking.k8s.io/v1<br>kind: Ingress<br>metadata:<br>  name: my-app<br>  annotations:<br>    nginx.ingress.kubernetes.io/rewrite-target: /<br>    nginx.ingress.kubernetes.io/ssl-redirect: &quot;true&quot;<br>    nginx.ingress.kubernetes.io/proxy-body-size: &quot;10m&quot;<br>spec:<br>  ingressClassName: nginx<br>  rules:<br>    - host: myapp.example.com<br>      http:<br>        paths:<br>          - path: /<br>            pathType: Prefix<br>            backend:<br>              service:<br>                name: my-app-svc<br>                port:<br>                  number: 80<br>  tls:<br>    - hosts:<br>        - myapp.example.com<br>      secretName: myapp-tls</pre><p>After(F5 Nginx)</p><pre>apiVersion: networking.k8s.io/v1<br>kind: Ingress<br>metadata:<br>  name: my-app<br>  annotations:<br>    nginx.org/redirect-to-https: &quot;true&quot;<br>    nginx.org/client-max-body-size: &quot;10m&quot;<br>spec:<br>  ingressClassName: f5-nginx<br>  rules:<br>    - host: myapp.example.com<br>      http:<br>        paths:<br>          - path: /<br>            pathType: Prefix<br>            backend:<br>              service:<br>                name: my-app-svc<br>                port:<br>                  number: 80<br>  tls:<br>    - hosts:<br>        - myapp.example.com<br>      secretName: myapp-tls</pre><p>5. Advanced Migration:</p><p>What if your path has the regex mapping and sharing the same hostname with the Multiple Paths to solve this F5 ingress offers the Native CRD’s.</p><p>Kubernetes Ingress supports only two paths:</p><pre>Exact — Matches only that exact path. Example: /api/v1/users matches nothing else.<br><br>Prefix — Matches anything starting with it. Example: /api/ is too broad.</pre><p>No regex. So if you want to match /api/v1/users, /api/v2/users, /api/v3/users with one rule, the spec gives you no way to do it cleanly.<br>For this Community Nginx Uses the regex Annotation:</p><pre>annotations:<br>  nginx.ingress.kubernetes.io/use-regex: &quot;true&quot;<br>spec:<br>  rules:<br>    - host: app.example.com<br>      http:<br>        paths:<br>          - path: /api/v[0-9]+/users<br>            pathType: ImplementationSpecific<br>            backend:<br>              service:<br>                name: api-service<br>                port:<br>                  number: 8080</pre><p>But in the F5 Ingress its supported by using the CRD’s which is used by the Virtual Server.</p><pre>apiVersion: k8s.nginx.org/v1<br>kind: VirtualServer<br>metadata:<br>  name: api-routing<br>  namespace: production<br>spec:<br>  host: app.example.com<br><br>  # Two upstreams only — static and health were removed as their routes are no longer needed<br>  upstreams:<br><br>    # Handles all versioned API routes: /api/v1/users, /api/v1/orders, /api/v1/products<br>    - name: api<br>      service: api-service<br>      port: 8080<br><br>    # Handles login only — exact path /login, no other auth endpoints<br>    - name: auth<br>      service: auth-service<br>      port: 8081<br><br>  routes:<br><br>    # ── /login — exact match, no regex (~) needed ─────────<br>    # Plain path match is stricter — /login/anything will NOT match<br>    - path: /login<br>      action:<br>        proxy:<br>          upstream: auth<br>          requestHeaders:<br>            set:<br>              # Tell the backend the original request came over HTTPS<br>              - name: X-Forwarded-Proto<br>                value: https<br>              # Pass the real client IP, since NGINX sits in front<br>              - name: X-Real-IP<br>                value: ${nginx.remoteAddress}<br>          responseHeaders:<br>            # Strip Set-Cookie from auth response before sending to client<br>            hide:<br>              - Set-Cookie<br>            # Flag to identify this response came through the auth service<br>            add:<br>              - name: X-Auth-Service<br>                value: &quot;true&quot;<br><br>    # ── /api/v[0-9]+/users — regex match ─────────────────<br>    # ~ prefix enables regex; [0-9]+ matches any version number (v1, v2, v3...)<br>    # (/.*)?  makes the subpath optional — matches /users and /users/42<br>    - path: ~/api/v[0-9]+/users(/.*)?$<br>      action:<br>        proxy:<br>          upstream: api<br>          requestHeaders:<br>            set:<br>              - name: X-Forwarded-Proto<br>                value: https<br>              - name: X-Real-IP<br>                value: ${nginx.remoteAddress}<br>              # Unique ID per request — useful for tracing logs across services<br>              - name: X-Request-ID<br>                value: ${nginx.requestId}<br>          responseHeaders:<br>            add:<br>              # Informs the client which API version served the response<br>              - name: X-API-Version<br>                value: &quot;v1&quot;<br><br>    # ── /api/v[0-9]+/orders — same regex pattern as users ─<br>    # Separated from users intentionally — allows independent config later<br>    - path: ~/api/v[0-9]+/orders(/.*)?$<br>      action:<br>        proxy:<br>          upstream: api<br>          requestHeaders:<br>            set:<br>              - name: X-Forwarded-Proto<br>                value: https<br>              - name: X-Real-IP<br>                value: ${nginx.remoteAddress}<br>              - name: X-Request-ID<br>                value: ${nginx.requestId}<br>          responseHeaders:<br>            add:<br>              - name: X-API-Version<br>                value: &quot;v1&quot;<br><br>    # ── /api/v[0-9]+/products — same regex pattern ────────<br>    # No X-API-Version header here — products endpoint does not need version tagging<br>    - path: ~/api/v[0-9]+/products(/.*)?$<br>      action:<br>        proxy:<br>          upstream: api<br>          requestHeaders:<br>            set:<br>              - name: X-Forwarded-Proto<br>                value: https<br>              - name: X-Real-IP<br>                value: ${nginx.remoteAddress}<br>              - name: X-Request-ID<br>                value: ${nginx.requestId}</pre><p>After Applying the Virtual Server it has to Show the configurations as Valid.</p><pre>Kubectl get virtualserver -n &lt;Namesapce name&gt;</pre><p><a href="https://docs.nginx.com/nginx-ingress-controller/configuration/virtualserver-and-virtualserverroute-resources/">https://docs.nginx.com/nginx-ingress-controller/configuration/virtualserver-and-virtualserverroute-resources/</a></p><p>Once you done all the configuration cut down your standard community ingress from DNS and Update the F5 Ingress IP to the DNS to cut down the downtime.</p><p>And Thats it!!!!! Happy Learning…….</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0e1432b30524" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kubernetes Observability using the Grafana Loki, Promtail and Grafana Dashboard using Helm in the…]]></title>
            <link>https://medium.com/@mano.panneer94/kubernetes-observability-using-the-grafana-loki-promtail-and-grafana-dashboard-using-helm-in-the-f4b86259cb91?source=rss-d9ce48bdb465------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4b86259cb91</guid>
            <category><![CDATA[azure-kubernetes-service]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[grafana-loki]]></category>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Manokaran]]></dc:creator>
            <pubDate>Sat, 24 Aug 2024 09:06:15 GMT</pubDate>
            <atom:updated>2024-08-24T09:06:15.980Z</atom:updated>
            <content:encoded><![CDATA[<h3>Kubernetes Observability using the Grafana Loki, Promtail and Grafana Dashboard using Helm in the AKS cluster.</h3><p><strong>Introduction:<br></strong>Hi, If you are a container enthusiastic you will be in need of the observability to troubleshoot the container. Here I am writing this article to know about the Grafana Loki installation on the AKS Cluster and How i configured to use it for the observability.</p><p><strong>Grafana Loki:</strong><br>Mostly all are familiar with the Prometheus and Grafana for the metrics monitoring tool for the Container based deployments where we can continuously monitor the spikes on the k8 cluster and when comes to troubleshooting we need to collect and get deeper on the logs echoed by the container. To achieve this Loki comes in handy for the log aggregation side.<br>Loki is Horizontally Scalable, Multi-Tenant log aggregation system which was developed based on the Prometheus solution. The key highlighted part is it indexes a set of labels for each log stream instead of the log contents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8JJPxy1aM-zsB5J3RW62iQ.png" /><figcaption>https://grafana.com/oss/loki/</figcaption></figure><p><strong>Loki Architecture:<br></strong>Loki Based Logging-Stack is made up of three component.<br>1. Agent- An agent or client, such as Grafana Promtail (which comes with Loki), scrapes logs, converts them into streams by adding labels, and sends the streams to Loki via an HTTP API.<br>2. Loki- Loki handles the storage of our logs. It indexes only the labels and metadata for each message, allowing for efficient filtering and searching. Loki gathers and delivers log data.<br>3. Grafana- Grafana is used for querying and displaying log data. Additionally, you can query logs from the command line using LogCLI or directly through the Loki API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fWS9z3SUxf8aNu3C_RDkBQ.png" /></figure><p><strong>Loki Deployment Modes:</strong></p><ol><li>Simple Scalable: The simple scalable deployment mode is ideal for most Loki installations, balancing monolithic and microservice modes. It allows independent scaling of read, write, and backend targets, supporting up to a few TBs of logs per day. Its is the recommended way of installation in the Helm.</li><li>Monolithic Mode: Monolithic deployment mode is the simplest for Loki, running all components in a single process as a single binary or Docker image. It’s suitable for up to 20GB/day and can scale horizontally with a shared object store. For larger scales, simple scalable mode is recommended. High availability is achieved with multiple instances, memberlist_config, and a shared object store, with traffic routed in a round-robin fashion.</li><li>Microservices Mode: Microservices deployment mode runs Loki components as distinct processes, each with a specific target. This allows for granular scaling of each component to better match your use case. While more efficient, it is complex to set up and maintain, recommended for large clusters or precise control. Designed for Kubernetes, a community-supported Helm chart is available for deployment, making it suitable for very large Loki installations.</li></ol><blockquote><a href="https://grafana.com/docs/loki/latest/get-started/deployment-modes/">https://grafana.com/docs/loki/latest/get-started/deployment-modes/</a></blockquote><p><strong>Loki Installation:<br></strong>There are several methods on installing the loki:</p><ul><li>Install Helm (recommended)</li><li>Install using Tanaka</li><li>Install using Docker or Docker Compose</li><li>Install and run locally</li><li>Install from source</li></ul><p><strong>Installing the Scalable Loki using Helm:</strong></p><ol><li>Pre-requsites:</li></ol><ul><li>Running AKS Cluster</li><li>Helm Binaries</li></ul><p>2. Loki Helm:</p><p>This chart sets up Loki to operate read, write, and backend targets in a scalable manner. Loki’s straightforward scalable deployment mode divides execution paths into read, write, and backend targets.</p><p>The Helm method deploy the following components.</p><ul><li>Read component (3 replicas)</li><li>Write component (3 replicas)</li><li>Backend component (3 replicas)</li><li>Loki Canary (1 DaemonSet)</li><li>Gateway (1 NGINX replica)</li><li>Minio (Optional)</li></ul><p>Adding the Grafana chart repo to the Helm</p><pre>helm repo add grafana https://grafana.github.io/helm-charts</pre><p>Updating the Chart Repository</p><pre>helm repo update</pre><p>To pull the repo to local</p><pre>helm pull grafana/loki-stack</pre><p>To list the updated helm repo</p><pre>helm search repo loki</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/770/1*TJs19v6Cd8oRAt_cBu5_fg.png" /></figure><p>To get the values files to update the configuration for the Helm loki.</p><pre>helm show values grafana/loki-stack &gt; loki-stack-values.yaml</pre><p>The default values files you can get from the loki helm</p><pre>test_pod:<br>  enabled: true<br>  image: bats/bats:1.8.2<br>  pullPolicy: IfNotPresent<br> <br>loki:<br>  enabled: true<br>  isDefault: true<br>  url: http://{{(include &quot;loki.serviceName&quot; .)}}:{{ .Values.loki.service.port }}<br>  readinessProbe:<br>    httpGet:<br>      path: /ready<br>      port: http-metrics<br>    initialDelaySeconds: 45<br>  livenessProbe:<br>    httpGet:<br>      path: /ready<br>      port: http-metrics<br>    initialDelaySeconds: 45<br>  datasource:<br>    jsonData: &quot;{}&quot;<br>    uid: &quot;&quot;<br> <br> <br>promtail:<br>  enabled: true<br>  config:<br>    logLevel: info<br>    serverPort: 3101<br>    clients:<br>      - url: http://{{ .Release.Name }}:3100/loki/api/v1/push<br> <br>fluent-bit:<br>  enabled: false<br> <br>grafana:<br>  enabled: false<br>  sidecar:<br>    datasources:<br>      label: &quot;&quot;<br>      labelValue: &quot;&quot;<br>      enabled: true<br>      maxLines: 1000<br>  image:<br>    tag: 10.3.3<br> <br>prometheus:<br>  enabled: false<br>  isDefault: false<br>  url: http://{{ include &quot;prometheus.fullname&quot; .}}:{{ .Values.prometheus.server.service.servicePort }}{{ .Values.prometheus.server.prefixURL }}<br>  datasource:<br>    jsonData: &quot;{}&quot;<br> <br>filebeat:<br>  enabled: false<br>  filebeatConfig:<br>    filebeat.yml: |<br>      # logging.level: debug<br>      filebeat.inputs:<br>      - type: container<br>        paths:<br>          - /var/log/containers/*.log<br>        processors:<br>        - add_kubernetes_metadata:<br>            host: ${NODE_NAME}<br>            matchers:<br>            - logs_path:<br>                logs_path: &quot;/var/log/containers/&quot;<br>      output.logstash:<br>        hosts: [&quot;logstash-loki:5044&quot;]<br> <br>logstash:<br>  enabled: false<br>  image: grafana/logstash-output-loki<br>  imageTag: 1.0.1<br>  filters:<br>    main: |-<br>      filter {<br>        if [kubernetes] {<br>          mutate {<br>            add_field =&gt; {<br>              &quot;container_name&quot; =&gt; &quot;%{[kubernetes][container][name]}&quot;<br>              &quot;namespace&quot; =&gt; &quot;%{[kubernetes][namespace]}&quot;<br>              &quot;pod&quot; =&gt; &quot;%{[kubernetes][pod][name]}&quot;<br>            }<br>            replace =&gt; { &quot;host&quot; =&gt; &quot;%{[kubernetes][node][name]}&quot;}<br>          }<br>        }<br>        mutate {<br>          remove_field =&gt; [&quot;tags&quot;]<br>        }<br>      }<br>  outputs:<br>    main: |-<br>      output {<br>        loki {<br>          url =&gt; &quot;http://loki:3100/loki/api/v1/push&quot;<br>          #username =&gt; &quot;test&quot;<br>          #password =&gt; &quot;test&quot;<br>        }<br>        # stdout { codec =&gt; rubydebug }<br>      }<br> <br># proxy is currently only used by loki test pod<br># Note: If http_proxy/https_proxy are set, then no_proxy should include the<br># loki service name, so that tests are able to communicate with the loki<br># service.<br>proxy:<br>  http_proxy: &quot;&quot;<br>  https_proxy: &quot;&quot;<br>  no_proxy: &quot;&quot;</pre><p>We can enable or remove the not needed values from the values file. For my use case i removed the Fluentbit, Filebeat, Prometheus and logstash.</p><pre>loki:<br>  enabled: true<br>  isDefault: true<br>  url: http://{{(include &quot;loki.serviceName&quot; .)}}:{{ .Values.loki.service.port }}<br>  readinessProbe:<br>    httpGet:<br>      path: /ready<br>      port: http-metrics<br>    initialDelaySeconds: 45<br>  livenessProbe:<br>    httpGet:<br>      path: /ready<br>      port: http-metrics<br>    initialDelaySeconds: 45<br>  datasource:<br>    jsonData: &quot;{}&quot;<br>    uid: &quot;&quot;<br> <br> <br>promtail:<br>  enabled: true<br>  config:<br>    logLevel: info<br>    serverPort: 3101<br>    clients:<br>      - url: http://{{ .Release.Name }}:3100/loki/api/v1/push<br> <br>fluent-bit:<br>  enabled: false<br> <br>grafana:<br>  enabled: true<br>  sidecar:<br>    datasources:<br>      label: &quot;&quot;<br>      labelValue: &quot;&quot;<br>      enabled: true<br>      maxLines: 1000<br>  image:<br>    tag: 10.3.3</pre><blockquote><a href="https://grafana.com/docs/loki/latest/setup/install/helm/install-scalable/">https://grafana.com/docs/loki/latest/setup/install/helm/install-scalable/</a></blockquote><p><strong>Object Storage Configuration for Azure:</strong><br>Loki uses the TSDB mode to persist the data for the indexing the more efficient querying of the log data. The below is the configuration I used for the azure object storage.</p><pre>schemaConfig:<br>    configs:<br>      - from: 2024-04-01<br>        store: tsdb<br>        object_store: azure<br>        schema: v13<br>        index:<br>          prefix: loki_index_<br>          period: 24h<br>  ingester:<br>    chunk_encoding: snappy<br>  tracing:<br>    enabled: true<br>  querier:<br>    max_concurrent: 4<br>  storage:<br>    type: azure<br>    azure:<br>      accountName: &lt;storage account name&gt;<br>      accountKey: &lt;storage account key&gt;<br>    bucketNames:<br>      chunks: chunks<br>      ruler: ruler<br>      admin: admin<br>deploymentMode: SimpleScalable<br>backend:<br>  replicas: 3<br>  persistance:<br>    storageClass: azurefile-csi<br>    size: 1Gi<br>read:<br>  replicas: 2<br>  persistance:<br>    storageClass: azurefile-csi<br>    size: 1Gi<br>write:<br>  replicas: 2<br>  persistance:<br>    storageClass: azurefile-csi<br>    size: 1Gi<br>minio:<br>  enabled: false<br>singleBinary:<br>  replicas: 0<br>ingester:<br>  replicas: 0<br>querier:<br>  replicas: 0<br>queryFrontend:<br>  replicas: 0<br>queryScheduler:<br>  replicas: 0<br>distributor:<br>  replicas: 0<br>compactor:<br>  replicas: 0<br>indexGateway:<br>  replicas: 0<br>bloomCompactor:<br>  replicas: 0<br>bloomGateway:<br>  replicas: 0</pre><blockquote><a href="https://grafana.com/docs/loki/latest/configure/storage/">https://grafana.com/docs/loki/latest/configure/storage/</a></blockquote><p>Install the Loki on the aks cluster</p><pre>helm install grafana loki-stack-2.10.2/loki-stack -f .\loki-stack-values.yaml -n loki</pre><p><strong>Checking the Deployment in the AKS cluster:</strong></p><p>Connect the AKS cluster using the Az command</p><pre>az aks get-credentials --resource-group &lt;resource group name&gt; --name &lt;cluster name&gt; --overwrite-existing</pre><p>To list the loki deployment on the AKS cluster deployed.</p><pre>kubectl get pod -n &lt;loki deployment ns&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/1*CXUMDG5_DrmjvATrAoNHuw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*zXqZry4ieGdV_jwYR5__uw.png" /></figure><p>You can see that grafana service is running on the cluster ip, you can either create a ingress for the cluster ip and access it through the ingress reverse proxy or you can do the port forward to the localhost and access it on the machine itself. I verified the grafana Dashboard by doing the port forward.</p><pre>kubectl -n loki port-forward svc/grafana 3000:80</pre><blockquote>If you have any problems, delete any pods stuck in the terminating state with (this can happen when you uninstall and reinstall or update Loki)</blockquote><p>The dashboard look like this</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T_f83vpkgWo4rKrQ97a7uA.png" /></figure><p>Check the data source connectivity to from under the data source connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FhzmY3ga2DVGdH_-iL_lwg.png" /></figure><p>By using the Query filter out the labels needed to get the logs from the loki.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mlfIRDSDxD3vuBpRgJyZoQ.png" /></figure><p>And Thanks!! Happy Learning✌🏼</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4b86259cb91" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Registering the K8s Pod Running in the AKS Cluster for the Agent Pools in AZDO.]]></title>
            <link>https://medium.com/@mano.panneer94/registering-the-k8s-pod-running-in-the-aks-cluster-for-the-agent-pools-in-azdo-e02d90c9640a?source=rss-d9ce48bdb465------2</link>
            <guid isPermaLink="false">https://medium.com/p/e02d90c9640a</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[azure-kubernetes-service]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[devops-practice]]></category>
            <dc:creator><![CDATA[Manokaran]]></dc:creator>
            <pubDate>Wed, 15 May 2024 15:38:18 GMT</pubDate>
            <atom:updated>2024-05-15T15:38:18.080Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introduction:</strong></p><p>Azure DevOps (AzDO) serves as a robust Continuous Integration and Continuous Deployment (CI/CD) platform, enabling effective DevOps practices for software releases. Within AzDO, you have the option to utilize either Microsoft-hosted agents or self-hosted agents. In this discussion, our focus lies on self-hosted agents, which allow seamless integration into AzDO pipelines that we create and manage independently. Typically, self-hosted agents operate within virtual machines (VMs) during the build and release phases. In this article, we’ll delve into the process of leveraging Docker containers running on an Azure Kubernetes Service (AKS) cluster to register as agents within the agent pool.</p><p><strong>Pre-requisites:</strong></p><ol><li>Personal Access Token(PAT)</li><li>Agent Pool created in the Azure DevOps.</li><li>AKS(Azure Kubernetes Cluster)</li></ol><p>In this article we will see how to Register the Windows Docker container and Linux Docker Container running on the Azure Kubernetes Service to register in the Agent Pool in Azure DevOps.</p><p><strong>Creating the Windows Container Agent:<br></strong>Create and Build Docker File</p><ol><li>Open Command Prompt or Powershell.</li><li>Create a New Directory.</li></ol><pre>mkdir &quot;C:\azp-agent-in-docker\&quot;</pre><p>3. Go on to the Directory.</p><pre>cd &quot;C:\azp-agent-in-docker\&quot;</pre><p>4. Create a Dockerfile with the following commands and save as “C:\azp-agent-in-docker\azp-agent-windows.dockerfile”</p><pre>FROM mcr.microsoft.com/windows/servercore:ltsc2022<br><br>WORKDIR /azp/<br><br>COPY ./start.ps1 ./<br><br>CMD powershell .\start.ps1</pre><p>5. Create a Powershell script called “C:\azp-agent-in-docker\start.ps1&quot;</p><pre>function Print-Header ($header) {<br>  Write-Host &quot;`n${header}`n&quot; -ForegroundColor Cyan<br>}<br><br>if (-not (Test-Path Env:AZP_URL)) {<br>  Write-Error &quot;error: missing AZP_URL environment variable&quot;<br>  exit 1<br>}<br><br>if (-not (Test-Path Env:AZP_TOKEN_FILE)) {<br>  if (-not (Test-Path Env:AZP_TOKEN)) {<br>    Write-Error &quot;error: missing AZP_TOKEN environment variable&quot;<br>    exit 1<br>  }<br><br>$Env:AZP_TOKEN_FILE = &quot;\azp\.token&quot;<br>  $Env:AZP_TOKEN | Out-File -FilePath $Env:AZP_TOKEN_FILE<br>}<br><br>Remove-Item Env:AZP_TOKEN<br><br>if ((Test-Path Env:AZP_WORK) -and -not (Test-Path $Env:AZP_WORK)) {<br>  New-Item $Env:AZP_WORK -ItemType directory | Out-Null<br>}<br><br>New-Item &quot;\azp\agent&quot; -ItemType directory | Out-Null<br><br># Let the agent ignore the token env variables<br>$Env:VSO_AGENT_IGNORE = &quot;AZP_TOKEN,AZP_TOKEN_FILE&quot;<br><br>Set-Location agent<br><br>Print-Header &quot;1. Determining matching Azure Pipelines agent...&quot;<br><br>$base64AuthInfo = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes(&quot;:$(Get-Content ${Env:AZP_TOKEN_FILE})&quot;))<br>$package = Invoke-RestMethod -Headers @{Authorization=(&quot;Basic $base64AuthInfo&quot;)} &quot;$(${Env:AZP_URL})/_apis/distributedtask/packages/agent?platform=win-x64&amp;`$top=1&quot;<br>$packageUrl = $package[0].Value.downloadUrl<br><br>Write-Host $packageUrl<br><br>Print-Header &quot;2. Downloading and installing Azure Pipelines agent...&quot;<br><br>$wc = New-Object System.Net.WebClient<br>$wc.DownloadFile($packageUrl, &quot;$(Get-Location)\agent.zip&quot;)<br><br>Expand-Archive -Path &quot;agent.zip&quot; -DestinationPath &quot;\azp\agent&quot;<br><br>try {<br>  Print-Header &quot;3. Configuring Azure Pipelines agent...&quot;<br><br>.\config.cmd --unattended --agent &quot;$(if (Test-Path Env:AZP_AGENT_NAME) { ${Env:AZP_AGENT_NAME} } else { hostname })&quot; --url &quot;$(${Env:AZP_URL})&quot; --auth PAT --token &quot;$(Get-Content ${Env:AZP_TOKEN_FILE})&quot; --pool &quot;$(if (Test-Path Env:AZP_POOL) { ${Env:AZP_POOL} } else { &#39;Default&#39; })&quot; --work &quot;$(if (Test-Path Env:AZP_WORK) { ${Env:AZP_WORK} } else { &#39;_work&#39; })&quot; --replace<br><br>Print-Header &quot;4. Running Azure Pipelines agent...&quot;<br><br>.\run.cmd<br>} finally {<br>  Print-Header &quot;Cleanup. Removing Azure Pipelines agent...&quot;<br><br>.\config.cmd remove --unattended --auth PAT --token &quot;$(Get-Content ${Env:AZP_TOKEN_FILE})&quot;<br>}</pre><p>This Script used to configure the agent with the AgentPool name, PAT Token and Organization URL for registering the agent with the AgentPool.</p><p>6. To Run the Docker file Run the below Command:</p><pre>docker build --tag &quot;azp-agent:windows&quot; --file &quot;./azp-agent-windows.dockerfile&quot; .</pre><p>Docker image is tagged as azp-agent:windows</p><p><strong>Creating the Linux Container Agent:</strong></p><ol><li>Open the Terminal.</li><li>Create a New Directory.</li></ol><pre>mkdir ~/azp-agent-in-docker/</pre><p>3. Cd into the Dir.</p><pre>cd ~/azp-agent-in-docker/</pre><p>4. Create a Dockerfile Under the Path.</p><pre>FROM ubuntu:22.04<br><br>RUN apt update -y &amp;&amp; apt upgrade -y &amp;&amp; apt install curl git jq libicu70 -y<br><br># Also can be &quot;linux-arm&quot;, &quot;linux-arm64&quot;.<br>ENV TARGETARCH=&quot;linux-x64&quot;<br><br>WORKDIR /azp/<br><br>COPY ./start.sh ./<br>RUN chmod +x ./start.sh<br><br># Create agent user and set up home directory<br>RUN useradd -m -d /home/agent agent<br>RUN chown -R agent:agent /azp /home/agent<br><br>USER agent<br># Another option is to run the agent as root.<br># ENV AGENT_ALLOW_RUNASROOT=&quot;true&quot;<br><br>ENTRYPOINT [ &quot;./start.sh&quot; ]</pre><p>Uncomment the ENV AGENT_ALLOW_RUNASROOT=&quot;true&quot; line and remove adding the agent user before this line if you want to run the agent as root.</p><p>5. Save the following content to ~/azp-agent-in-docker/start.sh</p><pre>#!/bin/bash<br>set -e<br><br>if [ -z &quot;${AZP_URL}&quot; ]; then<br>  echo 1&gt;&amp;2 &quot;error: missing AZP_URL environment variable&quot;<br>  exit 1<br>fi<br><br>if [ -z &quot;${AZP_TOKEN_FILE}&quot; ]; then<br>  if [ -z &quot;${AZP_TOKEN}&quot; ]; then<br>    echo 1&gt;&amp;2 &quot;error: missing AZP_TOKEN environment variable&quot;<br>    exit 1<br>  fi<br><br>  AZP_TOKEN_FILE=&quot;/azp/.token&quot;<br>  echo -n &quot;${AZP_TOKEN}&quot; &gt; &quot;${AZP_TOKEN_FILE}&quot;<br>fi<br><br>unset AZP_TOKEN<br><br>if [ -n &quot;${AZP_WORK}&quot; ]; then<br>  mkdir -p &quot;${AZP_WORK}&quot;<br>fi<br><br>cleanup() {<br>  trap &quot;&quot; EXIT<br><br>  if [ -e ./config.sh ]; then<br>    print_header &quot;Cleanup. Removing Azure Pipelines agent...&quot;<br><br>    # If the agent has some running jobs, the configuration removal process will fail.<br>    # So, give it some time to finish the job.<br>    while true; do<br>      ./config.sh remove --unattended --auth &quot;PAT&quot; --token $(cat &quot;${AZP_TOKEN_FILE}&quot;) &amp;&amp; break<br><br>      echo &quot;Retrying in 30 seconds...&quot;<br>      sleep 30<br>    done<br>  fi<br>}<br><br>print_header() {<br>  lightcyan=&quot;\033[1;36m&quot;<br>  nocolor=&quot;\033[0m&quot;<br>  echo -e &quot;\n${lightcyan}$1${nocolor}\n&quot;<br>}<br><br># Let the agent ignore the token env variables<br>export VSO_AGENT_IGNORE=&quot;AZP_TOKEN,AZP_TOKEN_FILE&quot;<br><br>print_header &quot;1. Determining matching Azure Pipelines agent...&quot;<br><br>AZP_AGENT_PACKAGES=$(curl -LsS \<br>    -u user:$(cat &quot;${AZP_TOKEN_FILE}&quot;) \<br>    -H &quot;Accept:application/json;&quot; \<br>    &quot;${AZP_URL}/_apis/distributedtask/packages/agent?platform=${TARGETARCH}&amp;top=1&quot;)<br><br>AZP_AGENT_PACKAGE_LATEST_URL=$(echo &quot;${AZP_AGENT_PACKAGES}&quot; | jq -r &quot;.value[0].downloadUrl&quot;)<br><br>if [ -z &quot;${AZP_AGENT_PACKAGE_LATEST_URL}&quot; -o &quot;${AZP_AGENT_PACKAGE_LATEST_URL}&quot; == &quot;null&quot; ]; then<br>  echo 1&gt;&amp;2 &quot;error: could not determine a matching Azure Pipelines agent&quot;<br>  echo 1&gt;&amp;2 &quot;check that account &quot;${AZP_URL}&quot; is correct and the token is valid for that account&quot;<br>  exit 1<br>fi<br><br>print_header &quot;2. Downloading and extracting Azure Pipelines agent...&quot;<br><br>curl -LsS &quot;${AZP_AGENT_PACKAGE_LATEST_URL}&quot; | tar -xz &amp; wait $!<br><br>source ./env.sh<br><br>trap &quot;cleanup; exit 0&quot; EXIT<br>trap &quot;cleanup; exit 130&quot; INT<br>trap &quot;cleanup; exit 143&quot; TERM<br><br>print_header &quot;3. Configuring Azure Pipelines agent...&quot;<br><br>./config.sh --unattended \<br>  --agent &quot;${AZP_AGENT_NAME:-$(hostname)}&quot; \<br>  --url &quot;${AZP_URL}&quot; \<br>  --auth &quot;PAT&quot; \<br>  --token $(cat &quot;${AZP_TOKEN_FILE}&quot;) \<br>  --pool &quot;${AZP_POOL:-Default}&quot; \<br>  --work &quot;${AZP_WORK:-_work}&quot; \<br>  --replace \<br>  --acceptTeeEula &amp; wait $!<br><br>print_header &quot;4. Running Azure Pipelines agent...&quot;<br><br>chmod +x ./run.sh<br><br># To be aware of TERM and INT signals call ./run.sh<br># Running it with the --once flag at the end will shut down the agent after the build is executed<br>./run.sh &quot;$@&quot; &amp; wait $!</pre><p>6. Run the following command in the directory to build the docker file.</p><pre>docker build --tag &quot;azp-agent:linux&quot; --file &quot;./azp-agent-linux.dockerfile&quot; .</pre><p>The image is tagged as “azp-agent:linux”</p><p><strong>Environment Variables:</strong></p><pre>AZP_URL - The Url of Azure DevOps<br>AZP_TOKEN - Personal Access Token<br>AZP_AGENT_NAME - Agent Name for the agent(Default:Contianer Host name)<br>AZP_POOL - Name of the Agent Pool where agent needs to ne registered<br>AZP_WORK - Work Directory on the Agent (Default _work)</pre><p>You can extend the Dockerfile to include additional tools and their dependencies, or build your own container by using this one as a base layer. Just make sure that the following are left untouched:</p><ul><li>The start.sh script is called by the Dockerfile.</li><li>The start.sh script is the last command in the Dockerfile.</li></ul><p><strong>Azure Container Registry:<br></strong>Certainly! After building and tagging the Docker image with the appropriate name, you can push it to the Azure Container Registry (ACR) that you’ve already set up. If you need guidance on configuring a new ACR, refer to the provided documentation.</p><p><a href="https://learn.microsoft.com/en-us/azure/container-registry/container-registry-get-started-portal?tabs=azure-cli">Quickstart - Create Registry in Portal - Azure Container Registry</a></p><p>Run This Command to push the docker to the container Registry.</p><pre>docker push &quot;&lt;acr-server&gt;/azp-agent:&lt;tag&gt;&quot;</pre><p><strong>Deploy the Container On the Azure Kubernetes Service(AKS):</strong></p><p>Once the Image pushed to the ACR we can use the below steps to deploy it to the Azure Kubernetes Cluster.</p><ol><li>Create the Namespace in the AKS.</li><li>Create the Secret on the AKS Cluster using the below command:</li></ol><pre>kubectl create secret generic azdevops \<br>  --from-literal=AZP_URL=https://dev.azure.com/yourOrg \<br>  --from-literal=AZP_TOKEN=YourPAT \<br>  --from-literal=AZP_POOL=NameOfYourPool</pre><p>3. Create the Deployment.yaml file to deploy on the AKS.</p><pre>apiVersion: apps/v1<br>kind: Deployment<br>metadata:<br>  name: azdevops-deployment<br>  labels:<br>    app: azdevops-agent<br>spec:<br>  replicas: 1 # here is the configuration for the actual agent always running<br>  selector:<br>    matchLabels:<br>      app: azdevops-agent<br>  template:<br>    metadata:<br>      labels:<br>        app: azdevops-agent<br>    spec:<br>      containers:<br>      - name: kubepodcreation<br>        image: &lt;acr-server&gt;/azp-agent:&lt;tag&gt;<br>        env:<br>          - name: AZP_URL<br>            valueFrom:<br>              secretKeyRef:<br>                name: azdevops<br>                key: AZP_URL<br>          - name: AZP_TOKEN<br>            valueFrom:<br>              secretKeyRef:<br>                name: azdevops<br>                key: AZP_TOKEN<br>          - name: AZP_POOL<br>            valueFrom:<br>              secretKeyRef:<br>                name: azdevops<br>                key: AZP_POOL<br>        volumeMounts:<br>        - mountPath: /var/run/docker.sock<br>          name: docker-volume<br>      volumes:<br>      - name: docker-volume<br>        hostPath:<br>          path: /var/run/docker.sock</pre><p>4. Use this command to Deploy on the AKS</p><pre>kubectl apply -f deployment.yml</pre><p>You can use the Persistent Volumes on the Kubernetes to mount the volumes to the containers.</p><blockquote><strong>Reference Links:<br></strong><a href="https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/docker?view=azure-devops">https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/docker?view=azure-devops</a></blockquote><p><strong>Summary:</strong><br>Certainly! The article emphasizes the utilization of Docker containers within Agent Pools for various processes such as build, deployment, and automated test execution. However, it’s essential to recognize that the suitability of this approach depends entirely on the specific project requirements and context.</p><p>Thank You!!😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e02d90c9640a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Installing the Docker Engine from binaries and the MiniKube.]]></title>
            <link>https://medium.com/@mano.panneer94/installing-the-docker-engine-from-binaries-and-the-minikube-1c2b0e5bc92c?source=rss-d9ce48bdb465------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c2b0e5bc92c</guid>
            <category><![CDATA[devops-practice]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[devops-tool]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Manokaran]]></dc:creator>
            <pubDate>Sat, 23 Mar 2024 10:34:51 GMT</pubDate>
            <atom:updated>2024-03-23T10:34:51.157Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Introduction:</strong><br>Kubernetes becomes a widely used Orchestration Platform, which enable the developers to manage the Containerized Application workloads. To use and Explore the Kubernetes locally on the windows machine, Minikube provides that feasibility. Minikube allows you run the single node cluster on the machine to make the hands dirty on the k8.</p><p><strong>Pre-requisites:</strong><br>Here are some of the pre-requisites for running the Minikube.</p><ol><li>Machine with the Windows Operating system with 2CPU or More, 2GB of Free Memory, 20GB of Free Disk Space.</li><li>You need a Container or Virtual Machine manager (<a href="https://minikube.sigs.k8s.io/docs/drivers/docker/">Docker</a>, <a href="https://minikube.sigs.k8s.io/docs/drivers/qemu/">QEMU</a>, <a href="https://minikube.sigs.k8s.io/docs/drivers/hyperkit/">Hyperkit</a>, <a href="https://minikube.sigs.k8s.io/docs/drivers/hyperv/">Hyper-V</a>, <a href="https://minikube.sigs.k8s.io/docs/drivers/kvm2/">KVM</a>, <a href="https://minikube.sigs.k8s.io/docs/drivers/parallels/">Parallels</a>, <a href="https://minikube.sigs.k8s.io/docs/drivers/podman/">Podman</a>, <a href="https://minikube.sigs.k8s.io/docs/drivers/virtualbox/">VirtualBox</a>, or <a href="https://minikube.sigs.k8s.io/docs/drivers/vmware/">VMware Fusion/Workstation</a>) to run the minikube.</li><li>You need a kubectl command line tool to interact with the minikube cluster. you can download and install using the chocolatey package manager.</li></ol><p>In this step-by-step tutorial you will see the process of setting up the minikube on the windows machine using the Docker engine installed using the docker binaries.</p><p><strong>Installing the Docker engine using the Docker Binaries:</strong></p><ol><li>Download the static binary archive. Go to <a href="https://download.docker.com/win/static/stable/x86_64">https://download.docker.com/win/static/stable/x86_64</a> and select the latest version from the list.</li><li>Run the Powershell on the Admin Mode and run the below powershell commands:</li></ol><pre>PS C:\&gt; Expand-Archive /path/to/&lt;FILE&gt;.zip -DestinationPath $Env:ProgramFiles</pre><p>3. Register the service and start the docker engine.</p><pre>PS C:\&gt; &amp;$Env:ProgramFiles\Docker\dockerd --register-service<br>PS C:\&gt; Start-Service docker</pre><p>4. Check the docker installation by pulling the nginx image using the docker command.</p><pre>PS C:\&gt; &amp;$Env:ProgramFiles\Docker\docker run nginx</pre><p>5. To upgrade the static binaries of the docker engine, stop the dockerd or dockerd.exe process, then follow the regular installation process to upgrade the version.</p><blockquote>Attached the docker documentation for the reference</blockquote><blockquote><a href="https://docs.docker.com/engine/install/binaries/#install-server-and-client-binaries-on-windows">https://docs.docker.com/engine/install/binaries/#install-server-and-client-binaries-on-windows</a></blockquote><p><strong>Installing the Minikube on the Windows Machine.</strong></p><ol><li>Open the PowerShell on the Admin mode and run the command.</li></ol><pre>New-Item -Path &#39;c:\&#39; -Name &#39;minikube&#39; -ItemType Directory -Force<br>Invoke-WebRequest -OutFile &#39;c:\minikube\minikube.exe&#39; -Uri &#39;https://github.com/kubernetes/minikube/releases/latest/download/minikube-windows-amd64.exe&#39; -UseBasicParsing</pre><p>2. Add the minikube.exe to your PATH.</p><pre>$oldPath = [Environment]::GetEnvironmentVariable(&#39;Path&#39;, [EnvironmentVariableTarget]::Machine)<br>if ($oldPath.Split(&#39;;&#39;) -inotcontains &#39;C:\minikube&#39;){<br>  [Environment]::SetEnvironmentVariable(&#39;Path&#39;, $(&#39;{0};C:\minikube&#39; -f $oldPath), [EnvironmentVariableTarget]::Machine)<br>}</pre><p>3. After the installation close the PowerShell and reopen it to before running minikube.</p><p>4. Start the Cluster using the command.</p><pre>minikube start</pre><p>5. Interact with the minikube using the kubectl commands.</p><pre>minikube kubectl get ns<br>minikube kubectl get pods</pre><blockquote>you can also create alias for the commands which makes your life easier</blockquote><p>6. To stop and delete the minikube cluster use.</p><pre>minikube stop<br>minikube delete --all</pre><blockquote>Added the link for the more details and more minikube cluster management.</blockquote><blockquote><a href="https://minikube.sigs.k8s.io/docs/start/">https://minikube.sigs.k8s.io/docs/start/</a></blockquote><p>Thank You!!!😊</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c2b0e5bc92c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting the Windows Node up and running in the EKS cluster.]]></title>
            <link>https://medium.com/@mano.panneer94/getting-the-windows-node-up-and-running-in-the-eks-cluster-124181b499bb?source=rss-d9ce48bdb465------2</link>
            <guid isPermaLink="false">https://medium.com/p/124181b499bb</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[aws-eks]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[information-technology]]></category>
            <dc:creator><![CDATA[Manokaran]]></dc:creator>
            <pubDate>Sun, 11 Feb 2024 16:04:53 GMT</pubDate>
            <atom:updated>2024-02-11T16:04:53.398Z</atom:updated>
            <content:encoded><![CDATA[<p>I am writing this post to explain the issues I Faced while creating the windows node in the EKS and Adding the EBS CSI DRIVER as an add-ons. In this page i will add the error and the solution i followed to fix the issue.</p><blockquote>Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox : plugin type=”vpc-bridge” name=”vpc” failed (add): failed to parse Kubernetes args: failed to get pod IP address ebs-csi-node-windows: error executing k8s connector: error executing connector binary: exit status 1 with execution error: pod ebs-csi-node-windows does not have label vpc.amazonaws.com/PrivateIPv4Address.</blockquote><p>“For reading/understanding the article, You will need a prerequisite of a General knowledge on the EKS cluster, Kubectl objects and Kubectl”</p><p>Document You can refer from AWS:<br><a href="https://docs.aws.amazon.com/eks/latest/userguide/windows-support.html#enable-windows-support">https://docs.aws.amazon.com/eks/latest/userguide/windows-support.html#enable-windows-support</a></p><p>Solution:<br>Make sure the proper version is updated for the cluster and the EBSCSI DRIVER, in my case the cluster version is in — 1.28 and EBSCSI version is in — 1.27.0-eksbuild.1</p><p>Create the IAM Role for the EBSCSI DRIVER by following the below document.<a href="https://docs.aws.amazon.com/eks/latest/userguide/csi-iam-role.html"><br>https://docs.aws.amazon.com/eks/latest/userguide/csi-iam-role.html</a></p><p>In the Cluster IAM Role attach the <a href="https://us-east-1.console.aws.amazon.com/iam/home?region=us-east-1#/policies/details/arn%3Aaws%3Aiam%3A%3Aaws%3Apolicy%2FAmazonEKSVPCResourceController">AmazonEKSVPCResourceController</a>.</p><p>Connect to the cluster using the kubectl command and get the list of all pods running in the Kube-system namespace.</p><p>Once you added the EBS addon in the cluster you can see a Deamonset in the Kube-system Namespace <em>“daemonset.apps/ebs-csi-node-windows”</em></p><p>By using the Command kubectl edit daemonset.apps/ebs-csi-node-windows -n kube-system add the annotation on the yaml file <em>“vpc.amazonaws.com/PrivateIPv4Address: “True” ”</em></p><p>Create a yaml file called <em>vpc-resource-controller-configmap.yaml to enable the IP Address Management for the windows node in the Cluster.</em></p><pre>apiVersion: v1<br>kind: ConfigMap<br>metadata:<br>  name: amazon-vpc-cni<br>  namespace: kube-system<br>data:<br>  enable-windows-ipam: &quot;true&quot;</pre><p>Use the command <em>kubectl apply -f vpc-resource-controller-configmap.yaml -n kube-system </em>to apply the configmap to the cluster.</p><p>Once the config map is appplied to the cluster use the “kubectl get all -n kube-system command” Then restart the deamon set for the EBSCSI driver.<br><em>“kubectl rollout restart daemonset.apps/ebs-csi-node-windows -n kube-system”</em></p><p>Once its restared you can see the ebs-csi-driver is created on the windows node as a deamonset to support the ebs driver mapping for the pods.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/906/1*XZIz3ziJ4sQqYOa70kgBCg.png" /></figure><p>And Voilà</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=124181b499bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>