Share via

How to fix the AppD Machine agents which stopped working when we upgraded AKS from AKS 1.17 to AKS 1.24

Antony Sundar 0 Reputation points
2023-05-08T20:37:27.98+00:00

AppDynamics Machine agent stopped working when we upgraded the AKS from 1.17 to 1.24. The AppD Machine agents depoyed as DaemonSets are stuck in CrashLoopBackOff. Version if AppD Agent is 22.5.0.

Error we see in the logs is:

WARNING: All illegal access operations will be denied in a future release

Could not start up the machine agent due to: Failed to get a response from /info using a GET request. The error encountered is: java.net.SocketException: Connection refused

Please see startup.log in the current working directory for details.

Azure Kubernetes Service
Azure Kubernetes Service
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
2,459 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Akram Kathimi 1,366 Reputation points Microsoft Employee
    2023-05-09T08:51:06.21+00:00

    Hi @Antony Sundar ,

    Thank you for your question.

    By checking the supported AKS versions by AppDynamics v22.5, we can see that the latest supported AKS version is 1.21 as mentioned here.

    To resolve the issue, I suggest upgrading AppDynamics to the latest version (22.12) since it supports AKS version 1.24 as mentioned here.

    Please Accept the answer if the information helped you. This will help us and others in the community as well.

    Thank you.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.