Contact

Send a private message

Use the form on this page to report a technical error, suggest a topic, or ask about accessibility, privacy, or copyright. Enter your name, an email address for replies, and your message. Email and message are required.

Sending a message requires JavaScript. If the form does not respond, enable JavaScript and reload the page. The form uses Google's Blogger service; browser extensions that block that service may prevent it from working. Check the status shown beneath the Send button before assuming your message has been submitted.

Report a technical error

Include these details so the affected explanation can be checked:

  • The article URL and the relevant heading, command, or code example.
  • What appears to be incorrect and what you expected instead.
  • The software version and any relevant environment assumptions.
  • A link to authoritative documentation or a short, reproducible example, if available.

Remove credentials, access tokens, customer information, and other confidential details from messages and screenshots. DevOpsDreams publishes educational material and does not provide urgent incident-response support.

Other enquiries

For a broken link or accessibility problem, include the page URL and describe what happened. For a privacy request, identify the message or comment concerned without sending unnecessary personal information. For a copyright concern, identify the article and material involved and explain your relationship to the rights holder.

You can also ask a technical question in an article's comment section using a Google account. Comments are moderated before publication and are public after approval. Use the form on this page for information intended only for the publisher.

Read the Privacy Policy for information about contact messages, comments, analytics, and advertising. Looking for a guide rather than contacting the publisher? Start Here helps you choose one by task.

Comments

Post a Comment

Popular posts from this blog

Argo CD Auto-Sync and Health Checks: An Operator's Guide to Safe GitOps Reconciliation

Image
Argo CD Auto-Sync and Health Checks: An Operator's Guide to Safe GitOps Reconciliation Auto-sync and health are not the same thing in Argo CD. This guide shows how reconciliation, pruning, self-healing, retries, health checks, hooks, and sync waves fit together in real clusters. TL;DR Argo CD auto-sync and health checks solve different problems. Auto-sync decides when the controller reconciles Git with the cluster, while health checks decide whether the resulting resources are ready, degraded, or suspended. In practice, you need both: automated sync with prune and self-heal keeps desired state converged, retry refresh helps failed syncs recover on new revisions, and health checks plus custom Lua logic make readiness visible to operators. Sync waves and hooks add ordering when resources depend on each other. The control loop most teams misunderstand Argo CD has two separate jobs that often get blurred together in day-to-day platform talk. The first is reconciliation. Should Arg...
Read more

Applying SRE Error Budgets to Services Running on EKS: SLIs, Burn Rates, and Release Decisions

Image
Listen to this article AI-narrated article - 28 min 01 sec. Prose is preserved; code and diagram cues refer to the examples below. Your browser does not support audio playback. Open the MP3 . Read the narration transcript - Open audio Applying SRE Error Budgets to Services Running on EKS: SLIs, Burn Rates, and Release Decisions Build error budgets around user requests, not healthy pods. Implement Prometheus burn-rate alerts, diagnose EKS failure modes, and turn reliability evidence into release decisions. TL;DR Error budgets turn a service reliability objective into an explicit allowance for unsuccessful user events. For EKS workloads, measure requests at a defined user boundary, calculate good and total events consistently, and distinguish application failures from load balancer failures and missing telemetry. This guide implements request-based SLIs, rolling budget calculations, and multiwindow burn-rate alerts with Prometheus. It also explains latency budgets, low-traffic edge ca...
Read more

Progressive Delivery with Canary and Blue-Green on Kubernetes: Argo Rollouts, Flagger, and Gateway API

Image
Listen to this article AI-narrated article - 19 min 58 sec. Narration may not include the latest examples. Use the written guide for implementation details. Your browser does not support audio playback. Open the MP3 . Read the narration transcript - Open audio Progressive Delivery with Canary and Blue-Green on Kubernetes: Argo Rollouts, Flagger, and Gateway API Canary and blue-green delivery fail when teams treat them as YAML patterns. This guide shows how rollout controllers, traffic routers, metrics gates, and rollback mechanics work together on Kubernetes. TL;DR Progressive delivery on Kubernetes is safest when rollout control, traffic control, and metric evaluation are separated. Native Deployments provide rolling updates and revision rollback, but canary and blue-green releases need explicit traffic splitting, health gates, and promotion rules. Argo Rollouts gives Kubernetes-native Rollout, AnalysisTemplate, and blue-green/canary strategies; Flagger automates service-mesh or G...
Read more

Contact DevOpsDreams


*

*