<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
  <channel>
    <atom:link href="https://varlogdiego.com/rss.xml" rel="self" type="application/rss+xml"/>
    <title>/var/log/diego</title>
    <link>https://varlogdiego.com</link>
    <description>My logs as DevOps Engineer. Technical blog with nerd stuff By Diego Najar.</description>
    <lastBuildDate>Sun, 08 Dec 2024 20:13:42 +0100</lastBuildDate>
    <item>
      <title>Kubernetes: Traefik and  service backend HTTPs and Self-signed certificate</title>
      <link>https://varlogdiego.com/kubernetes-traefik-service-backend-https-self-signed-certificate</link>
      <image/>
      <description>&lt;p&gt;How to set up Traefik running as ingress controller in Kubernet to forward requests to a Kubernetes service backend that uses the HTTPS protocol and self-signed certificate.&lt;/p&gt;
&lt;p&gt;References links&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://community.traefik.io/t/insecureskipverify-explanation/2195"&gt;https://community.traefik.io/t/insecureskipverify-explanation/2195&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://doc.traefik.io/traefik/routing/providers/kubernetes-ingress/"&gt;https://doc.traefik.io/traefik/routing/providers/kubernetes-ingress/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
      <pubDate>Thu, 15 Jun 2023 14:44:31 +0200</pubDate>
      <guid isPermaLink="false">2d64278cf395418311668b1b8925da9b</guid>
    </item>
    <item>
      <title>EKS: Your current user or role does not have access to Kubernetes objects on this EKS cluster.</title>
      <link>https://varlogdiego.com/eks-your-current-user-or-role-does-not-have-access-to-kubernetes</link>
      <image/>
      <description>&lt;p&gt;When you install EKS for the first time, you receive the following message in the AWS Console UI.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Your current user or role does not have access to Kubernetes objects on this EKS cluster.
This may be due to the current user or role not having Kubernetes RBAC permissions to describe cluster resources or not having an entry in the cluster’s auth config map.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This happen because your AWS user account doesn't have access to the Kubernetes control plane.&lt;/p&gt;
</description>
      <pubDate>Fri, 20 Aug 2021 15:48:42 +0200</pubDate>
      <guid isPermaLink="false">6476a67a8890cffe6e90dfca8ca4da41</guid>
    </item>
    <item>
      <title>Schedule pods to start and stop in Kubernetes by date and time</title>
      <link>https://varlogdiego.com/schedule-pods-to-start-and-stop-in-kubernetes-by-date-and-time</link>
      <image/>
      <description>&lt;p&gt;Kubernetes by default doesn't provide this feature but you can use &lt;a href="https://github.com/dignajar/another-autoscaler"&gt;Another Autoscaler&lt;/a&gt; controller for that.&lt;/p&gt;
&lt;p&gt;We are using this tool in my company to save some money on the Kubernetes clusters with GPU instances (P2 and G4DN); Developers using these types of instances generally use them during working hours, so we can terminate pods after working hours and our Cluster Autoscaler will scale-down instances that are idle.&lt;/p&gt;
&lt;p&gt;Another Autoscaler page: &lt;a href="https://github.com/dignajar/another-autoscaler"&gt;https://github.com/dignajar/another-autoscaler&lt;/a&gt;&lt;/p&gt;
</description>
      <pubDate>Thu, 24 Jun 2021 09:47:41 +0200</pubDate>
      <guid isPermaLink="false">94d5a6e5a97c65f3798516f2f9536b1a</guid>
    </item>
    <item>
      <title>Kubernetes and GPU nodes on AWS</title>
      <link>https://varlogdiego.com/kubernetes-and-gpu-nodes-on-aws</link>
      <image/>
      <description>&lt;p&gt;Time for GPU and Kubernetes, the idea is to provide an instance group with Kubernetes' nodes with GPU, also to save some money we can start the autoscaling group from 0 instances.&lt;/p&gt;
&lt;h2&gt;The environment&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;AWS&lt;/li&gt;
&lt;li&gt;&lt;a href="https://aws.amazon.com/ec2/instance-types/g4/"&gt;G4DN instances&lt;/a&gt; also tested on &lt;a href="https://aws.amazon.com/ec2/instance-types/p2/"&gt;P2 instances&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Kubernetes 1.18 deployed via Kops&lt;/li&gt;
&lt;li&gt;Cluster Autoscaler 1.18&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/getting-started.html"&gt;GPU Operator&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</description>
      <pubDate>Mon, 26 Apr 2021 18:01:09 +0200</pubDate>
      <guid isPermaLink="false">0353eab0edd26649ce97f91f31a671a7</guid>
    </item>
    <item>
      <title>Kubernetes: AWS Load Balancer Controller (ALB Ingress controller) and cross namespaces</title>
      <link>https://varlogdiego.com/kubernetes-aws-load-balancer-controller-cross-namespaces</link>
      <image/>
      <description>&lt;p&gt;Assuming you have deployed &lt;a href="https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/"&gt;AWS Load Balancer Controller&lt;/a&gt;, the following steps are how to configure one ALB to expose all your services, also services cross namespaces.&lt;/p&gt;
&lt;p&gt;Default configuration for the ALB &amp;quot;dev&amp;quot; with the following features:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;HTTP redirect to HTTPs.&lt;/li&gt;
&lt;li&gt;SSL termination, with ACM certificate provide from AWS.&lt;/li&gt;
&lt;/ul&gt;
</description>
      <pubDate>Fri, 12 Feb 2021 16:28:53 +0100</pubDate>
      <guid isPermaLink="false">dbac22d78d3f34fced319e3d1e60b0e7</guid>
    </item>
  </channel>
</rss>
