Steadybit logoResilience Hub
Try SteadybitGitHub icon
Steadybit logoResilience Hub

New Relic Workflow Is Disrupted on Non-Ready Pods for a Deployment

When a deployment has no pods ready, New Relic Workflow should notice that and mark the workflow as disrupted.
Targets:

Containers

Kubernetes cluster

New Relic Accounts

New Relic Workloads

Download now

New Relic Workflow Is Disrupted on Non-Ready Pods for a Deployment

When a deployment has no pods ready, New Relic Workflow should notice that and mark the workflow as disrupted.
Targets:

Containers

Kubernetes cluster

New Relic Accounts

New Relic Workloads

Download now

New Relic Workflow Is Disrupted on Non-Ready Pods for a Deployment

When a deployment has no pods ready, New Relic Workflow should notice that and mark the workflow as disrupted.
Targets:

Containers

Kubernetes cluster

New Relic Accounts

New Relic Workloads

Download now

New Relic Workflow Is Disrupted on Non-Ready Pods for a Deployment

When a deployment has no pods ready, New Relic Workflow should notice that and mark the workflow as disrupted.
Targets:

Containers

Kubernetes cluster

New Relic Accounts

New Relic Workloads

Download now
Go back to list
The experiment editor showing the visual structure of the experiment.The experiment editor showing the visual structure of the experiment.

Intent

Verify that New Relic alerts you on disruptions in your New Relic workflow such as a critical deployment having no pods ready to serve traffic.

Motivation

Kubernetes features a liveness probe to determine whether your pod is healthy and able to accept traffic. If Kubernetes is unable to probe a pod, it is restarting it in the hope to get it ready eventually. In case it is a critical deployment, New Relic workflow should alert on this disrutpion

Structure

First, check that the New Relic Workflow is marked as operational As soon as all pods of a deployment aren't reachable, caused by the Steadybit attack block traffic, New Relic should detect this by marking the workflow as disrupted and ensuring your on-call team is taking action.

Environment Example

The Kubernetes deployment gateway consists of two pods. We are attacking both pods and wait for New Relic to detect the disrupted New Relic workflow.

Solution Sketch


Download now

.json (4 kB)

It's quick and easy

  1. 1.

    Download .json file
  2. 2.

    Upload it inside Steadybit
  3. 3.

    Start your experiment!
Screenshot showing the Steadybit UI elements to import the experiment.json file into the Steadybit platform.
Tags
Kubernetes
New Relic
Harden Observability
GitHub
steadybit/reliability-hub-db/tree/main/recipes/new-relic.workflow-deployment-unavailable
License
MIT
MaintainerSteadybit

Used Actions

See all
Block Traffic

Blocks network traffic (incoming and outgoing).

Attack

Attack

Containers

Start Using Steadybit Today

Get started with Steadybit, and you’ll get access to all of our features to discover the full power of Steadybit. Available for SaaS and on-prem!

Are you unsure where to begin?

No worries, our reliability experts are here to help: book a demo with them!

Steadybit logoResilience Hub
Try Steadybit
HubActionsTargetsExtensionsRecipes
© 2024 Steadybit GmbH. All rights reserved.
Twitter iconLinkedIn iconGitHub icon