cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Community access restored to most members


I've been able to make some changes to restore community engagement access to most members.

Follow the blog post for up to date information



We thank you for your patience while we get this fixed


Issue registering a cluster agent to the controller.

Gustavo.Marconi
Builder

Hi everybody,

I'm trying to monitor a demo web app deployed with Kubernetes, but even following the documentation I end up short in that pursue, the web app consiste in 4 containers, all running properly on a Ubuntu Server 24.04, using MicroK8s and kubectl.

I followed this guide in the documentation:
https://docs.appdynamics.com/appd/24.x/latest/en/infrastructure-visibility/monitor-kubernetes-with-t...

Everything was clear for the seven steps, but I have to point it out that in the step 6, the YML example is showing the port 8080 for the controllerUrl, and since I have the SaaS version, I changed it to 443.

When I validate the installation noticed that the cluster agent was not registered, so I started following the troubleshooting docs, when I retrieve the logs for the namespace with the operator and the cluster-agent I checked the following error:
[ERROR]: 2024-07-03 15:52:57 - secretconfig.go:68 - Problem With Getting /opt/appdynamics/cluster-agent/secret-volume/api-user Secret: open /opt/appdynamics/cluster-agent/secret-volume/api-user: no such file or directory
I don't know why is searching for that specific path and in which moment should I create or where to find that api-user, that was not in the docs.

So I'll be really thankful if someone could help me with this issue.

Hope everybody have a nice day.

Regards

12 REPLIES 12

Rajesh.Ganapavarapu
AppDynamics Team

Hello @Gustavo.Marconi ,

Sure I'm checking on running the curl command to check the connectivity issue. I remember asking you to update the controller url as https instead of http ? Have you made these change and still facing the same issue ?

Also can you please confirm if you have any proxy inbetween ?

 

Best Regards,
Rajesh Ganapavarapu

Hi Rajesh,

It was the http configuration on my controller, as soon as I changed to https and re-deploy my cluster-agent, started reporting to my controller.

Thanks for the help and patience.

Have a great day!

Regards
Gustavo Marconi

Rajesh.Ganapavarapu
AppDynamics Team

Hello Gustavo,

Yes, by default SaaS controller is SSL enabled so we need to provide secure connection otherwise Clusteragent will fail to connect to the controller.

Glad that helped. 

Best Regards,
Rajesh Ganapavarapu