Controller (SaaS, On Premise)

Showing results for 
Search instead for 
Did you mean: 

Controller on Kubernetes or Docker based platforms

Hello experts,
Just out of curiousity and with intermediate knowledge on kubernetes, I was just wondering if anyone tried installing Appdynamics controllers on Kubernetes or some other docker based platforms? And if yes, then what are his observations in terms of scalability and performance.

Reason am interested in such a kind is - we all know there is a constraint within AppD wrt horizontal scaling of controllers (we cannot have clustered controllers within active leg of architecture), I was thinking to create a base image for AppD controllers(standalone) and as the demand increases, you spinup another controller with no delay.
I understand that this will increase complexity of too many controller info to manage, but atleast time consumed in building of new clustered AppD env will be reduced (and cheaper than having full physical/virtual box provisioned)

I might sound weird but thought to highlight it over here for comments and suggestion.
(Like AppD on aws is awesome concept but due to some restrictions am not able to proceed on that thread)

Appreciate your help.


Controller on Kubernetes or Docker based platforms
Any thoughts on this?

I'd really have to sit down and think about it, but I think it'll be difficult. Your agents are hard-coded to authenticate themselves to a specific Access Key and Controller Name. Dynamically creating new Controllers would require you to also dynamically create new controller-info.xml files. Also, license key management might be an issue because the license rules are hard-coded into the key. That's not to say it's impossible, but you'd have to overcome those, perhaps a shared .yml like they do with the cluster agents? Not sure.


You can probably definitely do it for the Events Services and maybe even the EUM server since those can scale pretty easily. But you'd have to take in some extra considerations on the Console for the Events Server and maybe a reverse proxy to handle a dynamics EUM servername.

Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.

Thanks, Eric @Eric.Miller  for the response. I missed that you have already replied.


I think it really makes sense what you commented on above.

But what I am looking as of now is to have some logic and documentation defined around deploying controllers on containers for 2 factors - 

1. Will help us to meet resiliency requirements laid out by our Organization.  We will use replicas of the controllers to meet disaster event like scenarios. Currently, we have to manage the async replica of data and controller configurations across datacenters.

2. Will lower the cost of implementation as we don't need heavy boxes to host the environment but I can spinup smaller controller footprints based upon various lines of businesses. 

3. Easy to adopt Infrastructure as code concept at containers end for paving the environment across the datacenters within few minutes.



In nutshell, like you provide documentation for deploying controllers on AWS - similar documentation for container-based controller deployments would be much appreciated.