O. Matskiv

@Ab-hishek we have not yet decided if we want to implement this, so for now we will leave it unassigned.

@Ab-hishek Are you still working on this issue? If you got blocked and need help, please don't hesitate to reach out to us in vcluster channel in [our Slack](https://slack.loft.sh/).

@Ab-hishek Where are you with regards to this issue? We will implement it if you are busy with other things. :slightly_smiling_face:

@Chakravarti-Baratam to answer your question - `whether we can use CRD in vcluster without deploying the same CRD in the host cluster?` - it depends. Most of the time CRDs...

Now we have another an alternative to writing a plugin with the SDK, you can use our "Generic CRD Sync" plugin to sync CRDs declaratively. Docs: https://www.vcluster.com/docs/plugins/generic-crd-sync Based on the...

@rahulii The docs describe how to write the mapping in the helm values, it is then transformed into a different format to pass it as a CLI flag - https://github.com/loft-sh/vcluster/blob/09b0fd82c1ab8e820a6ed1fa342cb2dd443419e2/charts/k3s/templates/_helpers.tpl#L113-L129

@rahulii You could test it with minikube too. Use `minikube tunnel` command. Docs: https://minikube.sigs.k8s.io/docs/handbook/accessing/#using-minikube-tunnel

I don't think we will be able to have pod names 1:1 match between the host and virtual due to the potential collisions. There is a separate issue about adding...

This issue has had no reply for over 2 months. Closing.

This is quite an old issue with no reports of further problems, so I presume this was resolved. Please comment or open a new issue if you experience this problem.