KubeArmor icon indicating copy to clipboard operation
KubeArmor copied to clipboard

Failed test scenarios on Vagrant Env

Open nam-jaehyun opened this issue 2 years ago • 1 comments

Bug Report

General Information

  • Environment description (GKE, VM-Kubeadm, vagrant-dev-env, minikube, microk8s, ...) vagrant-dev-next + k3s (-> $ make vagrant-up NETNEXT=1)

  • Kernel version (run uname -a) Linux kernel 5.15

To Reproduce

vagrant-dev-next $ kubectl proxy & vagrant-dev-next $ cd KubeArmor/tests

  1. test-scenarios-github.sh

vagrant-dev-next $ ./test-scenarios-in-local.sh (test scenarios failed)

  1. test-scenarios-in-local.sh

vagrant-dev-next $ ./test-scenarios-in-local.sh (test scenarios failed)

Expected behavior

All test scenarios should pass, but it seems that something is still missing in the bpf-lsm enforcer.

nam-jaehyun avatar Jul 31 '22 09:07 nam-jaehyun

I believe we can close this issue, since it's not reproducible anymore. // @nam-jaehyun

daemon1024 avatar Aug 07 '22 17:08 daemon1024