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
When we execute karmor install
It install our helm chart followed up by waiting for KubeArmor to start to verify whether enforcement works or not.
Ideal case this is the behaviour
$ karmor install
🛡 Installed helm release : kubearmor-operator
😄 KubeArmorConfig created
⌚️ This may take a couple of minutes
🥳 KubeArmor Snitch Deployed!
🥳 KubeArmor Daemonset Deployed!
🥳 Done Checking , ALL Services are running!
⌚️ Execution Time : 30.608023946s
🔧 Verifying KubeArmor functionality (this may take upto a minute) /.
Cluster is Armored Up!
But in some cases, the daemonset creation can get stuck, it may be due to less node resources or incorrect volume mounts
$ karmor install
🛡 Installed helm release : kubearmor-operator
😄 KubeArmorConfig updated
⌚️ This may take a couple of minutes
🥳 KubeArmor Snitch Deployed!
ℹ️ Waiting for Daemonset to start: —
In that case the CLI forever keeps waiting to start. We should show the current status of Pods when we are waiting for the daemonset to start
Like
Pending
Init
PodInitialising
Running
And similarly show events as well in case there are any error events.
The text was updated successfully, but these errors were encountered:
When we execute
karmor install
It install our helm chart followed up by waiting for KubeArmor to start to verify whether enforcement works or not.
Ideal case this is the behaviour
But in some cases, the daemonset creation can get stuck, it may be due to less node resources or incorrect volume mounts
In that case the CLI forever keeps waiting to start. We should show the current status of Pods when we are waiting for the daemonset to start
Like
Pending
Init
PodInitialising
Running
And similarly show events as well in case there are any error events.
The text was updated successfully, but these errors were encountered: