Privacy Policy

Updated: 4 October 2026.

Scope and publisher

This policy describes the features used on DevOpsDreams, at devopsdreams.blogspot.com. The site is published under the DevOpsDreams name and hosted on Google's Blogger platform. For questions about this policy or information you have submitted, use the form on the Contact page.

Information you choose to provide

The form on the Contact page uses Blogger's contact-form service. It collects the name, email address, and message you enter so that the publisher can read and respond to your enquiry. Email and message are required. Do not include passwords, tokens, customer records, or other sensitive information. Contact messages are not intentionally published as blog content.

Comments use Blogger's Google-account sign-in and moderation features. An approved comment and the profile information Blogger associates with it may be visible to other readers. Avoid posting information you do not want public. You can request correction or removal of information you submitted through the contact form, identifying the relevant message or comment.

Hosting and cookies

Blogger and other Google services may process technical information, including browser and device information, request information, and cookies or similar storage, to operate their services. Their processing is described in Google's Privacy Policy and Google's explanation of partner-site data.

Your browser can block or delete cookies and manage site storage. These controls may affect sign-in, comments, or other features. A platform cookie notice is not the same as a choice about every advertising or analytics purpose.

Analytics

This site includes a Google Analytics tag to understand aggregate site usage, such as pages visited and traffic patterns. Google Analytics may use cookies and process device and interaction information. Read Google's partner-site information and the Google Analytics opt-out browser add-on for more information and controls. Browser controls also let you limit cookies and storage.

Do not put personal information in public comments, page URLs, or technical examples. The presence of an analytics tag does not mean that every visit is successfully measured.

Advertising

The site includes Google AdSense advertising code. When advertising is served, third-party vendors, including Google, may use cookies to serve ads based on a user's prior visits to this site or other websites. Google's advertising cookies enable Google and its partners to serve ads based on visits to sites across the Internet. See Google's explanation of advertising cookies.

You can manage personalised advertising through Google's ad settings and find information about other participating providers at YourAdChoices. Read Google's advertising technology information for further details.

Where a consent message is displayed, use its controls to manage the available purposes and vendors. The site's Privacy and cookie settings link appears when Google's consent service is ready and lets you reopen its settings. If that link is unavailable, you can still use the Google and browser controls linked above. Advertising consent settings and browser cookie settings serve different roles. The presence of advertising code does not establish that an ad is shown on every visit.

Links and requests

Articles link to external documentation and websites. Those sites have their own privacy practices, and visiting them is your choice. Contact DevOpsDreams for questions or requests about information supplied directly to the publisher. Google-account and Google-service controls are managed through Google.

This policy may change as the site's features change. The date above identifies the latest revision.

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