osdc-nodelocaldns

Deploy and troubleshoot NodeLocal DNSCache in IPv6-only Kubernetes clusters.

17|14|Updated Jun 15, 2023
One-click install
npx skills add https://github.com/pytorch/ci-infra --skill osdc-nodelocaldns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: osdc-nodelocaldns
Source: https://github.com/pytorch/ci-infra/tree/main/osdc/.claude/skills/osdc-nodelocaldns
Command: npx skills add https://github.com/pytorch/ci-infra --skill osdc-nodelocaldns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers deploy, debug, and safely maintain NodeLocal DNSCache across IPv6-only Kubernetes clusters while avoiding DNS outages caused by incorrect service ordering, address-family assumptions, or incomplete metrics monitoring.

Core Features & Use Cases

  • Production Deployment Guidance: Coordinates dynamic kube-dns ClusterIP discovery, IPv6 validation, manifest rendering, service-first application, and conditional DaemonSet restarts.
  • Reliability and Diagnostics: Explains iptables-mode fallback behavior, CoreDNS configuration, health probes, tolerations, resource settings, image-pull behavior, and common failure modes.
  • Observability and Verification: Covers both metrics endpoints, canonical metric names, PodMonitor and alert requirements, smoke tests, ip6tables inspection, and soak-gate criteria for future cutovers.
  • Use Case: Use this Skill when changing the NodeLocal DNSCache DaemonSet or Corefile, investigating runner-node DNS failures, or preparing a future cluster-wide NLD rollout.

Quick Start

Use the osdc-nodelocaldns skill to diagnose a NodeLocal DNSCache rollout where pods are crashlooping or DNS metrics are missing.

Frequently Asked Questions about osdc-nodelocaldns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy NodeLocal DNSCache in an IPv6-only Kubernetes cluster?

To deploy NodeLocal DNSCache in an IPv6-only Kubernetes cluster, you must validate the dynamic kube-dns ClusterIP, apply the service before the DaemonSet, configure IPv6 iptables-mode, and verify the rollout with production soak tests.

Why are my NodeLocal DNSCache pods crashlooping after a manifest change?

NodeLocal DNSCache pods crashloop when service-before-DaemonSet ordering is violated, address-family assumptions are incorrect for IPv6, or CoreDNS Corefile configurations and health probes are misconfigured during manifest rendering.

How does NodeLocal DNSCache handle DNS metrics scraping in IPv6 environments?

NodeLocal DNSCache handles DNS metrics scraping in IPv6 environments by exposing dual metrics endpoints, utilizing canonical metric names, and requiring specific PodMonitor and alert configurations to ensure full DNS observability.

What is the correct service ordering for NodeLocal DNSCache rollouts?

The correct service ordering for NodeLocal DNSCache rollouts requires applying the service first before deploying the DaemonSet, which prevents DNS outages and ensures dynamic kube-dns ClusterIP validation succeeds.

How do I troubleshoot runner-node DNS failures with CoreDNS and iptables?

Troubleshoot runner-node DNS failures by inspecting ip6tables for IPv6 iptables-mode fallback behavior, checking CoreDNS configuration and health probes, and verifying dual metrics scraping to identify incomplete monitoring or misconfigured tolerations.

Can I use NodeLocal DNSCache for future cluster-wide DNS cutovers?

Yes, NodeLocal DNSCache supports future cluster-wide cutovers by enforcing smoke-test changes, soak-gate criteria verification, and conditional DaemonSet restarts to maintain resilient per-node DNS caching without outages.