# dry-run A dry run is manually executing a program using written variable values and runtime data to check its operation and control flow or find bugs. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 【kube-apiserver】Mutating / Validating Webhook：timeout、failurePolicy 与可用性门 DevFeed: [【kube-apiserver】Mutating / Validating Webhook：timeout、failurePolicy 与可用性门]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [configuration](), [dry-run](), [TLS (Transport Layer Security)](), [API]() Tags: [admission](), [api](), [apiserver](), [cel](), [configuration](), [distributed](), [kubernetes](), [kyverno](), [mutating](), [timeout](), [tls](), [v1-30-3](), [validating](), [webhook]() ### AI overview A tutorial on configuring and troubleshooting Kubernetes v1.30.3 mutating and validating admission webhooks. It explains configuration fields, timeout and failurePolicy behavior, production availability requirements, reinvocation and idempotency, CEL ValidatingAdmissionPolicy boundaries, and an evidence-based troubleshooting approach. It emphasizes that slow webhooks add latency to the admission path rather than indicating etcd lag. ### Source excerpt 钉 K8s v1.30.3 的 MutatingWebhookConfiguration / ValidatingWebhookConfiguration v1：timeoutSeconds、failurePolicy、sideEffects、reinvocationPolicy 字段语义；webhook 慢如何表现为写路径延迟而非 etcd lag；生产可用性门选取；CEL ValidatingAdmissionPolicy 作为内置替代路径；排障证据包。 ## Automatizar servidores con Ansible: primeros pasos DevFeed: [Automatizar servidores con Ansible: primeros pasos]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-01-08T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Ansible](), [Ansible Roles](), [ssh](), [dry-run](), [Git](), [nginx]() Tags: [ansible](), [dry-run](), [git](), [nginx](), [ssh](), [sysadmins](), [variables](), [vault]() ### AI overview A step-by-step introduction to automating server configuration with Ansible. It covers ad-hoc commands, inventories, playbooks, dry runs, roles, group variables, loops, and secrets with ansible-vault. ### Source excerpt Ansible desde cero: comandos ad-hoc, playbooks, roles, variables por grupo, bucles y secretos con ansible-vault, paso a paso. ## Using nixos-rebuild for NixOS Configuration, Upgrades, Rollbacks, and Testing DevFeed: [Using nixos-rebuild for NixOS Configuration, Upgrades, Rollbacks, and Testing]() Original publisher: [Read original article]() Author: Jacek Galowicz Published: 2023-07-31T00:00:00Z Content type: tutorial Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [configuration](), [Deployment](), [upgrade](), [dry-run]() Tags: [configuration](), [deployment](), [dry-run](), [tooling](), [upgrade]() ### AI overview This tutorial explains nixos-rebuild, the standard tool for changing an installed NixOS system. It covers configuration changes, input updates, upgrades, rollbacks, dry runs, virtual-machine testing, local rebuilds, and remote deployment or building. ### Source excerpt Discover the power of nixos-rebuild for seamless system configuration, upgrades, and rollbacks with just a few commands. Explore its versatile capabilities! ## Recovering Lost Post Data DevFeed: [Recovering Lost Post Data]() Original publisher: [Read original article]() Author: Jay (noreply@blogger.com) Published: 2013-05-07T12:00:00Z Content type: tutorial Language: en Sources: [Jay Fields]() Topics: [Chrome](), [developer tooling](), [dry-run]() Tags: [chrome](), [devtools](), [dry-run](), [error](), [logging](), [network]() ### AI overview A practical guide to recovering form data after a session-expired error by using Chrome DevTools. It explains how to inspect the Network tab, find the POST request, allow a repost if prompted, and copy the contents of Form Data. ### Source excerpt I recently typed out a long, thoughtful response in a textarea. I clicked submit, like I've done millions of times, and I got the dreaded "session expired" error message. This happens very, very rarely, but it's devastating when it does. Creating long & thoughtful responses isn't something that comes naturally for me. I crossed my fingers and clicked back. No luck, web 2.0 dynamically created text boxes ensured Chrome had no chance to preserve my editing state. My first reaction was: I guess I'm not responding after all. Then it occurred to me, DevTools must have my data somewhere, right? Lucky for me, the answer was yes. There might be easier ways, this is what worked for me: open DevTools go to the "Network" tab. look for the row with the method POST. If you don't see a POST row, try refreshing the page. With any luck you'll get a repost confirmation dialog, giving you some hope that your data is still around. (You'll want to allow the data repost) click on the POST row, and scroll down till you see "Form Data". If you've gotten this far, hopefully you'll find your data in clear text and able to be copied. The examples from this post are from following the instructions above and logging in to twitter.com. If you've ever lost post data in the past, you may want to give these directions a dry-run now. © Jay Fields - www.jayfields.com