robusta-dev/robusta 0.11.0 on GitHub

New Features

Change Tracking Triggers

Trigger a playbook when a resource field changes. Learn more

customPlaybooks:
- name: "NotifyOnImageChange"
  triggers:
    - on_deployment_update: {}
        change_filters:
          include:
          - image
  actions:
    - resource_babysitter: {}

Fine Grained Scope For Triggers

Triggers now have an extensive include/exclude definition. Explore examples

customPlaybooks:
- name: "PostgresWarning"
  triggers:
    - on_event_create:
        scope:
          include:
            - attributes:
                - "type=Warning, involvedObject.name=postgres, event.reason=FailedScheduling"
  actions:
    - create_finding: # 
       title: "Failed scheduling postgres"
       aggregation_key: "FailedScheduling"

View Argo Rollouts in the Robusta UI

Users can now monitor and manage Argo rollouts directly within the Robusta UI. See PR

Other Changes

Update dependencies to mitigate vulnerabilities by @arikalon1 in #1370 and @Sheeproid in #1372.
Added KRR scan support for Mattermost sink by @IdeoG in #1374.

Breaking Changes

Sink Matcher Identifier Update:
Some playbooks notifications identifiers have changed. (For example: image_pull_backoff_reporter is now ImagePullBackoff)
If you're using Sink Matchers based on the identifier you will need to update your sinks configuration.
For example:
Image_pull_backoff_reporter → ImagePullBackoff
job_failure → JobFailure
krr_report → KrrReport
pod_oom_killer_enricher → PodOOMKilled
report_crash_loop → CrashLoopBackoff

Full list of changed identifiers

job_failure -> JobFailure
image_pull_backoff_reporter -> ImagePullBackoff
krr_report -> KrrReport
pod_oom_killer_enricher -> PodOOMKilled
report_crash_loop -> CrashLoopBackoff
show_stackoverflow_search -> ShowStackoverflowSearch
argo_app_sync -> ArgoAppSync
scale_hpa_callback -> ScaleHpaAction
alert_on_hpa_reached_limit -> HpaReachedMaximum
daemonset_fix_config -> DaemonsetFixConfig
daemonset_silence_false_alarm -> DaemonsetSilenceFalseAlarm
report_rendering_task -> GrafanaReport
disk_benchmark -> DiskBenchmark
report_image_changes -> ReportImageChanges
http_get -> HttpGet
http_post -> http_post
http_put -> HttpPut
java_process_inspector -> JavaProcessInspector
pod_jmap_pid -> PodJmapPid
pod_jstack_pid -> PodJstackPid
job_restart_on_oomkilled_community -> JobRestartOnOomkilledCommunity
node_not_ready -> NodeNotReady
count_pod_creations -> CountPodCreations
volume_analysis -> VolumeAnalysis
python_profiler -> PythonProfiler
pod_processes -> PodProcesses
python_memory_allocations -> PythonMemoryAllocations
debugger_stack_trace -> DebuggerStackTrace
python_process_inspector -> PythonProcessInspector
python_debugger -> PythonDebugger
popeye_report -> PopeyeReport
volume_snapshot_error -> VolumeSnapshotError
volume_snapshot -> VolumeSnapshot
restart_loop_reporter -> CrashLoopBackoff
http_stress_test -> HttpStressTest
Generic finding key -> GenericFindingKey
Generic Change -> GenericChange
General scheduled task -> GeneralScheduledTask
crash_loop -> CrashLoop

Resource Babysitter action Breaking change
The fields_to_monitor was removed from resource_babysitter action. If you added a custom playbook, with this action, you may need to update the action configuration, see here about how to be alerted on custom configuration changes

New Contributors

@IdeoG made their first contribution - Sending krr reports to Mattermost in #1374.

Full Changelog: Compare Versions