Progressive delivery allows teams to gradually release changes to their applications, minimizing risk and ensuring stability. When using Blackbox exporters with Argo CD, you can implement a progressive delivery strategy through deployment strategies like canary or blue-green deployments. By managing the rollout of changes, you can monitor application performance and mitigate potential issues before a full rollout.
apiVersion: apps/v1
kind: Deployment
metadata:
name: blackbox-exporter
labels:
app: blackbox-exporter
spec:
replicas: 2
selector:
matchLabels:
app: blackbox-exporter
template:
metadata:
labels:
app: blackbox-exporter
spec:
containers:
- name: blackbox-exporter
image: ''
ports:
- containerPort: 9115
---
apiVersion: argoproj.io/v1alpha1
kind: Rollout
metadata:
name: blackbox-exporter-rollout
spec:
replicas: 2
strategy:
canary:
steps:
- setWeight: 20
- pause: { duration: 10s }
- setWeight: 100
template:
metadata:
labels:
app: blackbox-exporter
spec:
containers:
- name: blackbox-exporter
image: ''
ports:
- containerPort: 9115
How do I avoid rehashing overhead with std::set in multithreaded code?
How do I find elements with custom comparators with std::set for embedded targets?
How do I erase elements while iterating with std::set for embedded targets?
How do I provide stable iteration order with std::unordered_map for large datasets?
How do I reserve capacity ahead of time with std::unordered_map for large datasets?
How do I erase elements while iterating with std::unordered_map in multithreaded code?
How do I provide stable iteration order with std::map for embedded targets?
How do I provide stable iteration order with std::map in multithreaded code?
How do I avoid rehashing overhead with std::map in performance-sensitive code?
How do I merge two containers efficiently with std::map for embedded targets?