You are looking at the documentation of a prior release. To read the documentation of the latest release, please visit here.

hyperalert check_node_exists

Count Kubernetes Nodes

Synopsis

Count Kubernetes Nodes

hyperalert check_node_exists [flags]

Options

  -c, --count int           Number of expected Kubernetes Node
  -h, --help                help for check_node_exists
      --kubeconfig string   Path to kubeconfig file with authorization information (the master location is set by the master flag).
      --master string       The address of the Kubernetes API server (overrides any value in kubeconfig)
  -n, --nodeName string     Name of node whose existence is checked
  -l, --selector string     Selector (label query) to filter on, supports '=', '==', and '!='.

Options inherited from parent commands

      --allow_verification_with_non_compliant_keys   Allow a SignatureVerifier to use keys which are technically non-compliant with RFC6962.
      --alsologtostderr                              log to standard error as well as files
      --analytics                                    Send analytical events to Google Analytics (default true)
      --log_backtrace_at traceLocation               when logging hits line file:N, emit a stack trace (default :0)
      --log_dir string                               If non-empty, write log files in this directory
      --logtostderr                                  log to standard error instead of files
      --stderrthreshold severity                     logs at or above this threshold go to stderr
  -v, --v Level                                      log level for V logs
      --vmodule moduleSpec                           comma-separated list of pattern=N settings for file-filtered logging

SEE ALSO