Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(improvements): Improve the usability of karmor probe by detailing… #362

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Commits on Aug 21, 2023

  1. fix(improvements): Improve the usability of karmor probe by detailing…

    … error messages
    
    The following error may occur when executing "karmor probe".
    
      ```
      > karmor probe
      probe.go:380: error when getting kubearmor daemonset Get "http://localhost:8080/apis/apps/v1/namespaces/kube-system/daemonsets/kubearmor": dial tcp 127.0.0.1:8080: connect: connection refused
    
      Didn't find KubeArmor in systemd or Kubernetes, probing for support for KubeArmor
    
      Host:
        Observability/Audit: Supported (Kernel Version 5.15.0)
        Enforcement: Full (Supported LSMs: lockdown,capability,landlock,yama,apparmor)
      To get full probe, a daemonset will be deployed in your cluster - This daemonset will be deleted after probing
      Use --full tag to get full probing
      ```
    
    When "karmor probe" is executed, "systemctl status kubearmor" is executed
    internally, but the systemctl command may require sudo. In this case,
    without sudo, an error occurs.
    
    In this commit, to make it easier to understand the root cause of such an
    error, error messages have been modified to be more detailed.
    
    Signed-off-by: Hayato Kiwata <haytok@amazon.co.jp>
    haytok committed Aug 21, 2023
    Configuration menu
    Copy the full SHA
    eae62c5 View commit details
    Browse the repository at this point in the history