Nahuel Hernandez

EndeavourOS Linux I3 Setup

EndeavourOS is another Arch Linux based distribution. All worked out of the box and the installation was straightforward. On the other hand, EOS comes with an I3 setup option. I3 is a dynamic tiling window you can do everything using your keyboard, perfect for #productivity and to have a minimalist and very fast environment.

January 31, 2022

4-Minute Read

I installed Endeavors using the installer from the live environment with encryption on the disk, swapping for hibernating with a few clicks, and so on. EOS + I3 is an excellent combination, after testing Manjaro, Arch, Debian, and Fedora. I feel confortable with this setup. In brief EOS + I3 is an excellent combination to have an amazing environment to use every day.

Karpenter Kubernetes Node Autoscaling

K8S Autoscaling helps us to scale out or in our applications. Pod-based scaling or HPA is an excellent first step. However, the problem is when we need more K8S nodes to contain our PODs. Karpenter is a Node-based scaling solution built for K8S, and its goal is to improve efficiency and cost. It is a great solution because we don't need to configure instances types or create nodegroups, which drastically simplifies configuration. On the other hand, the integration with Spot instances is painless and we can reduce our costs (up to 90% cheaper than On-Demand instances)

January 24, 2022

8-Minute Read

A Kubernetes node autoscaling solution is a tool that automatically adjusts the size of the Kubernetes cluster based on the demands of our workloads. Because of this, we don’t need to create manually a new Kubernetes Node every time we need it (or delete it). Karpenter automatically provisions new nodes in response to unschedulable pods. It does this by observing events within the Kubernetes cluster, and then sending commands to the underlying cloud provider. It is designed to work with…

Ingress Controller and External DNS with Route53 on EKS

One great way to expose Kubernetes Applications to the world is using Ingress resources. On EKS we can avoid creating one Load Balancer each time we expose an Application. Moreover, K8S Ingress offers a single entry point to the cluster. So we can save money, manage and monitor one Load Balancer and reduce the attack surface of the Cluster. This is great, however, every time we need to expose an application we will need to create and manage DNS records manually. We can set externalDNS by adding a simple annotation to our ingress resources pointing to the DNS record and then it will be created automatically on Route53. In conclusion, using Ingress resources and ExternalDNS allows us to save time, money and improve security.

January 17, 2022

9-Minute Read

Normally when we expose an application on EKS we use a LoadBalancer service to expose the application, the problem with this is every time we create a new LoadBalancer service, AWS will create a new ELB. Ingress controllers on EKS allow us to use one ELB and configure the application access using Kubernetes resources.