Learn how to implement progressive delivery for HTTP/2 and HTTP/3 using Argo CD, allowing for controlled rollouts and testing of new features in a Kubernetes environment.
progressive delivery, HTTP/2, HTTP/3, Argo CD, Kubernetes, feature rollout
# Create an Argo CD Application for progressive delivery
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: my-app
namespace: argocd
spec:
destination:
name: ''
namespace: my-app-namespace
project: default
source:
repoURL: 'https://github.com/my-org/my-app.git'
targetRevision: HEAD
path: k8s
syncPolicy:
automated:
prune: true
selfHeal: true
syncOptions:
- CreateNamespace=true
- ApplyOutOfSyncOnly=true
# Define progressive rollouts (for example with an nginx deployment)
# This can involve a specific configuration for HTTP/2 or HTTP/3 if needed
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?