Part 3: The Controller Ecosystem — Helm, Ingress, and Observability

📰 Medium · DevOps

Learn to utilize EKS Blueprints Addons to deploy Controllers for Helm, Ingress, and Observability in an EKS cluster, enhancing its functionality and management

intermediate Published 28 Apr 2026

Action Steps

Utilize the eks_blueprints_addons module to install addons on an EKS cluster
Deploy Controllers for Helm, Ingress, and Observability using EKS Blueprints Addons
Configure the EKS cluster to collect performance metrics and update DNS records automatically
Integrate the EKS cluster with AWS Application Load Balancer for enhanced load balancing and scalability
Use EKS Blueprints Addons to manage and modularize the deployment of various tools and services in the EKS cluster

Who Needs to Know This

DevOps engineers and cloud architects can benefit from this knowledge to improve the management and scalability of their EKS clusters, ensuring seamless integration with various tools and services

Key Insight

💡 EKS Blueprints Addons provides a community-vetted, modular framework for deploying Controllers and managing EKS clusters, reducing the need for custom code and enhancing scalability

Key Takeaways

Learn to utilize EKS Blueprints Addons to deploy Controllers for Helm, Ingress, and Observability in an EKS cluster, enhancing its functionality and management

Full Article

Title: Part 3: The Controller Ecosystem — Helm, Ingress, and Observability

URL Source: https://medium.com/@mbilalayyoob/part-3-the-controller-ecosystem-helm-ingress-and-observability-e3899c4a24ca?source=rss------devops-5

Published Time: 2026-04-28T18:52:42Z

Markdown Content:
# Part 3: The Controller Ecosystem — Helm, Ingress, and Observability | by M Bilal | Apr, 2026 | Medium

[Sitemap](https://medium.com/sitemap/sitemap.xml)

[Open in app](https://play.google.com/store/apps/details?id=com.medium.reader&referrer=utm_source%3DmobileNavBar&source=post_page---top_nav_layout_nav-----------------------------------------)

Sign up

[Sign in](https://medium.com/m/signin?operation=login&redirect=https%3A%2F%2Fmedium.com%2F%40mbilalayyoob%2Fpart-3-the-controller-ecosystem-helm-ingress-and-observability-e3899c4a24ca&source=post_page---top_nav_layout_nav-----------------------global_nav------------------)

[](https://medium.com/?source=post_page---top_nav_layout_nav-----------------------------------------)

Get app

[Write](https://medium.com/m/signin?operation=register&redirect=https%3A%2F%2Fmedium.com%2Fnew-story&source=---top_nav_layout_nav-----------------------new_post_topnav------------------)

[Search](https://medium.com/search?source=post_page---top_nav_layout_nav-----------------------------------------)

Sign up

[Sign in](https://medium.com/m/signin?operation=login&redirect=https%3A%2F%2Fmedium.com%2F%40mbilalayyoob%2Fpart-3-the-controller-ecosystem-helm-ingress-and-observability-e3899c4a24ca&source=post_page---top_nav_layout_nav-----------------------global_nav------------------)

![Image 1](https://miro.medium.com/v2/resize:fill:32:32/1*dmbNkD5D-u45r44go_cf0g.png)

# Part 3: The Controller Ecosystem — Helm, Ingress, and Observability

[![Image 2: M Bilal](https://miro.medium.com/v2/resize:fill:32:32/0*TjkQ8W0jvzOHQ6nX.jpg)](https://medium.com/@mbilalayyoob?source=post_page---byline--e3899c4a24ca---------------------------------------)

[M Bilal](https://medium.com/@mbilalayyoob?source=post_page---byline--e3899c4a24ca---------------------------------------)

Follow

6 min read

·

2 hours ago

[](https://medium.com/m/signin?actionUrl=https%3A%2F%2Fmedium.com%2F_%2Fvote%2Fp%2Fe3899c4a24ca&operation=register&redirect=https%3A%2F%2Fmedium.com%2F%40mbilalayyoob%2Fpart-3-the-controller-ecosystem-helm-ingress-and-observability-e3899c4a24ca&user=M+Bilal&userId=54f9aec490cf&source=---header_actions--e3899c4a24ca---------------------clap_footer------------------)

36

[](https://medium.com/m/signin?actionUrl=https%3A%2F%2Fmedium.com%2F_%2Fbookmark%2Fp%2Fe3899c4a24ca&operation=register&redirect=https%3A%2F%2Fmedium.com%2F%40mbilalayyoob%2Fpart-3-the-controller-ecosystem-helm-ingress-and-observability-e3899c4a24ca&source=---header_actions--e3899c4a24ca---------------------bookmark_footer------------------)

[Listen](https://medium.com/m/signin?actionUrl=https%3A%2F%2Fmedium.com%2Fplans%3Fdimension%3Dpost_audio_button%26postId%3De3899c4a24ca&operation=register&redirect=https%3A%2F%2Fmedium.com%2F%40mbilalayyoob%2Fpart-3-the-controller-ecosystem-helm-ingress-and-observability-e3899c4a24ca&source=---header_actions--e3899c4a24ca---------------------post_audio_button------------------)

Share

Press enter or click to view image in full size

![Image 3](https://miro.medium.com/v2/resize:fit:700/1*ZC0ra6gKIUwLBw6U_2oZrw.jpeg)

Utilizing eks_blueprints_addons module to install addons on cluster

In the previous parts, we built the “Land” (VPC) and the “Brain” (EKS). Now, we need to build the “Gateway.” By default, an EKS cluster is isolated. It doesn’t know how to talk to an AWS Application Load Balancer, it doesn’t collect performance metrics, and it won’t automatically update your DNS records. To solve this, we deploy Controllers.

### The Power of EKS Blueprints

Instead of writing thousands of lines of custom code for every tool, we utilize **EKS Blueprints Addons**. This is a community-vetted, modular framework that allows us to manag

Read full article → ← Back to Reads

Part 3: The Controller Ecosystem — Helm, Ingress, and Observability

Key Takeaways

Full Article

Related Videos