Deploying ThousandEyes Enterprise Agent on Kubernetes Cluster

[COjeda]

Hey everyone,

Has anyone successfully deployed an Enterprise Agent within a Kubernetes cluster?  Currently followed a Cisco U. training where this was used: justinhauer/Thousand-Eyes-kubernetes: Thousand Eyes Enterprise Agent Deployment in kubernetes (github.com)

However, it did not work.  I have a theory that this is due to ARM architecture of the cluster but while I wait for support to reply and confirm my suspicions, I wanted to ask here.  

Thanks.  

[Torbjørn · Accepted solution]

I haven't used that exact github project, but I have deployed an agent successfully to Kubernetes. As far as I can see those manifests should be OK.

That said the enterprise agent unfortunately does require x86, so you won't get it running on that specific k8s node/cluster.

[Tyler Langston · Accepted solution]

Hi @COjeda  - hopping in here to echo @Torbjørn's post and provide a few extra details from my expert team:

1. We don't offer official Kubernetes support at this point in time.
2. Our docker containers will currently only run on x86 CPU architecture. ARM CPUs are not currently supported. A full list of our supported CPU architecture can be found here. 

While both of these are areas we are looking into offering in the future, they're not currently on the roadmap for release.

[asergeant01]

I too am trying to deploy the enterprise agent on Kubernetes following https://github.com/jmullool/HELM_for_Cisco_ThousandEye_Agents/blob/master/thousandeyesagent/templates/deploymentAgent.yaml

The agent without BrowserBot works as expected, however with BrowserBot I receive constant logs about BrowserBot installing and when I check BrowserBot logs I see ipv4 forwarding issues

time="2024-10-30T10:19:11Z" level=info msg="Installation mode started"
time="2024-10-30T10:19:11Z" level=info msg="Deploying test image"
time="2024-10-30T10:19:11Z" level=info msg="This is a docker agent. Checking if browserbot is supported..."
time="2024-10-30T10:19:11Z" level=debug msg="IPv4 forwarding is disabled for this agent"
time="2024-10-30T10:19:11Z" level=debug msg="IPv6 forwarding is disabled for this agent"
time="2024-10-30T10:19:11Z" level=info msg="Installation done"
time="2024-10-30T10:19:11Z" level=error msg="Installation failed: IPv4 and IPv6 forwarding are disabled. Browserbot will not work\n"

[remyJe]

Hi, @asergeant01  you'll want to confirm that the hosts on which pods/containers are running have IP forwarding enabled:

https://www.kernel.org/doc/html/latest/networking/ip-sysctl.html

IP forwarding can also be enabled/disabled on a per-pod/container basis. More details here:

https://kubernetes.io/docs/tasks/administer-cluster/sysctl-cluster/

Kindly,

Jeremy Stark
  Technical Consulting Engineer
    ThousandEyes (part of Cisco)