deploy: 6d76ada

quickstart-metal3.html

@@ -516,7 +516,7 @@
 % kubectl get bmh
 NAME             STATE       CONSUMER   ONLINE   ERROR   AGE
 controlplane-0   available              false            15m
-worker-0         available              false            15m</pre></div></section></section><section class="sect1" id="id-known-issues" data-id-title="Known issues"><div class="titlepage"><div><div><div class="title-container"><h2 class="title"><span class="title-number-name"><span class="title-number">1.4 </span><span class="title-name">Known issues</span></span> <a title="Permalink" class="permalink" href="quickstart-metal3.html#id-known-issues">#</a></h2><div class="icons"><a target="_blank" class="icon-reportbug" title="Report an issue"> </a></div></div></div></div></div><div class="itemizedlist"><ul class="itemizedlist"><li class="listitem"><p>The upstream <a class="link" href="https://github.com/metal3-io/ip-address-manager" target="_blank">IP Address Management controller</a> is currently not supported, because it’s not yet compatible with our choice of network configuration tooling and first-boot toolchain in SLEMicro.</p></li><li class="listitem"><p>Relatedly, the IPAM resources and Metal3DataTemplate networkData fields are not currently supported.</p></li><li class="listitem"><p>Only deployment via redfish-virtualmedia is currently supported.</p></li><li class="listitem"><p>Deployed clusters are not currently imported into Rancher</p></li><li class="listitem"><p>Due to disabling the Rancher embedded CAPI controller, a management cluster configured for Metal<sup>3</sup> as described above cannot also be used for other cluster provisioning methods such as Elemental (<a class="xref" href="components-elemental.html" title="Chapter 12. Elemental">Chapter 12, <em>Elemental</em></a>)</p></li></ul></div></section><section class="sect1" id="id-planned-changes" data-id-title="Planned changes"><div class="titlepage"><div><div><div class="title-container"><h2 class="title"><span class="title-number-name"><span class="title-number">1.5 </span><span class="title-name">Planned changes</span></span> <a title="Permalink" class="permalink" href="quickstart-metal3.html#id-planned-changes">#</a></h2><div class="icons"><a target="_blank" class="icon-reportbug" title="Report an issue"> </a></div></div></div></div></div><div class="itemizedlist"><ul class="itemizedlist"><li class="listitem"><p>Deployed clusters imported into Rancher, this is planned via <a class="link" href="https://turtles.docs.rancher.com/" target="_blank">Rancher Turtles</a> in future</p></li><li class="listitem"><p>Aligning with Rancher Turtles is also expected to remove the requirement to disable the Rancher embedded CAPI, so other cluster methods should be possible via the management cluster.</p></li><li class="listitem"><p>Enable support of the IPAM resources and configuration via networkData fields</p></li></ul></div></section><section class="sect1" id="id-additional-resources" data-id-title="Additional resources"><div class="titlepage"><div><div><div class="title-container"><h2 class="title"><span class="title-number-name"><span class="title-number">1.6 </span><span class="title-name">Additional resources</span></span> <a title="Permalink" class="permalink" href="quickstart-metal3.html#id-additional-resources">#</a></h2><div class="icons"><a target="_blank" class="icon-reportbug" title="Report an issue"> </a></div></div></div></div></div><p>The ATIP Documentation (<a class="xref" href="atip.html" title="Chapter 30. SUSE Adaptive Telco Infrastructure Platform (ATIP)">Chapter 30, <em>SUSE Adaptive Telco Infrastructure Platform (ATIP)</em></a>) has examples of more advanced usage of Metal<sup>3</sup> for telco use-cases.</p><section class="sect2" id="id-single-node-configuration" data-id-title="Single-node configuration"><div class="titlepage"><div><div><div class="title-container"><h3 class="title"><span class="title-number-name"><span class="title-number">1.6.1 </span><span class="title-name">Single-node configuration</span></span> <a title="Permalink" class="permalink" href="quickstart-metal3.html#id-single-node-configuration">#</a></h3><div class="icons"><a target="_blank" class="icon-reportbug" title="Report an issue"> </a></div></div></div></div></div><p>For test/PoC environments where the management cluster is a single node, it is possible to avoid the requirement for an additional floating IP managed via MetalLB.</p><p>In this mode, the endpoint for the management cluster APIs is the IP of the management cluster, therefore it should be reserved when using DHCP
+worker-0         available              false            15m</pre></div></section></section><section class="sect1" id="id-known-issues" data-id-title="Known issues"><div class="titlepage"><div><div><div class="title-container"><h2 class="title"><span class="title-number-name"><span class="title-number">1.4 </span><span class="title-name">Known issues</span></span> <a title="Permalink" class="permalink" href="quickstart-metal3.html#id-known-issues">#</a></h2><div class="icons"><a target="_blank" class="icon-reportbug" title="Report an issue"> </a></div></div></div></div></div><div class="itemizedlist"><ul class="itemizedlist"><li class="listitem"><p>The upstream <a class="link" href="https://github.com/metal3-io/ip-address-manager" target="_blank">IP Address Management controller</a> is currently not supported, because it’s not yet compatible with our choice of network configuration tooling and first-boot toolchain in SLEMicro.</p></li><li class="listitem"><p>Relatedly, the IPAM resources and Metal3DataTemplate networkData fields are not currently supported.</p></li><li class="listitem"><p>Only deployment via redfish-virtualmedia is currently supported.</p></li></ul></div></section><section class="sect1" id="id-planned-changes" data-id-title="Planned changes"><div class="titlepage"><div><div><div class="title-container"><h2 class="title"><span class="title-number-name"><span class="title-number">1.5 </span><span class="title-name">Planned changes</span></span> <a title="Permalink" class="permalink" href="quickstart-metal3.html#id-planned-changes">#</a></h2><div class="icons"><a target="_blank" class="icon-reportbug" title="Report an issue"> </a></div></div></div></div></div><div class="itemizedlist"><ul class="itemizedlist"><li class="listitem"><p>Enable support of the IPAM resources and configuration via networkData fields</p></li></ul></div></section><section class="sect1" id="id-additional-resources" data-id-title="Additional resources"><div class="titlepage"><div><div><div class="title-container"><h2 class="title"><span class="title-number-name"><span class="title-number">1.6 </span><span class="title-name">Additional resources</span></span> <a title="Permalink" class="permalink" href="quickstart-metal3.html#id-additional-resources">#</a></h2><div class="icons"><a target="_blank" class="icon-reportbug" title="Report an issue"> </a></div></div></div></div></div><p>The ATIP Documentation (<a class="xref" href="atip.html" title="Chapter 30. SUSE Adaptive Telco Infrastructure Platform (ATIP)">Chapter 30, <em>SUSE Adaptive Telco Infrastructure Platform (ATIP)</em></a>) has examples of more advanced usage of Metal<sup>3</sup> for telco use-cases.</p><section class="sect2" id="id-single-node-configuration" data-id-title="Single-node configuration"><div class="titlepage"><div><div><div class="title-container"><h3 class="title"><span class="title-number-name"><span class="title-number">1.6.1 </span><span class="title-name">Single-node configuration</span></span> <a title="Permalink" class="permalink" href="quickstart-metal3.html#id-single-node-configuration">#</a></h3><div class="icons"><a target="_blank" class="icon-reportbug" title="Report an issue"> </a></div></div></div></div></div><p>For test/PoC environments where the management cluster is a single node, it is possible to avoid the requirement for an additional floating IP managed via MetalLB.</p><p>In this mode, the endpoint for the management cluster APIs is the IP of the management cluster, therefore it should be reserved when using DHCP
 or statically configured to ensure the management cluster IP does not change - referred to as <code class="literal">&lt;MANAGEMENT_CLUSTER_IP&gt;</code> below.</p><p>To enable this scenario the metal3 chart values required are as follows:</p><div class="verbatim-wrap highlight yaml"><pre class="screen">global:
   ironicIP: &lt;MANAGEMENT_CLUSTER_IP&gt;
 metal3-ironic: