DEV Community: Chinenye Genevieve Onyema

From Zero to a Working EKS Pipeline: Terraform, Ansible, and GitLab CI/CD (and Everything That Broke Along the Way)

Chinenye Genevieve Onyema — Thu, 16 Jul 2026 12:32:38 +0000

From Zero to a Working EKS Pipeline: Terraform, Ansible, and GitLab CI/CD (and Everything That Broke Along the Way)

I recently built an end-to-end deployment pipeline on AWS EKS using Terraform for infrastructure, Ansible for configuration, and GitLab CI/CD to tie it all together. On paper, that sentence sounds clean. In practice, it took several rounds of "why is this failing" before it actually worked.

This post is not a "here's how EKS works" tutorial. There are plenty of those. This is the version with the failures left in, the quota limits, the IAM permission walls, the pods that wouldn't schedule, and the resources that refused to die. If you're building something similar, I'm hoping this saves you a few hours of confused Googling.

Repo: gitlab.com/nenyeonyema/terraform-eks-ansible-cicd

What I Was Building

The goal was a full IaC-driven pipeline:

Terraform to provision the EKS cluster and supporting AWS infrastructure (VPC, node groups, IAM roles)
Ansible to handle configuration tasks on top of the provisioned infrastructure
GitLab CI/CD to automate the whole thing — plan, apply, configure, deploy — on every push

Simple enough in theory. Four separate blockers said otherwise.

Blocker #1: Free Tier ASG Restrictions

The first wall I hit was with the Auto Scaling Group for my EKS node group. AWS Free Tier limits how much compute you can provision, and my initial node group sizing quietly ran into those limits — the kind of failure that doesn't always throw an obvious, single-line error.

Fix: I resized the node group to stay within Free Tier boundaries and got explicit about instance types and desired/min/max capacity in Terraform, instead of leaving Auto Scaling to make assumptions I couldn't afford.

Lesson: If you're building on Free Tier, hardcode your capacity expectations early. Don't let the defaults surprise you later.

Blocker #2: EKS Private Endpoint Access

By default, EKS clusters can be configured with private-only API server endpoint access. That's great for security, less great when your CI/CD runner or local machine suddenly can't reach the cluster to run kubectl commands.

Fix: I had to explicitly configure endpoint access (public, private, or both, depending on where the access was coming from) in the Terraform EKS module configuration, rather than relying on defaults.

Lesson: Decide your access model on purpose, not by accident. "It won't connect" is often a networking/endpoint configuration issue before it's anything else.

Blocker #3: The IAM Access Entry API

This one cost the most time. Managing who (which IAM roles/users) can access the EKS cluster used to be handled through the aws-auth ConfigMap. AWS has since introduced the Access Entry API as the newer approach to cluster access management, and the two don't always play nicely if you're mixing old tutorials with new AWS provider versions.

Fix: I moved to using the Access Entry API directly through Terraform's EKS resources instead of manually patching aws-auth, which meant re-reading provider documentation carefully since a lot of existing tutorials online still reference the older ConfigMap-based method.

Lesson: When Terraform provider behavior doesn't match a tutorial, check the provider version and changelog before assuming you made a mistake. AWS and the community are actively moving away from aws-auth.

Blocker #4: t3.micro Pod Limits

Even after the cluster came up, deployments started failing to schedule. The problem wasn't compute, it was pod density. Instance types like t3.micro have a maximum number of pods they can run based on their networking capacity (ENI/IP limits), not just CPU/RAM.

Fix: I scaled from a single-node setup to multiple nodes, spreading pods across more machines instead of trying to force everything onto one small instance.

Lesson: "Not enough compute" and "not enough pod slots" look identical from the outside. If pods are stuck in Pending and your node has CPU/memory to spare, check max-pods-per-node before you check anything else.

Blocker #5: Orphaned ELBs Blocking `terraform destroy`

The most frustrating one. After deploying a Kubernetes LoadBalancer service, Kubernetes provisions an AWS ELB behind the scenes — but Terraform doesn't know about it, because it wasn't the one that created it. Result: running terraform destroy would hang or fail, because AWS wouldn't let Terraform tear down the VPC/subnets while an orphaned ELB was still attached to them.

Fix: Before running terraform destroy, I had to manually delete any Kubernetes-created LoadBalancer services first (kubectl delete svc <service-name>), which triggers AWS to clean up the associated ELB. Only then would terraform destroy complete cleanly.

Lesson: Anything Kubernetes provisions on your behalf (LoadBalancers, EBS volumes via PVCs) lives outside Terraform's state. Always tear down Kubernetes-managed cloud resources before tearing down the infrastructure underneath them.

What I'd Do Differently Next Time

Pin provider versions early. Several of these issues came from AWS's EKS access model evolving faster than the tutorials I was learning from.
Build a teardown checklist, not just a build checklist. terraform destroy needs its own runbook when Kubernetes is in the mix.
Size for pod density, not just compute. I'll check max-pods-per-instance-type before picking an instance size going forward.

Why This Matters

None of these blockers are exotic. They're the ordinary friction of running Terraform, Ansible, and Kubernetes together in a real AWS account — which is exactly why I think they're worth writing down. The polished tutorials rarely mention them, but if you're doing this hands-on, you will hit at least one of these five.

If you're working through something similar, or you've hit a different version of one of these walls, I'd love to hear about it — drop a comment or reach out.

Repo: gitlab.com/nenyeonyema/terraform-eks-ansible-cicd

How Linux Awakens: What Happens When You Press the Power Button.

Chinenye Genevieve Onyema — Mon, 05 May 2025 22:08:19 +0000

Understanding the Linux Boot Process from Power-On to Login.

Have you ever wondered what happens when you click the power button on your Linux system? When you press the power button on your Linux system, a complex sequence of events occurs in milliseconds, bringing your system to life. Whether you're a Linux System Administrator, DevOps engineer, Site Reliability engineer, or a Linux enthusiast, understanding the Linux boot process helps you to troubleshoot issues, optimize performance, and appreciate the inner workings of your system.

Here is a Simplified Overview of What Happens behind the scenes:

1. BIOS/UEFI Initialization (Firmware Stage)

What it does:
When you press the power button, the motherboard's system firmware (BIOS for older systems and UEFI for newer ones) kicks in.

Key Tasks:

Performs a diagnostic test known as POST(Power-On Self Test) to check hardware components such as RAM, CPU, storage devices, and peripherals.
Detects and initializes boot devices(SSD, HDD, USB, etc)
Once the hardware is verified, the firmware hands over control to the bootloader stored on the primary boot device.

Important fact: UEFI is replacing BIOS because it's faster, supports larger drivers (over 2TB), and has a graphical user interface.

2. BOOTLOADER Execution

What it does:
The firmware searches for the bootloader on the storage device and loads it into memory.
The Bootloader is a small program that loads the Linux kernel into memory. The most common Bootloader is GRUB(Grand Unified Bootloader).
Key Tasks:

GRUB presents a boot menu to select the OS/Kernel options or automatically load the default Linux kernel.
Loads the selected Linux kernel and initramfs/initrd into memory.
Passes control to the kernel.

Initramfs/initrd: A temporary filesystem used by the kernel to access necessary drivers before the real root filesystem is mounted.

3. KERNEL Loading

What it does:
The Linux Kernel is now in control of the system
Key Tasks:

Hardware Detection: The Kernel detects and initializes the hardware via built-in or loaded drivers(CPU, memory, I/O).
Mounts the root file/system.
Starts the first user space program, usually /sbin/init or systems

The Kernel also:

Manages memory
Sets up process scheduling
Initializes networking and system calls.

4. Init/Systemd Starts

This is the first user-space process with process ID 1.

What it does:
The Kernel starts the init process (traditionally, but in modern Linux distros, use systemd). It orchestrates the rest of the boot process.

Key Tasks:

Reads its initial configurations from /etc/systemd and /etc/initab in older systems.
Mounts the remaining file system. (eg,/home, /boot)
Runs startup scripts/services to prepare the system, such as starting network services and setting up the graphical environment.

5. User-space Login(TTY or GUI)

Once all services are up, the system presents you with a login interface.

A TTY login prompt(text based) for servers or minimal systems.
Graphical Login manager (like GDM, lightDM, SDDM) for desktop environment.

After a successful authentication, the login session starts.

For TTY login a shell (eg, bash) is launched allowing a command-line interractions.
For GUI a desktop environment or windows manager is started, providing a graphical interface for user-interactions. This process signifies the transition of kernel system services to user-level interactions.

Conclusion

In essence, pressing the power button triggers a chain of hardware checks, loads the kernel, sets up the system service, and finally presents you with a usable desktop environment. Despite its complexity, this seamless process ensures your Linux system is ready almost instantly after you power it on.

Unlocking The Power Of Linux: A Beginner's Guide to the Tech Giant's Favorite Operating System.

Chinenye Genevieve Onyema — Fri, 25 Apr 2025 15:57:10 +0000

Introduction: What Is Linux and Why Does It Matter?

In the past, most people used commercial Operating Systems like Windows or MacOS. These Systems are popular, but they come with some downsides, such as needing to pay for licenses, limitations on customization, and potential security issues.

Now, picture an operating system(OS) that's completely free, allows you to change and adapt the source code to your computing needs.
That's LINUX! A powerful platform embraced by tech giants and enthusiasts alike. It was built by Linus Torvalds in 1991 to give people control, flexibility, and freedom.

In this article, we'll explore the fundamentals of Linux, the different distributions(distros) available, how Linux is structured under the hood, how the package managers install software's and how its unique folder hierarchy makes it ideal for everything from smartphones to supercomputers. Let's dive in!

The Open Source Nature of Linux

When we say Linux is open source, we mean:

Free to use: This means anyone can download, install, and use it without paying for the license.
Customization: Users can modify the source code, which means that if you want to change how your operating system works, you can do so without any legal issues.
Community Support: Linux benefits from a large community that contributes to its development, ensuring it remains secure and up-to-date without the need for a costly license.

The Structure of Linux: A Well-Organized System.

Why Structure Matters
Just like peeling an onion, layer by layer. Like a well-organized office, Linux has a clear structure that makes it easy to find and manage files

Here are the key components of the Linux Operating System:

🧠The Kernel: The Brain of the OS.

At the core of the Linux system lies the Kernel, a program that connects your computer hardware to its software. Think of the Kernel as the traffic controller, directing communication between your hardware (CPU, memory, processes, and hard drives) and the software applications that you use.

Why The Kernel?

Without the Kernel, your application couldn't talk to your CPU, memory, or storage. The kernel distributes resources needed to perform a task. The Kernel schedules processes, manages memory and network interfaces, allocates file systems, and provides inter-process communication.

2.The Shell: The Command-Line Interface

The Shell sits right above the Kernel, It's what you interact with when you open the terminal. It interprets your commands(ls, cd, etc) and passes them to the Kernel for execution.

Why Shell?
The Shell gives you direct control of the system, letting you automate, customize, and troubleshoot like a pro. The Shell acts as an interface between the user and the kernel.

3.System Libraries and Utilities: Your System Toolkit

Linux comes with hundreds of tiny programs(often called Utilities) that perform specific tasks, like managing files, monitoring processes, and configuring networks. These Libraries and Utilities are a collection of functions or pre-written code and tools that help software applications operate smoothly.

Why The Libraries and Utilities ?
By using these libraries, developers can save time and effort, as they don't need to write the same code repeatedly. The system libraries act as an interface between the system applications and the kernel.

4.File System: The Organized Foundation
The Linux filesystem is organized in a tree-like structure. Every file, folder, and even hardware is treated as a file, with the root(/) directory at the top of the hierarchy. The organizational structure of the file system is crucial for easy navigation and file management.

The Key directories:

Why File Systems?
As a Linux administrator or root user, understanding the structure of the file system matters. It enables you to manage system files, configure settings, and troubleshoot issues efficiently. Knowing where everything is helps maintain system health and security.

Exploring Linux Distributions: Why Variety is Key.

What is a Distribution?

A Linux Distribution(distro) is a packaged version of the operating system that includes the kernel, libraries, utilities, and user interface. Think of it as a specific flavor of Linux tailored for different needs and preferences.

Popular Distributions: Choose Your Flavor

Ubuntu: Perfect for beginners and the most popular distros, known for its user-friendly interface. Built from the Debian family.
CentOS: A favorite in the world of servers, praised for its stability and security. Belongs to the family of Red Hat.
Debian: One of the oldest and most popular distros, known for its commitment to free software, stability, and reliability.
Red Hat Enterprise Linux (RHEL): Widely used by enterprises and businesses for its robust and reliable operating system. Known for its stability, security, and performance.
Fedora: Sponsored by Red Hat, ideal for developers who want the latest software features in a secure and stable environment.
Arch Linux: Ideal for advanced users who want complete control over their system and want to build from scratch. Offers the latest software updates.
Kali Linux: Built on Debian with high security, designed for network analysts and cybersecurity experts.
OpenSUSE: It has two kinds of releases. Perfect for users who want a reliable system with advanced configuration tools, along with the option to choose between a rolling release(Tumbleweed) and a stable release(Leap).

Having various distributions allows users to pick the one that best suits their needs, whether for everyday use, software development, or server management.

Package Managers: Simplifying Software Installation

What are Package Managers?
A Package Manager is a tool that makes installing and updating software as easy as clicking a button. It automatically handles downloading, installing, configuring software packages, updating, and removing software.
Popular Package Managers

apt(APT: Advanced Package Tool): Found in Debian and Ubuntu, it lets you install apps with simple commands like apt install <package-name>.
yum and dnf: Used for RHEL, CentOS, and Fedora. These command tools facilitate managing software on RPM-based systems.
pacman: The go-to package manager for Arch Linux users, known for its simplicity and speed.
zypper: The package manager for OpenSUSE, it's easy to use and consumes fewer resources.

Why Use Package Managers
Think of a package manager like an application store. Instead of searching various websites to find software, a package manager lets you search, install, and update applications from a single place. This saves time and minimizes errors.

Conclusion

Linux is not just an operating system; it's a powerful, community-driven tool that offers flexibility and security. Whether you're a user, developer, or administrator, understanding Linux fundamentals, structure, distributions, package managers, and folder organization will empower you to make the most out of your computing experience. So, why not try out a Linux distribution today? Join the community and explore the endless possibilities of Linux.

How to Setup A Simple Nginx Web Server on an Ubuntu GCP Virtual Machine.

Chinenye Genevieve Onyema — Fri, 31 Jan 2025 22:12:50 +0000

Introduction

I have always wanted to share my learning experiences and knowledge from my tasks and projects. In this article, as part of the HNG Internship program, I will provide a step-by-step guide on configuring a simple Nginx web server on a Google Compute Engine Ubuntu virtual machine.

Requirements

A Google Cloud account, if you don't have an account, Sign up. GCP is giving free $300 credits to new accounts.
Basic experience with Linux CLI.
Sign in to your Google Cloud console.

Steps on how to set up an Ubuntu Virtual Machine.

Step 1

Click on the three bars by the left side of the console.

Step 2

Click on Compute Engine and then clickon VM Instances

Step 3

Click on "Create" Instance.

Step 4: Machine Configuration settings

Give the instance any name of your choice.
Choose the region and zone nearest to you for your instance.
Choose the default General Purpose E2 machine for the task.

Step 5: Operating System and Storage

Continue the instance setup by clicking on OS and Storage.

Click "Change" in the Operating System configuration.

Change the OS image to Ubuntu and keep the remaining settings as default.
Click "Select".

Step 6: Networking

Choose Networking
For the firewalls, tick to allow HTTP and HTTPS traffic.
Click on "create" instance

Congratulations! You have successfully launched a Google Cloud Virtual Instance.

To SSH Into The Nginx Virtual Instance.

On the instance dashboard, Tick the instance and click on "SSH" A new window pops up.
Click "Authorize" to connect to the instance. And wait for SSH to connect to the instance successfully.

Good Job! You are now connected to your Instance Command Line interface.

How to Configure Nginx on Ubuntu Virtual Instance

Step 1: Run the command below to Update and Upgrade the Instance.
sudo apt update & sudo apt upgrade -y

Step 2: Install Nginx
sudo apt install nginx -y

Step 3: Start and Enable Nginx

sudo systemctl start nginx
sudo systemctl enable nginx

Step 4: Check if Nginx is actively running successfully
sudo systemctl status nginx

Step 5: Back up the Default Web Page

cd /var/www/html
sudo cp index.nginx-debian.html index.nginx-debian.html.bk

Step 6: Create a new file named index.html
touch index.html

Step 7: Move the content of the default page to the new file
sudo mv index.nginx-debian.html index.html

Step 8: Open the index.html file
sudo vi index.html

Step 9: Modify the content of index.html file to the code below

To edit the file, press the letter "i"

<!DOCTYPE html>
<html>
<head>
<title>HNG Stage 0 Nginx Web Server</title>
<style>
    body {
        width: 35em;
        margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif;
    }
</style>
</head>
<body>
<h4>Welcome to DevOps Stage 0 - [Your Name]/[SlackName] </h4>

</body>
</html>

After editing, press the escape key, colon, letters w and q. That is, ":wq"

Step 10: Restart Nginx
sudo systemctl restart nginx

Step 10: Copy the External Ip address and paste in your browser
34.89.121.56

Possible Challenges

One potential challenge you may face when accessing your webpage is related to networking. Ensure that the firewall is configured to allow inbound HTTP traffic, as the NGINX server listens on port 80 by default.

How This Task Contributed to My Learning

As someone with extensive experience using AWS Cloud, I wanted to enhance my multi-cloud skills by leveraging Google Cloud as my development environment for this task. Previously, I primarily accessed virtual instances by clicking the SSH option on the Google Cloud Console. However, during this task, I explored alternative methods of connecting to a GCP instance using PuTTY, Git Bash, and other SSH tools.

This was particularly exciting for me because, on AWS, I have always accessed EC2 instances by downloading and using the private key. Through this experience, I learned how to generate private and public key pairs using PuTTY, add the public key to the GCP instance's SSH configuration, and securely authenticate my connection.

In a forthcoming article, I will share a step-by-step guide on connecting to a GCP instance using third-party SSH tools and also generating keys through the command line.

Hire your skilled DevOps Engineers and Cloud Engineers here.

DEV Community: Chinenye Genevieve Onyema

From Zero to a Working EKS Pipeline: Terraform, Ansible, and GitLab CI/CD (and Everything That Broke Along the Way)

From Zero to a Working EKS Pipeline: Terraform, Ansible, and GitLab CI/CD (and Everything That Broke Along the Way)

What I Was Building

Blocker #1: Free Tier ASG Restrictions

Blocker #2: EKS Private Endpoint Access

Blocker #3: The IAM Access Entry API

Blocker #4: t3.micro Pod Limits

Blocker #5: Orphaned ELBs Blocking terraform destroy

What I'd Do Differently Next Time

Why This Matters

How Linux Awakens: What Happens When You Press the Power Button.

Understanding the Linux Boot Process from Power-On to Login.

1. BIOS/UEFI Initialization (Firmware Stage)

2. BOOTLOADER Execution

3. KERNEL Loading

4. Init/Systemd Starts

5. User-space Login(TTY or GUI)

Conclusion

Unlocking The Power Of Linux: A Beginner's Guide to the Tech Giant's Favorite Operating System.

Introduction: What Is Linux and Why Does It Matter?

The Open Source Nature of Linux

The Structure of Linux: A Well-Organized System.

Exploring Linux Distributions: Why Variety is Key.

Package Managers: Simplifying Software Installation

Conclusion

How to Setup A Simple Nginx Web Server on an Ubuntu GCP Virtual Machine.

Introduction

Requirements

Steps on how to set up an Ubuntu Virtual Machine.

To SSH Into The Nginx Virtual Instance.

How to Configure Nginx on Ubuntu Virtual Instance

Possible Challenges

How This Task Contributed to My Learning

Blocker #5: Orphaned ELBs Blocking `terraform destroy`