القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when you need to understand the physical servers, their operating systems, or hardware specifications in the homelab.
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.
Use when you need to understand or configure the DNS setup for the homelab and the OKD cluster, including Pi-hole records.
Use when you need to understand the homelab's network topology, IP ranges, gateway, or DNS server locations.
Use when managing or troubleshooting the Nginx-based load balancer (okd-lb) for the OKD cluster.
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.
| name | openshift-provisioning-workflow |
| description | 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. |
This skill covers what is done at a high level for setting up our OKD cluster. It's simple and focuses on the main steps.
All of these tasks are done through the Makefile in the okd/ directory. The Makefile does the heavy lifting for us by running bash scripts and Ansible playbooks behind the scenes.
The openshift-installer version used when creating the ISO is very important. Each OpenShift/OKD release comes with an openshift-installer binary specific to that version. The version of OKD has a 1-1 relationship with the openshift-installer.
make update-dns.
homelab-dns-context skill for more context on the dns setup.openshift-api-loadbalancer skill for more context on the load balancer setup.openshift-installer.install-config and an agent-assisted installer config. This is done for us in the makefile (via make build or make agent-iso, however, make build is prefered).openshift-installer binary to create an ISO that will be used by all 3 of the VMs that act as nodes (via make build).make copy-iso).
homelab-hardware-context skill for more context on the server.make start-vms).
openshift-node-setup skill for more context on the nodes.And boom! Our cluster has our nodes, the DNS setup, and the API load balancer setup.