Force Field for Kubernetes provides continuous discovery/test, monitoring, and security for containerized application services.
ArecaBay MicroSensor is deployed as a container and runs alongside application service containers within Kubernetes Pods, either as a sidecar or daemonset on Kubernetes Nodes. This is done without disrupting application service containers, without installing any software on Kubernetes Worker Nodes, and most importantly without making any code changes to applications.
The ArecaBay MicroSensor is transparently deployed into any vanilla Kubernetes environment, and works with service meshes such as Istio-Envoy and Linkerd, without any changes or modifications to applications.
ArecaBay Cloud + Kubernetes Cluster
ArecaBay Enterprise + Kubernetes Cluster
Force Field for Kubernetes supports native command line tools, Kubectl and Helm, allowing management via Helm charts. For example, simply add the below lines to the Pod deployment YAML to enable Kubernetes deployments using Kubectl to enjoy full API traffic visibility and monitoring.
Working with Service Mesh implementation – Istio, Linkerd, and others.
ArecaBay MicroSensor is deployed as a container and runs alongside application service containers within Kubernetes Pods, either as a sidecar or daemonset on Kubernetes Nodes. This works well with Istio-Envoy proxy or Linkerd which themselves run also as sidecar.
No additional changes are required to the application or service mesh framework, and similarly, for Kubernetes deployments using only Envoy proxy, ArecaBay MicroSensor can be deployed without any changes to applications or Envoy proxy itself.