<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: K8S Multi storage works load balancing in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/K8S-Multi-storage-works-load-balancing/m-p/170111#M39105</link>
    <description>&lt;P&gt;Your best bet is to cluster all of your nodes so you have one big namespace for all of your loads. Then, use Trident and perhaps rebalance the loads as they develop by moving the volumes between aggregates. Loads will probably vary too much to be able to guess at where they should be placed at creation time.&amp;nbsp; Moving the volumes used by Trident is mostly unproblematic as Trident only communicates with the SVM using volumes (and qtrees with the correct backend driver), so it doesn't matter which aggregate they are on.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 20 Sep 2021 18:54:15 GMT</pubDate>
    <dc:creator>shamz</dc:creator>
    <dc:date>2021-09-20T18:54:15Z</dc:date>
    <item>
      <title>K8S Multi storage works load balancing</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/K8S-Multi-storage-works-load-balancing/m-p/169716#M38981</link>
      <description>&lt;P&gt;I'd want to know , how to work load balancing&amp;nbsp; multipul storage with Kubernetes&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have 2 FAS8200 Storage without cluster, and 1 FAS8300 Storage&lt;/P&gt;&lt;P&gt;1 kubernetes master node and 100~ worker nodes&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are going to build a service using a total of 3 storage units.&lt;/P&gt;&lt;P&gt;I am planning to use iscsi, and I am curious how loadbalancing is performed when generating pv in k8s at this time.&lt;/P&gt;&lt;P&gt;I want to use the capacity of the three storage units as evenly as possible.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 10:15:12 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/K8S-Multi-storage-works-load-balancing/m-p/169716#M38981</guid>
      <dc:creator>sjlee</dc:creator>
      <dc:date>2025-06-04T10:15:12Z</dc:date>
    </item>
    <item>
      <title>Re: K8S Multi storage works load balancing</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/K8S-Multi-storage-works-load-balancing/m-p/170111#M39105</link>
      <description>&lt;P&gt;Your best bet is to cluster all of your nodes so you have one big namespace for all of your loads. Then, use Trident and perhaps rebalance the loads as they develop by moving the volumes between aggregates. Loads will probably vary too much to be able to guess at where they should be placed at creation time.&amp;nbsp; Moving the volumes used by Trident is mostly unproblematic as Trident only communicates with the SVM using volumes (and qtrees with the correct backend driver), so it doesn't matter which aggregate they are on.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Sep 2021 18:54:15 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/K8S-Multi-storage-works-load-balancing/m-p/170111#M39105</guid>
      <dc:creator>shamz</dc:creator>
      <dc:date>2021-09-20T18:54:15Z</dc:date>
    </item>
  </channel>
</rss>

