<p>etcd:
enabled: true
name: etcd
replicaCount: 3
pdb:
create: false
image:
repository: &quot;milvusdb/etcd&quot;
tag: &quot;3.5.0-r7&quot;
pullPolicy: IfNotPresent</p>
<p>service:
type: ClusterIP
port: 2379
peerPort: 2380</p>
<p>auth:
rbac:
enabled: false</p>
<p>persistence:
enabled: true
storageClass:
accessMode: ReadWriteOnce
size: 10Gi</p>
<h2>Enable auto compaction</h2>
<h2>compaction by every 1000 revision</h2>
<h2></h2>
<p>autoCompactionMode: revision
autoCompactionRetention: &quot;1000&quot;</p>
<h2>Increase default quota to 4G</h2>
<h2></h2>
<p>extraEnvVars:</p>
<ul>
<li>name: ETCD_QUOTA_BACKEND_BYTES
value: &quot;4294967296&quot;</li>
<li>name: ETCD_HEARTBEAT_INTERVAL
value: &quot;500&quot;</li>
<li>name: ETCD_ELECTION_TIMEOUT<code>enter code here</code>
value: &quot;2500&quot;</li>
</ul>
<h2>Configuration values for the pulsar dependency</h2>
<h2>ref: <a href="https://github.com/apache/pulsar-helm-chart" rel="nofollow noreferrer">https://github.com/apache/pulsar-helm-chart</a></h2>
<p><a href="https://i.stack.imgur.com/h1hLr.png" rel="nofollow noreferrer">enter image description here</a></p>
<p>I am trying to run the milvus cluster using kubernete in ubuntu server.
I used helm menifest <a href="https://milvus-io.github.io/milvus-helm/" rel="nofollow noreferrer">https://milvus-io.github.io/milvus-helm/</a></p>
<p>Values.yaml
<a href="https://raw.githubusercontent.com/milvus-io/milvus-helm/master/charts/milvus/values.yaml" rel="nofollow noreferrer">https://raw.githubusercontent.com/milvus-io/milvus-helm/master/charts/milvus/values.yaml</a></p>
<p>I checked PersistentValumeClaim their was an error
no persistent volumes available for this claim and no storage class is set</p>

<p>This error comes because you dont have a Persistent Volume.
A pvc needs a a pv with at least the same capacity of the pvc.</p>
<p>This can be done manually or with a Volume provvisioner.</p>
<p>The most easy way someone would say is to use the local storageClass, which uses the diskspace from the node where the pod is instanciated, adds a pod affinity so that the pod starts allways on the same node and can use the volume on that disk. In your case you are using 3 replicas. Allthough its possible to start all 3 instances on the same node, this is mostlikly not what you want to achieve with Kubernetes. If that node breaks you wont have any other instance running on another node.</p>
<p>You need first to thing about the infrastructure of your cluster. Where should the data of the volumes be stored?</p>
<p>An Network File System, nfs, might be a could solution.
In this case you have an nfs somewhere in your infrastructure and all the nodes can reach it.</p>
<p>So you can create a PV which is accessible from all your node.</p>
<p>To not allocate a PV always manualy you can install a Volumeprovisioner inside your cluster.</p>
<p>I use in some cluster this one here:
<a href="https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner" rel="nofollow noreferrer">https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner</a></p>
<p>As i said you must have already an nfs and configure the provvisioner.yaml with the path.</p>
<p>it looks like this:</p>
<pre><code># patch_nfs_details.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: nfs-client-provisioner
  name: nfs-client-provisioner
spec:
  template:
    spec:
      containers:
        - name: nfs-client-provisioner
          env:
            - name: NFS_SERVER
              value: &lt;YOUR_NFS_SERVER_IP&gt;
            - name: NFS_PATH
              value: &lt;YOUR_NFS_SERVER_SHARE&gt;
      volumes:
        - name: nfs-client-root
          nfs:
            server: &lt;YOUR_NFS_SERVER_IP&gt;
            path: &lt;YOUR_NFS_SERVER_SHARE&gt;
</code></pre>
<p>If you use an nfs without provvisioner, you need to define a storageClass which is linked to your nfs.</p>
<p>There are a lot of solutions to hold persitent volumes.</p>
<p>Here you can find a list of StorageClasses:</p>
<pre><code>https://kubernetes.io/docs/concepts/storage/storage-classes/
</code></pre>
<p>At the end it depends also where your cluster is provvisioned if you are not managing it by yourself.</p>
