<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Balkrishna Pandey on Medium]]></title>
        <description><![CDATA[Stories by Balkrishna Pandey on Medium]]></description>
        <link>https://medium.com/@pandeybk?source=rss-ee59a6f4b53------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*61NQqR0mP7-eaOOIYxWYJQ.jpeg</url>
            <title>Stories by Balkrishna Pandey on Medium</title>
            <link>https://medium.com/@pandeybk?source=rss-ee59a6f4b53------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:00:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@pandeybk/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Tutorial 2- Create and Retrieve Your First Features with Red Hat OpenShift AI Feature Store]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://pandeybk.medium.com/tutorial-2-create-and-retrieve-your-first-features-with-red-hat-openshift-ai-feature-store-f9d7325233e2?source=rss-ee59a6f4b53------2"><img src="https://cdn-images-1.medium.com/max/2174/1*jk5oae82UYBmsPyvoa6RTw.png" width="2174"></a></p><p class="medium-feed-snippet">In Tutorial 1, we deployed an empty Feature Store.</p><p class="medium-feed-link"><a href="https://pandeybk.medium.com/tutorial-2-create-and-retrieve-your-first-features-with-red-hat-openshift-ai-feature-store-f9d7325233e2?source=rss-ee59a6f4b53------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://pandeybk.medium.com/tutorial-2-create-and-retrieve-your-first-features-with-red-hat-openshift-ai-feature-store-f9d7325233e2?source=rss-ee59a6f4b53------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9d7325233e2</guid>
            <category><![CDATA[redhat-openshift]]></category>
            <category><![CDATA[openshift-ai]]></category>
            <category><![CDATA[feast-feature-store]]></category>
            <category><![CDATA[feature-store]]></category>
            <category><![CDATA[red-hat-openshift-ai]]></category>
            <dc:creator><![CDATA[Balkrishna Pandey]]></dc:creator>
            <pubDate>Thu, 08 Oct 2026 19:15:23 GMT</pubDate>
            <atom:updated>2026-10-08T19:15:23.451Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Deploy and Verify Your First Feature Store on Red Hat OpenShift AI]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://pandeybk.medium.com/deploy-and-verify-your-first-feature-store-on-red-hat-openshift-ai-69df0782f696?source=rss-ee59a6f4b53------2"><img src="https://cdn-images-1.medium.com/max/1630/1*jmSWGoZ3ZrpoMNKDJAr7lw.png" width="1630"></a></p><p class="medium-feed-link"><a href="https://pandeybk.medium.com/deploy-and-verify-your-first-feature-store-on-red-hat-openshift-ai-69df0782f696?source=rss-ee59a6f4b53------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://pandeybk.medium.com/deploy-and-verify-your-first-feature-store-on-red-hat-openshift-ai-69df0782f696?source=rss-ee59a6f4b53------2</link>
            <guid isPermaLink="false">https://medium.com/p/69df0782f696</guid>
            <category><![CDATA[feast]]></category>
            <category><![CDATA[feature-store]]></category>
            <category><![CDATA[red-hat-openshift]]></category>
            <category><![CDATA[red-hat-openshift-ai]]></category>
            <dc:creator><![CDATA[Balkrishna Pandey]]></dc:creator>
            <pubDate>Tue, 06 Oct 2026 19:30:00 GMT</pubDate>
            <atom:updated>2026-10-06T19:30:00.227Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Fixing and Enabling IPv6 on macOS]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://pandeybk.medium.com/fixing-and-enabling-ipv6-on-macos-f4523cfd50d5?source=rss-ee59a6f4b53------2"><img src="https://cdn-images-1.medium.com/max/1732/1*wgkyBTh8bzMZ26haoqL_Jw.png" width="1732"></a></p><p class="medium-feed-snippet">I ran into something interesting while building a dual-stack OpenShift lab.</p><p class="medium-feed-link"><a href="https://pandeybk.medium.com/fixing-and-enabling-ipv6-on-macos-f4523cfd50d5?source=rss-ee59a6f4b53------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://pandeybk.medium.com/fixing-and-enabling-ipv6-on-macos-f4523cfd50d5?source=rss-ee59a6f4b53------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4523cfd50d5</guid>
            <category><![CDATA[macos]]></category>
            <category><![CDATA[ipv6]]></category>
            <dc:creator><![CDATA[Balkrishna Pandey]]></dc:creator>
            <pubDate>Thu, 12 Feb 2026 20:23:04 GMT</pubDate>
            <atom:updated>2026-02-12T20:23:04.909Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Serving vLLM and Granite Models on ARM with Red Hat OpenShift AI]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://pandeybk.medium.com/serving-vllm-and-granite-models-on-arm-with-red-hat-openshift-ai-0178adba550e?source=rss-ee59a6f4b53------2"><img src="https://cdn-images-1.medium.com/max/1024/1*lx1PByeCALWnHbbS8YZGmg.jpeg" width="1024"></a></p><p class="medium-feed-snippet">At the time of writing, Red Hat OpenShift AI does not officially support ARM-based deployments. This blog post serves as a temporary&#x2026;</p><p class="medium-feed-link"><a href="https://pandeybk.medium.com/serving-vllm-and-granite-models-on-arm-with-red-hat-openshift-ai-0178adba550e?source=rss-ee59a6f4b53------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://pandeybk.medium.com/serving-vllm-and-granite-models-on-arm-with-red-hat-openshift-ai-0178adba550e?source=rss-ee59a6f4b53------2</link>
            <guid isPermaLink="false">https://medium.com/p/0178adba550e</guid>
            <category><![CDATA[vllm]]></category>
            <category><![CDATA[red-hat-openshift-ai]]></category>
            <category><![CDATA[arm]]></category>
            <category><![CDATA[red-hat-openshift]]></category>
            <dc:creator><![CDATA[Balkrishna Pandey]]></dc:creator>
            <pubDate>Thu, 05 Jun 2025 21:05:47 GMT</pubDate>
            <atom:updated>2025-06-05T21:05:47.841Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Deploying OpenShift in a Simulated Disconnected Lab Using the Agent-Based Installer]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">This blog is part of a multi-post series where I walk through a full disconnected (air-gapped) OpenShift 4.16 installation using KVM&#x2026;</p><p class="medium-feed-link"><a href="https://pandeybk.medium.com/deploying-openshift-in-a-simulated-disconnected-lab-using-the-agent-based-installer-f8dfeff36990?source=rss-ee59a6f4b53------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://pandeybk.medium.com/deploying-openshift-in-a-simulated-disconnected-lab-using-the-agent-based-installer-f8dfeff36990?source=rss-ee59a6f4b53------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8dfeff36990</guid>
            <category><![CDATA[openshift-install]]></category>
            <category><![CDATA[openshift]]></category>
            <category><![CDATA[agent-based-installer-ocp]]></category>
            <dc:creator><![CDATA[Balkrishna Pandey]]></dc:creator>
            <pubDate>Mon, 21 Apr 2025 23:52:22 GMT</pubDate>
            <atom:updated>2025-05-27T15:00:13.393Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Setting Up a Local Proxy Server with Squid for OpenShift Air-Gap Simulation]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">This blog is part of a multi-post series where I walk through a full disconnected (air-gapped) OpenShift 4.16 installation using KVM&#x2026;</p><p class="medium-feed-link"><a href="https://pandeybk.medium.com/setting-up-a-local-proxy-server-with-squid-for-openshift-air-gap-simulation-c4fe05466293?source=rss-ee59a6f4b53------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://pandeybk.medium.com/setting-up-a-local-proxy-server-with-squid-for-openshift-air-gap-simulation-c4fe05466293?source=rss-ee59a6f4b53------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4fe05466293</guid>
            <category><![CDATA[squid-proxy]]></category>
            <category><![CDATA[openshift]]></category>
            <dc:creator><![CDATA[Balkrishna Pandey]]></dc:creator>
            <pubDate>Mon, 21 Apr 2025 23:39:23 GMT</pubDate>
            <atom:updated>2025-04-21T23:58:02.034Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Mirroring OpenShift and Operator Images in a Disconnected Environment]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">This blog is part of a multi-post series where I walk through a full disconnected (air-gapped) OpenShift 4.16 installation using KVM&#x2026;</p><p class="medium-feed-link"><a href="https://pandeybk.medium.com/mirroring-openshift-and-operator-images-in-a-disconnected-environment-9be3a299c364?source=rss-ee59a6f4b53------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://pandeybk.medium.com/mirroring-openshift-and-operator-images-in-a-disconnected-environment-9be3a299c364?source=rss-ee59a6f4b53------2</link>
            <guid isPermaLink="false">https://medium.com/p/9be3a299c364</guid>
            <category><![CDATA[disconnected-ocp]]></category>
            <category><![CDATA[openshift-install]]></category>
            <category><![CDATA[openshift]]></category>
            <dc:creator><![CDATA[Balkrishna Pandey]]></dc:creator>
            <pubDate>Mon, 21 Apr 2025 23:32:27 GMT</pubDate>
            <atom:updated>2025-04-24T16:42:32.459Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Setting Up a Local Mirror Registry for Disconnected OpenShift Installs]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">This blog is part of a multi-post series where I walk through a full disconnected (air-gapped) OpenShift 4.16 installation using KVM&#x2026;</p><p class="medium-feed-link"><a href="https://pandeybk.medium.com/setting-up-a-local-mirror-registry-for-disconnected-openshift-installs-9bb649e2471e?source=rss-ee59a6f4b53------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://pandeybk.medium.com/setting-up-a-local-mirror-registry-for-disconnected-openshift-installs-9bb649e2471e?source=rss-ee59a6f4b53------2</link>
            <guid isPermaLink="false">https://medium.com/p/9bb649e2471e</guid>
            <category><![CDATA[airgapped-openshift]]></category>
            <category><![CDATA[oc-mirror]]></category>
            <category><![CDATA[mirror-registry-quay]]></category>
            <dc:creator><![CDATA[Balkrishna Pandey]]></dc:creator>
            <pubDate>Mon, 21 Apr 2025 23:03:07 GMT</pubDate>
            <atom:updated>2025-05-02T17:03:24.677Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Configuring Static IP Networking for SNO with ACM SiteConfig (Blog 2)]]></title>
            <link>https://pandeybk.medium.com/configuring-static-ip-networking-for-sno-with-acm-siteconfig-blog-2-bd05d0ea9441?source=rss-ee59a6f4b53------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd05d0ea9441</guid>
            <dc:creator><![CDATA[Balkrishna Pandey]]></dc:creator>
            <pubDate>Mon, 07 Apr 2025 20:37:48 GMT</pubDate>
            <atom:updated>2025-04-08T00:32:47.045Z</atom:updated>
            <content:encoded><![CDATA[<h3>Configuring Static IP Networking for SNO with ACM SiteConfig (Part 2)</h3><p>This is a continuation of our <a href="https://medium.com/@pandeybk/automate-single-node-openshift-deployment-using-red-hat-acm-and-siteconfig-39ddcd31225c">previous guide on deploying a Single Node OpenShift (SNO)</a> cluster using Red Hat Advanced Cluster Management (ACM).</p><p>https://youtu.be/-s5P1pe8CE0</p><p>In this part, we focus specifically on <strong>configuring static networking</strong> using the ClusterInstance resource and walk through how the SiteConfig operator manages this workflow end-to-end.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*fvfYbYEqWtSaOsg4sXM1nA.png" /><figcaption>Static IP Using SiteConfig</figcaption></figure><h3>Why Static IP?</h3><p>Static IP configuration ensures predictability and control in environments where DHCP may be limited or where precise network mapping is required for security and access reasons. When provisioning clusters using ACM and the Assisted Installer, static IPs are configured declaratively inside the ClusterInstance.</p><h3>High-Level Workflow</h3><ol><li><strong>ClusterInstance</strong> is applied.</li><li>ACM SiteConfig operator uses the specified template.</li><li>Template expands into Kubernetes-native resources like BareMetalHost and NMStateConfig.</li><li>The Assisted Installer leverages these resources to configure and provision the node.</li></ol><h3>Step-by-Step: Static Network Configuration</h3><h3>Step 1: Create and Boot the SNO Virtual Machine (Optional, this is just baremetal simulation)</h3><p>To simulate a bare metal environment with a static IP, create a virtual machine using the following virt-install script. Make sure the discovery ISO is already mounted or preconfigured in the image:</p><pre>export HUB_CLUSTER_NAME=&quot;hubztp&quot;<br>export CLUSTER_NAME=&quot;sno02&quot;<br>export NAME_BRIDGE=&quot;br0&quot;<br>export UUID=&quot;deed1e55-fe11-f0e5-0dd5-babb1ed1a011&quot;<br>export MAC=&quot;00:00:00:00:00:11&quot;</pre><pre>sudo qemu-img create -f qcow2 /opt/ssd/${HUB_CLUSTER_NAME}/${CLUSTER_NAME}.qcow2 200G</pre><pre>sudo virt-install \<br>  --name=${HUB_CLUSTER_NAME}-${CLUSTER_NAME} \<br>  --uuid=${UUID} \<br>  --ram=33384 \<br>  --vcpus=8 \<br>  --cpu host-passthrough \<br>  --os-type linux \<br>  --os-variant rhel8.0 \<br>  --noreboot \<br>  --events on_reboot=restart \<br>  --noautoconsole \<br>  --boot hd,cdrom \<br>  --import \<br>  --disk path=/opt/ssd/${HUB_CLUSTER_NAME}/${CLUSTER_NAME}.qcow2,size=20 \<br>  --network type=direct,source=${NAME_BRIDGE},mac=${MAC},source_mode=bridge,model=virtio</pre><h3>Step 2: Update DNS for the SNO Cluster (Use your DNS Server)</h3><p>To ensure that the cluster can resolve and register correctly, update your DNS zone file to include the entries for ai-sno-cluster002.</p><p>Here is an example zone file snippet from /var/named/balk.ocp.local.zone:</p><pre>$TTL 86400<br>@   IN  SOA ns1.balk.ocp.local. admin.balk.ocp.local. (<br>        2025040301 3600 1800 1209600 86400 )<br><br>    IN NS ns1.balk.ocp.local.<br><br>; DNS Server<br>ns1.balk.ocp.local.           IN A 192.168.7.126<br><br>; Hub cluster entries<br>api.hubztp.balk.ocp.local.    IN A 192.168.7.219<br>*.apps.hubztp.balk.ocp.local. IN A 192.168.7.220<br><br>; SNO cluster entries<br>api.ai-sno-cluster001.balk.ocp.local. IN A 192.168.7.10<br>*.apps.ai-sno-cluster001.balk.ocp.local. IN A 192.168.7.10<br><br>; SNO cluster entries<br>api.ai-sno-cluster002.balk.ocp.local. IN A 192.168.7.11<br>*.apps.ai-sno-cluster002.balk.ocp.local. IN A 192.168.7.11</pre><p>Restart the DNS service to apply the changes:</p><pre>sudo systemctl restart named</pre><h3>3. Create Required Namespace and Secrets</h3><pre>apiVersion: v1<br>kind: Namespace<br>metadata:<br>  name: ai-sno-cluster002</pre><pre>apiVersion: v1<br>kind: Secret<br>metadata:<br>  name: ai-bmh-secret<br>  namespace: ai-sno-cluster002<br>data:<br>  username: YWRtaW4K # user you username and password<br>  password: YWRtaW4K<br>type: Opaque</pre><pre>apiVersion: v1<br>kind: Secret<br>metadata:<br>  name: pull-secret<br>  namespace: ai-sno-cluster002<br>data:<br>  .dockerconfigjson: &lt;base64-encoded-pull-secret&gt;<br>type: kubernetes.io/dockerconfigjson</pre><h3>4. Define ClusterInstance With Static Networking</h3><pre>apiVersion: siteconfig.open-cluster-management.io/v1alpha1<br>kind: ClusterInstance<br>metadata:<br>  name: ai-sno-cluster002<br>  namespace: ai-sno-cluster002<br>spec:<br>  clusterName: ai-sno-cluster002<br>  clusterImageSetNameRef: img4.17.4-x86-64-appsub<br>  baseDomain: balk.ocp.local<br>  machineNetwork:<br>    - cidr: 192.168.4.0/22<br>  networkType: OVNKubernetes<br>  sshPublicKey: &lt;your-ssh-key&gt;<br>  pullSecretRef:<br>    name: pull-secret<br>  templateRefs:<br>    - name: ai-cluster-templates-v1<br>      namespace: open-cluster-management<br>  nodes:<br>    - role: master<br>      hostName: ai-sno-cluster002<br>      bmcAddress: redfish-virtualmedia+http://192.168.7.126:8000/redfish/v1/Systems/deed1e55-fe11-f0e5-0dd5-babb1ed1a011<br>      bmcCredentialsName:<br>        name: ai-bmh-secret<br>      bootMACAddress: &quot;00:00:00:00:00:11&quot;<br>      bootMode: UEFI<br>      automatedCleaningMode: disabled<br>      cpuArchitecture: x86_64<br>      templateRefs:<br>        - name: ai-node-templates-v1<br>          namespace: open-cluster-management<br>      nodeNetwork:<br>        interfaces:<br>          - name: ens1s0<br>            macAddress: &quot;00:00:00:00:00:11&quot;<br>        config:<br>          interfaces:<br>            - name: ens1s0<br>              type: ethernet<br>              state: up<br>              ipv4:<br>                enabled: true<br>                dhcp: false<br>                address:<br>                  - ip: 192.168.7.11<br>                    prefix-length: 24<br>              ipv6:<br>                enabled: false<br>          dns-resolver:<br>            config:<br>              search:<br>                - balk.ocp.local<br>              server:<br>                - 192.168.7.126<br>                - 8.8.8.8<br>          routes:<br>            config:<br>              - destination: 0.0.0.0/0<br>                next-hop-address: 192.168.4.1<br>                next-hop-interface: ens1s0<br>                table-id: 254</pre><h3>How Static Networking Gets Applied</h3><p>To understand how the static networking configuration is realized, it’s important to look at the node template being referenced in the ClusterInstance. You can inspect the template using the following command:</p><pre>oc get cm ai-node-templates-v1 -n open-cluster-management -o yaml | grep NMStateConfig -A13</pre><p>Output:</p><pre>Output:<br>  NMStateConfig: |-<br>    {{ if .SpecialVars.CurrentNode.NodeNetwork }}<br>    apiVersion: agent-install.openshift.io/v1beta1<br>    kind: NMStateConfig<br>    metadata:<br>      annotations:<br>        siteconfig.open-cluster-management.io/sync-wave: &quot;1&quot;<br>      name: &quot;{{ .SpecialVars.CurrentNode.HostName }}&quot;<br>      namespace: &quot;{{ .Spec.ClusterName }}&quot;<br>      labels:<br>        nmstate-label: &quot;{{ .Spec.ClusterName }}&quot;<br>    spec:<br>      config:<br>    {{ .SpecialVars.CurrentNode.NodeNetwork.NetConfig | toYaml | indent 4}}<br>      interfaces:<br>    {{ .SpecialVars.CurrentNode.NodeNetwork.Interfaces | toYaml | indent 4 }}<br>    {{ end }}</pre><p>This template includes logic to generate both BareMetalHost and NMStateConfig resources. Below is the snippet responsible for creating the NMStateConfig:</p><p>The real power of ACM lies in the templates used to generate Kubernetes resources automatically. In the example above, we referenced a node template ai-node-templates-v1. This contains instructions for generating the BareMetalHost and the corresponding NMStateConfig resource.</p><pre>oc get NMStateConfig -n ai-sno-cluster002   ai-sno-cluster002 -o yaml</pre><p>Output:</p><pre># NMStateConfig from Template Expansion<br>apiVersion: agent-install.openshift.io/v1beta1<br>kind: NMStateConfig<br>metadata:<br>  name: ai-sno-cluster002<br>  namespace: ai-sno-cluster002<br>spec:<br>  config:<br>    dns-resolver:<br>      config:<br>        search:<br>        - balk.ocp.local<br>        server:<br>        - 192.168.7.126<br>        - 8.8.8.8<br>    interfaces:<br>    - ipv4:<br>        address:<br>        - ip: 192.168.7.11<br>          prefix-length: 24<br>        dhcp: false<br>        enabled: true<br>      ipv6:<br>        enabled: false<br>      name: ens1s0<br>      state: up<br>      type: ethernet<br>    routes:<br>      config:<br>      - destination: 0.0.0.0/0<br>        next-hop-address: 192.168.4.1<br>        next-hop-interface: ens1s0<br>        table-id: 254<br>  interfaces:<br>  - macAddress: &quot;00:00:00:00:00:11&quot;<br>    name: ens1s0</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd05d0ea9441" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automate Single Node OpenShift Deployment Using Red Hat ACM and SiteConfig (Part 1)]]></title>
            <link>https://pandeybk.medium.com/automate-single-node-openshift-deployment-using-red-hat-acm-and-siteconfig-39ddcd31225c?source=rss-ee59a6f4b53------2</link>
            <guid isPermaLink="false">https://medium.com/p/39ddcd31225c</guid>
            <dc:creator><![CDATA[Balkrishna Pandey]]></dc:creator>
            <pubDate>Mon, 07 Apr 2025 17:27:08 GMT</pubDate>
            <atom:updated>2025-04-07T20:38:29.479Z</atom:updated>
            <content:encoded><![CDATA[<p>In this blog post, I’ll walk through a complete and streamlined process for deploying a Single Node OpenShift (SNO) cluster using Red Hat Advanced Cluster Management (ACM), SiteConfig, and kvm virtual machines (VMs) exposed using <a href="https://github.com/openstack/sushy-tools">sushy tool</a> to simulate a bare metal environment. This guide is designed for users who want to automate and standardize OpenShift deployments across environments using ACM.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ml97jCXCw2_p0TUUMEgCRQ.png" /></figure><p>This blog is to support this youtube video, it makes easy to copy/paste the content.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FO6y-2qkvOPg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DO6y-2qkvOPg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FO6y-2qkvOPg%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/0f6036fbf79bd8f2f4acff6f751299d7/href">https://medium.com/media/0f6036fbf79bd8f2f4acff6f751299d7/href</a></iframe><h3>Prerequisites</h3><ul><li>A working OpenShift hub cluster</li><li>Access to the OpenShift CLI (oc)</li><li>DNS server with the ability to manage zone files (e.g., bind), feel free to use you dns server.</li><li>libvirt and virsh installed for VM management, this is only for simulation if you have extra baremetal machine you can technically follow the same guide</li></ul><h3>Step 1: Install Red Hat Advanced Cluster Management (ACM)</h3><p>To begin, install the ACM operator via the OpenShift Console:</p><ol><li>Go to <strong>Operators &gt; OperatorHub</strong>, then search for “Advanced Cluster Management for Kubernetes”.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yus2LZXXh8gLONg1mCuyGg.png" /></figure><p>2. Click <strong>Install</strong>, choose the desired channel (e.g., release-2.13) and version.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PXP0GPjPsI9cqp7C6wTYLw.png" /></figure><p>3. Select <strong>A specific namespace on the cluster</strong> and use the recommended open-cluster-management namespace.</p><p>4. Set <strong>Update approval</strong> to either Automatic or Manual, then click <strong>Install</strong>.</p><p>5. Create the MultiClusterHub resource:</p><pre>apiVersion: operator.open-cluster-management.io/v1<br>kind: MultiClusterHub<br>metadata:<br>  name: multiclusterhub<br>  namespace: open-cluster-management<br>spec: {}</pre><p>Apply it using:</p><pre>oc apply -f multiclusterhub.yaml</pre><p>Wait until all pods in the open-cluster-management namespace are up and running.</p><h3>Step 2: Enable the SiteConfig Operator</h3><p>Check if SiteConfig is already enabled:</p><pre>oc get multiclusterhubs.operator.open-cluster-management.io multiclusterhub -n open-cluster-management -o yaml | grep siteconfig -B2 -A2</pre><p>If not enabled, patch it:</p><pre>oc patch multiclusterhubs.operator.open-cluster-management.io multiclusterhub -n open-cluster-management --type json --patch &#39;[{&quot;op&quot;: &quot;add&quot;, &quot;path&quot;:&quot;/spec/overrides/components/-&quot;, &quot;value&quot;: {&quot;name&quot;:&quot;siteconfig&quot;,&quot;enabled&quot;: true}}]&#39;</pre><p>Verify the operator pod is running:</p><pre>oc get po -n open-cluster-management | grep siteconfig</pre><p>Check for default install templates:</p><pre>oc get cm -n open-cluster-management | grep templates</pre><h3>Step 3: Configure AgentServiceConfig for Assisted Installer</h3><p>Before creating the AgentServiceConfig, you also need to configure the Provisioning resource to enable the Bare Metal Operator to function properly across all namespaces.</p><h3>Check for the Provisioning Resource</h3><pre>oc get provisioning</pre><p>If it exists, patch it with:</p><pre>oc patch provisioning provisioning-configuration --type merge -p &#39;{&quot;spec&quot;:{&quot;watchAllNamespaces&quot;: true }}&#39;</pre><p>If it does not exist, create it with:</p><pre>apiVersion: metal3.io/v1alpha1<br>kind: Provisioning<br>metadata:<br>  name: provisioning-configuration<br>spec:<br>  provisioningNetwork: &quot;Disabled&quot;<br>  watchAllNamespaces: true</pre><p>Apply it:</p><pre>oc apply -f provisioning.yaml</pre><p>Then proceed with creating the AgentServiceConfig as shown below:</p><pre>apiVersion: agent-install.openshift.io/v1beta1<br>kind: AgentServiceConfig<br>metadata:<br>  name: agent<br>spec:<br>  databaseStorage:<br>    accessModes:<br>      - ReadWriteOnce<br>    resources:<br>      requests:<br>        storage: 10Gi<br>  filesystemStorage:<br>    accessModes:<br>      - ReadWriteOnce<br>    resources:<br>      requests:<br>        storage: 50Gi<br>  imageStorage:<br>    accessModes:<br>      - ReadWriteOnce<br>    resources:<br>      requests:<br>        storage: 50Gi<br>  osImages:<br>    - cpuArchitecture: x86_64<br>      openshiftVersion: &#39;4.17&#39;<br>      rootFSUrl: &#39;https://mirror.openshift.com/pub/openshift-v4/x86_64/dependencies/rhcos/pre-release/latest-4.17/rhcos-4.17.0-ec.3-x86_64-live-rootfs.x86_64.img&#39;<br>      url: &#39;https://mirror.openshift.com/pub/openshift-v4/x86_64/dependencies/rhcos/pre-release/latest-4.17/rhcos-4.17.0-ec.3-x86_64-live.x86_64.iso&#39;<br>      version: 417.94.202410090854-0<br>    - cpuArchitecture: x86_64<br>      openshiftVersion: &#39;4.18&#39;<br>      rootFSUrl: &#39;https://mirror.openshift.com/pub/openshift-v4/x86_64/dependencies/rhcos/pre-release/4.18.0-rc.2/rhcos-4.18.0-rc.2-x86_64-live-rootfs.x86_64.img&#39;<br>      url: &#39;https://mirror.openshift.com/pub/openshift-v4/x86_64/dependencies/rhcos/pre-release/4.18.0-rc.2/rhcos-4.18.0-rc.2-x86_64-live.x86_64.iso&#39;<br>      version: 418.94.202411221729-0</pre><p>Apply it using:</p><pre>oc apply -f agentserviceconfig.yaml</pre><p>This configures the backend services required for Assisted Installer to function. Once applied, the service will generate Discovery Images and handle provisioning through the ACM console.</p><h3>Step 4: Configure DNS</h3><blockquote>Note: Managed cluster should able to communicate with HUB cluster and resolve DNS and vice-versa otherwise installtion will fail.</blockquote><p>Create a new zone file: /var/named/ai-sno-cluster001.balk.ocp.local.zone</p><pre>$TTL 86400<br>@   IN  SOA ns1.balk.ocp.local. admin.balk.ocp.local. (<br>        2025040301 3600 1800 1209600 86400 )<br><br>    IN NS ns1.balk.ocp.local.<br><br>; DNS Server<br>ns1.balk.ocp.local.           IN A 192.168.7.126<br><br>; Hub cluster entries<br>api.hubztp.balk.ocp.local.    IN A 192.168.7.219<br>*.apps.hubztp.balk.ocp.local. IN A 192.168.7.220<br><br>; SNO cluster entries<br>api.ai-sno-cluster001.balk.ocp.local. IN A 192.168.7.10<br>*.apps.ai-sno-cluster001.balk.ocp.local. IN A 192.168.7.10</pre><p>Update /etc/named.conf to load the new zone:</p><pre>zone &quot;balk.ocp.local&quot; IN {<br>    type master;<br>    file &quot;balk.ocp.local.zone&quot;;<br>};</pre><p>Restart DNS:</p><pre>systemctl restart named</pre><h3>Step 5: Create a VM to Simulate Bare Metal Using virsh</h3><blockquote>Note: If you are using Baremetal machine this step is not required, for now I am using sushy tools to simulate the baremetal scenario.</blockquote><pre>export HUB_CLUSTER_NAME=&quot;hubztp&quot;<br>export CLUSTER_NAME=&quot;sno01&quot;<br>export NAME_BRIDGE=&quot;br0&quot;<br>export UUID=&quot;deed1e55-fe11-f0e5-0dd5-babb1ed1a010&quot;<br>export MAC=&quot;00:00:00:00:00:10&quot;<br><br>sudo qemu-img create -f qcow2 /opt/ssd/${HUB_CLUSTER_NAME}/${CLUSTER_NAME}.qcow2 200G<br><br>sudo virt-install \<br>  --name=${HUB_CLUSTER_NAME}-${CLUSTER_NAME} \<br>  --uuid=${UUID} \<br>  --ram=65536 \<br>  --vcpus=16 \<br>  --cpu host-passthrough \<br>  --os-type linux \<br>  --os-variant rhel8.0 \<br>  --noreboot \<br>  --events on_reboot=restart \<br>  --noautoconsole \<br>  --boot hd,cdrom \<br>  --import \<br>  --disk path=/opt/ssd/${HUB_CLUSTER_NAME}/${CLUSTER_NAME}.qcow2,size=20 \<br>  --network type=direct,source=${NAME_BRIDGE},mac=${MAC},source_mode=bridge,model=virtio</pre><p>Ensure the VM boots using the Discovery ISO and matches the MAC address and hostname defined in your cluster config.</p><h3>Step 6: Prepare Namespace, Pull Secret, and BMC Secret</h3><p>Before creating the ClusterInstance, we need to create the required namespace and secrets:</p><h4>Create Namespace</h4><pre>oc create ns ai-sno-cluster001</pre><h4>Create Pull Secret</h4><p>Replace &lt;pull-secret.json&gt; with your actual file path:</p><pre>oc create secret generic pull-secret \<br>  -n ai-sno-cluster001 \<br>  --from-file=.dockerconfigjson=&lt;pull-secret.json&gt; \<br>  --type=kubernetes.io/dockerconfigjson</pre><h4>Create BMC Credentials Secret</h4><pre>oc create secret generic ai-bmh-secret \<br>  -n ai-sno-cluster001 \<br>  --from-literal=username=admin \<br>  --from-literal=password=your-password</pre><h3>Step 7: Define the ClusterInstance YAML</h3><blockquote><strong>Note:</strong> If you delete the ClusterInstance object, it will also delete the associated namespace. This means you must recreate the namespace and its required secrets (pull secret, BMC credentials, etc.) before applying a new ClusterInstance. Failing to do so will result in errors during provisioning.</blockquote><pre>apiVersion: siteconfig.open-cluster-management.io/v1alpha1<br>kind: ClusterInstance<br>metadata:<br>  name: ai-sno-cluster001<br>  namespace: ai-sno-cluster001<br>spec:<br>  cpuPartitioningMode: None<br>  clusterName: ai-sno-cluster001<br>  clusterImageSetNameRef: img4.17.4-x86-64-appsub<br>  machineNetwork:<br>    - cidr: 192.168.4.0/22<br>  networkType: OVNKubernetes<br>  sshPublicKey: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCrRj8UgTVFA1/1okryUGAdZ4kKAE0snw4CUp7lhCXAiB3HI2ynIrQQIn4ddzHkUjGU+tojvTmZnDWR5Gfi53BWNsByFUPPziH+XSp+LWWyYRIFPFpSBI22IQknywSaDs+e7KRiM/axFHVfGpuNRxQ9BYh9wO/xOhe4VAqQhs3M1geTiDKvwcaR77b0r2vNNuqD/6YlMaeYKy8rg6875K35BZgn+6RH1lqK/he2/uQWBhneVskncs5EUv9tSvTC4Tpg9F1LPHGB4CZaoOqB/N7Sb9goIRGjZwe9gsijnjuegbAJfuju2MG9AyNaD95zjU2kHB+tZ9SBijjvMvRdUauWj0PFypv3qb5/lUfMN2G4cSFuBktlV5YnfdP4jRCCakzbdedBG8A/711lE5IqUY464bw6M1f3uukSCvGpSEbmvzCrs2E3ZeUzxvdOyw/N5uUElL0Hzu+m5v9PYoh0D1ip7vxeAmOf9kb5aW3cO0Es8hVRD21EZDZmbvB19fdk770= bkpandey@Balkrishnas-MacBook-Pro.local<br>  nodes:<br>    - automatedCleaningMode: disabled<br>      nodeNetwork:<br>        config:<br>          dns-resolver:<br>            config:<br>              search:<br>                - balk.ocp.local<br>              server:<br>                - 192.168.7.126<br>          interfaces:<br>            - ipv4:<br>                dhcp: true<br>                enabled: true<br>              name: ens1s0<br>              state: up<br>              type: ethernet<br>          routes:<br>            config:<br>              - destination: 0.0.0.0/0<br>                next-hop-address: 192.168.4.1<br>                next-hop-interface: ens1s0<br>                table-id: 254<br>        interfaces:<br>          - macAddress: &#39;00:00:00:00:00:10&#39;<br>            name: ens1s0<br>      bmcCredentialsName:<br>        name: ai-bmh-secret<br>      ironicInspect: &#39;&#39;<br>      hostName: ai-sno-cluster001<br>      bootMode: UEFI<br>      role: master<br>      bootMACAddress: &#39;00:00:00:00:00:10&#39;<br>      templateRefs:<br>        - name: ai-node-templates-v1<br>          namespace: open-cluster-management<br>      cpuArchitecture: x86_64<br>      bmcAddress: &#39;redfish-virtualmedia+http://192.168.7.126:8000/redfish/v1/Systems/deed1e55-fe11-f0e5-0dd5-babb1ed1a010&#39;<br>  baseDomain: balk.ocp.local<br>  holdInstallation: false<br>  templateRefs:<br>    - name: ai-cluster-templates-v1<br>      namespace: open-cluster-management<br>  cpuArchitecture: x86_64<br>  pullSecretRef:<br>    name: pull-secret</pre><p>Apply the YAML:</p><pre>oc apply -f clusterinstance.yaml</pre><p>Monitor the deployment from the ACM console. Once the node reboots and joins, the cluster will be installed and visible in the Clusters tab.</p><p>For a full visual walkthrough, check out the <a href="https://youtu.be/O6y-2qkvOPg">video on the Goglides</a> channel.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39ddcd31225c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>