Verify Service Status
Log in to AccuKnox SaaS and check that each module you deployed is functioning. It may take 2 minutes or so for events to be collected and displayed.
Check Overall Connection Status¶
- Cluster Manager: Select Cluster Manager from the menu to see all connected Kubernetes clusters.
Check Agent Status¶
Connect to the cluster via terminal and use the following command to check the agent status
kubectl get po -A | egrep 'kubearmor|cilium|hubble|shared|knox|feeder'
Sample Output
accuknox-agents feeder-service-5cccc87cbb-bzq74 1/1 Running 0 23s
accuknox-agents shared-informer-agent-79ffd76cbc-xxqpx 1/1 Running 0 1m
kube-system cilium-46vlh 1/1 Running 0 5m
kube-system cilium-bt484 1/1 Running 0 5m
kube-system cilium-hrqxj 1/1 Running 0 5m
kube-system cilium-j92jt 1/1 Running 0 5m
kube-system cilium-node-init-4nmqn 1/1 Running 0 5m
kube-system cilium-node-init-5sdl2 1/1 Running 0 5m
kube-system cilium-node-init-f8zwb 1/1 Running 0 5m
kube-system cilium-node-init-x4hwc 1/1 Running 0 5m
kube-system cilium-operator-8675b564b4-6b6tq 1/1 Running 0 5m
kube-system cilium-operator-8675b564b4-lrrlp 1/1 Running 0 5m
kube-system hubble-relay-74b76459f9-vvs44 1/1 Running 0 3m
kube-system kubearmor-d95gl 1/1 Running 0 3m
kube-system kubearmor-fwsc5 1/1 Running 0 3m
kube-system kubearmor-host-policy-manager-69cfc96948-nss27 2/2 Running 0 3m
kube-system kubearmor-policy-manager-986bd8dbc-b47n4 2/2 Running 0 3m
kube-system kubearmor-q64h7 1/1 Running 0 3m
kube-system kubearmor-relay-645667c695-d96g8 1/1 Running 0 3m
kube-system kubearmor-sh6fb 1/1 Running 0 3m