You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After installing KubeArmor via Helm within one of our 1.26 EKS clusters, I ran into issues with a few resources being in the wrong namespaces as I used a namespace other than the suggested "kube-system". After looking into it a bit, I see at least one resource explicitly using kube-system (leader election role binding) which causes errors, while many others use the Helm release's namespace.
I am wondering, is KubeArmor intended to only be deployed within the kube-system namespace, or is this a bug?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
After installing KubeArmor via Helm within one of our 1.26 EKS clusters, I ran into issues with a few resources being in the wrong namespaces as I used a namespace other than the suggested "kube-system". After looking into it a bit, I see at least one resource explicitly using kube-system (leader election role binding) which causes errors, while many others use the Helm release's namespace.
I am wondering, is KubeArmor intended to only be deployed within the kube-system namespace, or is this a bug?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions