Open AbhiBhalani11 opened 3 months ago
@AbhiBhalani11 I'm sorry to hear you're having trouble. This isn't an issue with the New Relic Node Agent, so I've transferred it to the k8s-agents-operator repo.
Can anyone have a solution to this issue? I am stuck in the production setup.
Hi @AbhiBhalani11 We currently don't officially support AWS EKS Fargate for our K8s Agent operator.
Although we're very close to release a new version that don't require cert-manager that may solve your needs.
cc @dbudziwojskiNR @ramkrishankumarN
How close is close? Just wondering if I should wait it out to deploy operator across the fleet or wait for the non-cert-manager dependent version.
Hi @brenwhyte! We've actually already released support for non-cert-manager install starting in v0.13.0. This said, I would recommend installing v0.14.0 as it has support for annotation-less install :)
The timing couldn't have been more perfect, checking this out now 👍
Hey o/
I'm using the nri-bundle chart, how can I specify v0.14.0 version of the k8s-agents-operator
subchart?
I don't think I can.
Using Flux to deploy the charts
Hi @brenwhyte! We rollout releases over the course of a couple days. The nri-bundle
chart released yesterday contains v0.14.0 of the operator. Please let me know if anything else comes up!
Hi @brenwhyte! Just wanted to check in if you were able to install the operator? Cheers!
I am trying to install the Kubernetes agent operator in the AWS EKS cluster with the fargate container. I am following this article to install the operator.
I want to integrate New Relic to collect APM and AWS EKS fargate container logs in New Relic.
The below command execution is getting stuck and the job runs for 5 min and then gets terminated with a timeout error.
The same command works for the minikube Kubernetes cluster in the local machine.
Please let me know if I am missing something to make the cert-manager job completed.