CloudHealth EKS agent FAQs

Products

• CloudHealth

Issue/Introduction

Below are frequently asked questions regarding the EKS agent and what information is sent to CloudHealth.

Resolution

1. What information goes out from the EKS cluster to CloudHealth?

A) The collector agent uses the Kubernetes API to gather data directly from the k8s cluster that is then sent to the platform. The clusterrole (https://github.com/CloudHealth/helm/blob/main/charts/cloudhealth-collector/templates/clusterrole.yaml) shows all permissions needed for this and all of the different k8s objects that we are collecting.

2. Do IP addresses, environment values, secrets, or data from the etcd  get sent to CloudHealth?

A) Any data that is contained within the objects above are sent to CloudHealth.  This includes pods, nodes, namespaces, services, resourcequotas, limitranges, persistentvolumes, persistentvolumeclaims, statefulsets, damonsets, deployments, replicasets, cronjobs, jobs, ingresses, and pod/node metrics from metrics-server.  The platform does not collect k8s secrets or any ENV variables outside of the objects above.

3. How is the information transmitted to CloudHealth?  Is it possible to limit the container communication just to: api.cloudhealthtech.com and containers-api.edge.cloudhealthtech.com?

A) All data is sent to containers-api.edge.cloudhealthtech.com/ and communication can be limited there.