<p>My team and I are new to Kubernetes and are experimenting with running a few applications on it.</p>
<p>For proof of concept, we have a running <a href="https://docs.k3s.io/" rel="noreferrer">Lightweight Kubernetes (K3s)</a> install, which presumably does not have the full range of CRDs available on a standard Kubernetes. While trying to install Envoy proxy via <a href="https://artifacthub.io/packages/helm/cloudnativeapp/envoy" rel="noreferrer">Helm Chart</a>, we ran into the below error:</p>
<pre><code># helm install my-envoy cloudnativeapp/envoy --version 1.5.0
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: resource mapping not found for name: &quot;my-envoy&quot; namespace: &quot;&quot; from &quot;&quot;: no matches for kind &quot;PodDisruptionBudget&quot; in version &quot;policy/v1beta1&quot;
ensure CRDs are installed first
</code></pre>
<p>Presumably the message <code>ensure CRDs are installed first</code> refers to components that are missing in K3s. Is there a way to get these components installed (via Helm or some other methods)?</p>

arimbun
<p>Most likely the problem is not related to missing CRDs but to the kubernetes version. I assume you are using the latest K3S version, which is <a href="https://github.com/k3s-io/k3s/releases/tag/v1.25.4%2Bk3s1" rel="noreferrer">v1.25.4</a>. <code>PodDisruptionBudget</code> was moved from <code>policy/v1beta1</code> to <code>policy/v1</code> in version <a href="https://kubernetes.io/docs/reference/using-api/deprecation-guide/#poddisruptionbudget-v125" rel="noreferrer">v1.25</a>. As the Envoy helm chart that you are using does not seem to be actively maintained, probably you will have to downgrade K3S or find a different chart.</p>
