Does your company have a Change Advisory Board (CAB)?

• kube-monkey

  9 2,920 3.4 Go

  An implementation of Netflix's Chaos Monkey for Kubernetes clusters

Not in the typical sense, but we have plenty of standard practices and cross-team checkpoints to limit risk. By the time we're deploying changes to production, the work has had a card created, assigned points (which necessarily involves discussing scope and risk), architected (as a group), code peer reviewed, hit unit tests (automated), integration tests (automated), functional tests (automated), smoke tested (automated) end-to-end tests (a few automated, but mostly manual by QA), acceptance tested (by QA and business), resilience tests (chaos engineering with kube-monkey), been deployed to at least 3 environments (with the same exact same artifacts, just with config changes), and monitored for failures (pod restarts, log anomalies, etc -- all automated). Deploy to production is well communicated, and ANY team can request a halt to the deploy if they have concerns.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project