Examples

You can change notification format to - long or short through settings based on your requirement. Check configuration for more details. The default notification type is short

Sample Notifications

Resource created

Resource deleted

Failed to pull image

Error in pod

Readiness probe failed for the pod

Job succeeded

Monitor Velero backups

Add following configuration resource_config to monitor Velero backups resource.

    - name: velero.io/v1/backups
      namespaces:
        include:
          - all
        ignore:
          -
      events:
        - create
        - update
        - delete
        - error
      updateSetting:
        includeDiff: true
        fields:
          - status.phase

With this configuration, BotKube will monitor create/delete/error events and updates in status.phase fields in velero.io/v1/backups resource.

Debugging use-cases

List pods in “fission” namespace

get_pods

Get logs of “controller-676f97f45-pjmv2” pod in “fission” namespace

logs logs

Show cluster health

cluster-health

Describe a node

desc_node

List top pods in “fission” namespace

top_pods

Check connection status of “gke-stg” cluster

flag_clustername

List services in a “gke-dev” cluster

get_services

Describe deployment in a “gke-stg” cluster

describe_deployment describe_deployment