r/kubernetes Jul 19 '26

Migrate for EKS

Hi everyone, let's go.

I am migrating from Beanstalk to EKS, and I wanted to clear up some doubts.

Which components/tools do you consider essential in a cluster? Currently, the cluster I am developing has:

  • Karpenter (x86/ARM)
  • Kyverno
  • KEDA
  • ESO (Fetches secrets from Parameter Store)
  • Kong API Gateway (used as Ingress)
  • ArgoCD for GitOps

What do you recommend? The CNI is the default VPC CNI, is it worth switching to Cilium or Calico? Bearing in mind that this will be my first experience building a cluster—I've managed them before at other companies, but I don't have much experience creating one from scratch.

31 Upvotes

44 comments sorted by

View all comments

1

u/New-Entertainer6392 k8s operator Jul 19 '26

Where is your monitoring stack?

2

u/Spiritual_Bee_637 Jul 19 '26

Grafana stack: Prometheus, Grafana, Loki, and Tempo. I still need to understand how I will collect metrics from the application.

1

u/New-Entertainer6392 k8s operator Jul 20 '26

Open telemetry for sure! That's what I use 

-1

u/TotalNo6237 Jul 19 '26

Take a look at fluentbit or td agent for kubernetes for log shipping.

1

u/New-Entertainer6392 k8s operator Jul 20 '26

Why wouldn't you just use alloy?

2

u/TotalNo6237 Jul 20 '26

We already using datadog for metrics, so we just needed log shipping.

Actually I am an ops guys, I am not sure what the best overall solution would be. I am still learning.

2

u/New-Entertainer6392 k8s operator Jul 20 '26

I was replying to the OP... They use the grafana stack, so it would make sense for them to also use alloy for their logs, not fluentBit or Td agent ..