ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how Traefik Mesh’s TrafficSplit CRD enables weighted, code‑free canary releases in Kubernetes, with a step‑by‑step NGINX example and practical verification tips.
Learn how to use Cloud Run traffic splitting to shift a percentage of requests to a new revision, verify the split with curl and Cloud Monitoring, and roll back instantly if needed.
Learn how to configure Nomad’s update stanza for zero‑downtime rolling deployments with canary instances, Consul‑based health checks, auto‑promotion, and automatic rollback.
Learn how Envoy’s outlier detection automatically removes flaky upstream hosts during canary rollouts, with a practical configuration example, verification steps, and trade‑off guidance.
A decision guide that compares TrafficSplit with Istio‑based alternatives, explains trade‑offs, and shows how to implement and validate a weight‑based canary rollout.
Learn how Traefik Mesh TrafficSplit enables weighted canary releases without code changes, including setup, verification via Prometheus, and key limitations.
Goal: Ensure that a Nomad job can be rolled back to a previous version after an external database schema change without causing data corruption or version skew between old and new application instances. Uncertainty: Canary deployments update a single task, which may leave the majority of tasks running the old code against a new schema, risking incompatibilit
Goal Enable precise, non‑integer traffic allocation to revisions for canary and blue‑green deployments, such as 33.3%/33.3%/33.4% splits. Constraints The current Cloud Run Traffic Splitting API accepts only whole‑percentage values (e.g., 25%, 75%). Both the gcloud CLI and Cloud Console reject decimal inputs with validation errors. No public roadmap or releas
traefikmesh
kubernetes
cloudrun