Kubernetes | Edge Logging

Overview

This article provides the commands and logic required to retrieve logs for Aembit Edge Components (Agent Controller, Agent Injector, and Agent Proxy) within a Kubernetes cluster. Accessing these logs is the first step in diagnosing lifecycle and connectivity issues.

Relates To

• Deployment Type: Kubernetes

• Components: aembit-agent-controller, aembit-agent-injector, aembit-agent-proxy (Sidecar)

Cause (Symptom)

You should use this guide if:

• An Aembit pod is in a CrashLoopBackOff or Pending state.

• The Agent Injector is not successfully creating sidecars in client workloads.

• You need to verify registration or identity attestation events.

Solution

1. Retrieve Agent Controller Logs The Controller manages registration and policy updates.

Kubernetes

kubectl logs -l app.kubernetes.io/name=aembit-agent-controller -n aembit

ROSA / OpenShift:

oc logs -l app.kubernetes.io/name=aembit-agent-controller -n aembit

2. Retrieve Agent Injector Logs The Injector handles the Mutating Admission Webhook logic.

Kubernetes

kubectl logs -l app.kubernetes.io/name=aembit-agent-injector -n aembit

ROSA / OpenShift:

oc logs -l app.kubernetes.io/name=aembit-agent-injector -n aembit

3. Retrieve Agent Proxy (Sidecar) Logs Since the Proxy is a sidecar, you must specify the container name (aembit-agent-proxy).

Kubernetes

kubectl logs <workload-pod-name> -n <namespace> -c aembit-agent-proxy

ROSA / OpenShift:

oc logs <workload-pod-name> -c aembit-agent-proxy -n <workload-namespace>