<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Machine API :: Tag :: Kubernetes training</title><link>https://k8s-school.fr/labs/k8s/en/tags/machine-api/index.html</link><description/><generator>Hugo</generator><language>en</language><copyright>Copyright (c) 2025 Fabrice Jammes - Licensed under CC BY-SA 4.0</copyright><lastBuildDate>Wed, 21 Oct 2026 08:00:00 +0200</lastBuildDate><atom:link href="https://k8s-school.fr/labs/k8s/en/tags/machine-api/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenShift MachineSets and availability zones</title><link>https://k8s-school.fr/labs/k8s/en/1_labs/openshift-machineset/index.html</link><pubDate>Wed, 21 Oct 2026 08:00:00 +0200</pubDate><guid>https://k8s-school.fr/labs/k8s/en/1_labs/openshift-machineset/index.html</guid><description>Objective On an OpenShift cluster installed with IPI (installer-provisioned infrastructure), the Machine API manages the nodes like pods: a MachineSet keeps a number of Machines, and each Machine is a cloud VM which becomes a Node. In this lab you will:
Find the MachineSets created by the installer, one per availability zone Create your own MachineSet in a given zone, and scale it up Follow a Machine from the VM creation to the Node, and schedule a pod on it Understand how a MachineSet selects its Machines, with a classic mistake Complete this lab in 60 minutes: creating an Azure VM takes 5 to 10 minutes.</description></item></channel></rss>