Kubernetes install

[T_Singh]

Hi All

Im trying to install on my rke cluster and have read the documentation.

There seem to be no instructions on how to deploy the operator first. After creating a namespace, it jumps straight to 'deploy cluster agent operator yml' without any predefined yml code 😐

I tried the github readme as well, do I need to download the entire deploy directory from github or just the operator yml?😐

[Claudia_Landiva]

Hello, @T.Singh 

I wonder, did you happen to use this documentation: 

https://docs.appdynamics.com/display/PRO45/Install+the+Cluster+Agent 

The Cluster Agent Bundle on step 2 of that doc includes the cluster-agent-operator.yaml file. You can download it on our Downloads portal, or from our GitHub.

Does this answer your question?  If not, @Jeffrey.Holmes might have additional insight—mentioned here for visibility into your question.

Kind regards,

Claudia Landivar

Community Manager & Editor

AppDynamics

[T_Singh]

Hi @Claudia.Landivar @Jeffery.Holmes

Thanks for responding.
I am unsure of where to start, I assumed it was the Appdynamics operator for Kubernetes and that would auto install all dependencies cluster agent/machine agent.

The documentation does make it a bit hard for ppl new to AppD.

This is what I was referring to.
https://docs.appdynamics.com/display/PRO45/Deploy+the+AppDynamics+Operator+on+Kubernetes

[Claudia_Landiva]

@Ondine.Kilker, @Liza.Shibu, and @Jeff.Holmes:

Per our discussion, here is the document @T.Singh started on to configure AppDynamics for Kubernetes — Is that right, T. Singh? Team, can you weigh in? This is a great opportunity to discover how Docs and Community can help.

Claudia Landivar

Community Manager & Editor

[Jeffrey_Holmes]

Hi @T.Singh The current docs assume you start with the instructions on https://docs.appdynamics.com/display/PRO45/Install+the+Cluster+Agent and download the cluster agent bundle, which will include the cluster-agent-operator.yaml. However, I can understand how you'd easily start on the 'Deploy the AppDynamics Operator on Kubernetes' page, since it is a subpage and could be interpreted as step 1 in the install process. 

Perhaps our doc page 'Deploy the AppDynamics Operator on Kubernetes' could include a prerequisites section that ensures the steps on 'Install the Cluster Agent' were performed, and make clear that the cluster-agent-operator.yaml was part of the cluster agent bundle downloaded from that step.

Jeff

@Claudia.Landivar @Ondine.Kilker 

[T_Singh]

@Jeffrey.Holmes @Claudia.Landivar 

Thank you for reviewing the feedback. 

The operator section is positioned above the cluster agent section in the docs so it can be a bit misleading, but all sorted now. 

I did run into a licensing issue though. Looks like the trial isn't providing server visibility/infra licensing and as a result, the cluster agent is not registering with the SaaS controller. Can you please review this as well?
(Screenshot of my license count attached)

Cluster agent licensing errors in logs:

│ Property -appdynamics.agent.accountAccessKey successfully read and added to CA_PROPERTIES                                                                       │
│ [INFO]: 2020-06-13 01:01:53 - main.go:48 - Starting APPDYNAMICS CLUSTER AGENT version 20.5.0                                                                    │
│ [INFO]: 2020-06-13 01:01:53 - main.go:49 - Go lang version: go1.12.1                                                                                            │
│ W0613 01:01:53.285353       7 client_config.go:549] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.          │
│ [INFO]: 2020-06-13 01:01:53 - main.go:59 - Kubernetes version: v1.17.5                                                                                          │
│ [INFO]: 2020-06-13 01:01:53 - main.go:188 - Registering cluster agent with                                                                                      │
│  controller host : xxx.saas.appdynamics.com                                                                                                    │
│  controller port : 443                                                                                                                                          │
│  account name : xxx                                                                                                                          │
│ [INFO]: 2020-06-13 01:01:53 - agentregistrationmodule.go:286 - Established connection to Kubernetes API                                                         │
│ [INFO]: 2020-06-13 01:01:53 - agentregistrationmodule.go:50 - Cluster name: r0-rke                                                                              │
│ [INFO]: 2020-06-13 01:01:53 - agentregistrationmodule.go:101 - Initial Agent registration                                                                       │
│ [INFO]: 2020-06-13 01:01:54 - agentregistrationmodule.go:127 - Successfully registered agent again r0-rke                                                       │
│ [WARNING]: 2020-06-13 01:01:54 - agentregistrationmodule.go:206 - Agent is not licensed                                                                         │
│ [INFO]: 2020-06-13 01:01:54 - agentregistrationmodule.go:57 - Started APPDYNAMICS CLUSTER AGENT Successfully                                                    │
│ [INFO]: 2020-06-13 01:01:54 - eventmodule.go:29 - Starting Event Module                                                                                         │
│ [INFO]: 2020-06-13 01:01:54 - containermonitoringmodule.go:242 - Registering containers for cluster with machine Id 162                                         │
│ [INFO]: 2020-06-13 01:01:54 - podmonitoring.go:72 - Starting Pod Monitoring Module                                                                              │
│ [INFO]: 2020-06-13 01:02:54 - agentregistrationmodule.go:104 - Registering agent again                                                                          │
│ [INFO]: 2020-06-13 01:02:54 - agentregistrationmodule.go:127 - Successfully registered agent again r0-rke                                                       │
│ [WARNING]: 2020-06-13 01:02:54 - agentregistrationmodule.go:206 - Agent is not licensed     

[T_Singh]

Hi Guys

Any updates here?

[Jeffrey_Holmes]

Hi @T.Singh 

I was tracking down how we can change trial licenses to include a Server Visibility license, which may a few days to sort out.

thanks

Jeff

---

Edited  6/16/20 C. Landivar

[Chris_Edwards]

First: Im still stuck at the first error:

agentregistrationmodule.go:113 - Failed to send agent registration request: Status: 404 Not Found, Body

Second: For the kubernetes Cluster agent, does there need to be a license on the server? Or can it just take the the host and access key? I would imagine that it wouldn't since getting licenses on the machines would be pretty tough if you're machines are ephemeral or are just a huge number of servers versus pods

[T_Singh]

I've found the trial license does not cover Kubernetes agent licensing...which is a bit beside the point.

AppD is aware and discussing internally, unfortunately, no immediate fix. I've been chasing for a week with no luck.

[Chris_Edwards]

Yea... I think I found out part of mine though. It does leave me with one question for the team:

If my AppDynamics is internally hosted and behind a loadbalancer does that constitute this part of BOTH the proxy and SSL cert? (https://docs.appdynamics.com/display/PRO45/Configure+the+Cluster+Agent#ConfiguretheClusterAgent-Conf...) 

I think this is my issue, and I just wanted to know if the resolution would be to configure a proxy based on my loadbalancer, and then pass kubernetes my SSL cert? @Jeffrey.Holmes @Ondine.Kilker, 

[Jeffrey_Holmes]

@Chris.Edwards you would want to configure a cert for the endpoint where the cluster agent ssl connection would terminate, typically with the load balancer. I don't think you'd need the on prem controller cert unless the load balancer to controller connection is using ssl as well.

[Chris_Edwards]

Ah okay. The only cert we have is terminated at the loadbalancer level, I saw in the docs that there's an option to add a proxy, but Im not sure if a loadbalancer counts as a proxy or if its technically different.

Also, now, I'm getting the unauthorized notice

agentregistrationmodule.go:113 - Failed to send agent registration request: Status: 401 Unauthorized

I have confirmed that I am using the Name and Access Key listed in the Administration Tools > License > Account, but to no avail..

[Jeffrey_Holmes]

Two thoughts: generally that error indicates an error with access key, so worth double checking the value. Also have you setup the secret based on that value using:

kubectl -n appdynamics create secret generic cluster-agent-secret --from-literal=controller-key=<access-key>

as described on this page:

https://docs.appdynamics.com/display/PRO45/Deploy+the+Cluster+Agent+on+Kubernetes

And finally, do you have an available server visibility license?

[Chris_Edwards]

Regarding the access key, I just double checked and everything checks out... Same account name and access key that are on the License > Account tab.

And I don't have the server licenses currently set up, Im in the process of getting those from our internal team to use. What type of errors would show if the license wasn't set up? I understand that it wouldn't work, but I want to try and figure out what errors could come from where (for future reference)

[Jeffrey_Holmes]

You should see a message similar to this for missing server visibility license:

[WARNING]: 2020-06-04 15:23:28 - agentregistrationmodule.go:206 - Agent is not licensed

[Chris_Edwards]

Ah, gtocha. I think I found out what my specific issue was. The controller version I was using didn't have the license installed on it yet, I just think that with controllers it doesnt return a licensing error but a different error that's not exactly accurate. But I think that was it

[T_Singh]

Update:

I seem to have progressed, however seeing unlicensed errors in logs. This is a pro trial.

│ [ERROR]: 2020-06-12 06:40:41 - agentregistrationmodule.go:113 - Failed to send agent registration request: Post https://xxxx.saas.appdynamics.c │

│ [ERROR]: 2020-06-12 06:40:41 - agentregistrationmodule.go:114 - clusterId: 162                                                                                  │

│ [ERROR]: 2020-06-12 06:40:41 - agentregistrationmodule.go:116 - Registration properties: {}                                                                     │

│ [INFO]: 2020-06-12 06:41:41 - agentregistrationmodule.go:104 - Registering agent again                                                                          │

│ [INFO]: 2020-06-12 06:41:42 - agentregistrationmodule.go:127 - Successfully registered agent again r0-rke                                                       │

│ [WARNING]: 2020-06-12 06:41:42 - agentregistrationmodule.go:206 - Agent is not licensed