Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

homelab-dns-context

Étoiles8

Forks2

Mis à jour12 avril 2026 à 20:04

Use when you need to understand or configure the DNS setup for the homelab and the OKD cluster, including Pi-hole records.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

josephaw1022

josephaw1022/okd-sno-manual-install

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Administrateurs de réseaux et de systèmes informatiquesProfessions informatiques et mathématiques·SOC 15-1244

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	homelab-dns-context
description	Use when you need to understand or configure the DNS setup for the homelab and the OKD cluster, including Pi-hole records.

Homelab DNS Context

DNS infrastructure management for the homelab and OKD cluster.

Instructions

Use this skill to understand how DNS records are propagated to the Pi-hole.
All cluster-specific DNS logic is encapsulated in okd/dnsmasq/okd.conf.
Refer to references/records.md for the full list of static OKD records.

Procedures

Updating DNS Records

Modify okd/dnsmasq/okd.conf.
Execute make update-dns from the okd/ directory.
This runs an Ansible playbook to sync the config to the Pi-hole VM and restart services.

Gotchas

Manual VM Setup: The Pi-hole VM (192.168.1.5) is NOT automated. It was manually created on the Lenovo Laptop host (192.168.1.6) via Cockpit.
Dual Interfaces: The Pi-hole VM uses two NICs: one for the default VM network and one for the 192.168.1.0/24 LAN.
No DHCP: Pi-hole does NOT handle DHCP; the Netgear router handles all IP assignments.
Service Restart: Updating DNS via Ansible restarts pihole-FTL on the VM.

Plus depuis ce dépôt

même dépôt

homelab-hardware-context

josephaw1022/okd-sno-manual-install

Use when you need to understand the physical servers, their operating systems, or hardware specifications in the homelab.

2026-07-258

openshift-cluster-entraid-setup

josephaw1022/okd-sno-manual-install

Use when setting up or managing Entra ID (Azure AD) OAuth authentication for an OKD/OpenShift cluster. This skill covers the creation of Azure App Registrations, cluster secrets, and the OAuth configuration resource.

2026-04-128

homelab-network-context

josephaw1022/okd-sno-manual-install

Use when you need to understand the homelab's network topology, IP ranges, gateway, or DNS server locations.

2026-04-128

openshift-api-loadbalancer

josephaw1022/okd-sno-manual-install

Use when managing or troubleshooting the Nginx-based load balancer (okd-lb) for the OKD cluster.

2026-04-128

openshift-node-setup

josephaw1022/okd-sno-manual-install

Use when you need to understand how the OKD nodes (VMs) are created, managed, and destroyed on the desktop-server libvirt host in the homelab.

2026-04-128

openshift-provisioning-workflow

josephaw1022/okd-sno-manual-install

High-level overview of the OKD cluster setup process. Use this to understand the end-to-end flow from planning IPs and DNS to starting the VMs.

2026-04-128

name	homelab-dns-context
description	Use when you need to understand or configure the DNS setup for the homelab and the OKD cluster, including Pi-hole records.

Homelab DNS Context

DNS infrastructure management for the homelab and OKD cluster.

Instructions

Use this skill to understand how DNS records are propagated to the Pi-hole.
All cluster-specific DNS logic is encapsulated in okd/dnsmasq/okd.conf.
Refer to references/records.md for the full list of static OKD records.

Procedures

Updating DNS Records

Modify okd/dnsmasq/okd.conf.
Execute make update-dns from the okd/ directory.
This runs an Ansible playbook to sync the config to the Pi-hole VM and restart services.

Gotchas

Manual VM Setup: The Pi-hole VM (192.168.1.5) is NOT automated. It was manually created on the Lenovo Laptop host (192.168.1.6) via Cockpit.
Dual Interfaces: The Pi-hole VM uses two NICs: one for the default VM network and one for the 192.168.1.0/24 LAN.
No DHCP: Pi-hole does NOT handle DHCP; the Netgear router handles all IP assignments.
Service Restart: Updating DNS via Ansible restarts pihole-FTL on the VM.