do not ship `install.yaml` as release artifact

[ffromani]

In the github release page, we should not add install.yaml anymore as release artifact as we prefer the helm charts. Shipping both is confusing and can cause friction as we move the focus to helm - install.yaml will get out of date fast

[fmuyassarov]

I agree, +1

[swatisehgal]

/assign

[pravk03]

We can still remove it from https://github.com/kubernetes-sigs/dra-driver-cpu/releases/tag/v0.2.0 if that is preferred.

[ffromani]

We can still remove it from https://github.com/kubernetes-sigs/dra-driver-cpu/releases/tag/v0.2.0 if that is preferred.

We can do both :) fix the release artifacts and fix the release process (incl. docs). If you agree it's misleading, I can go ahead and remove it. Looks like @swatisehgal wants to fix the process.

[pravk03]

I added install.yaml to remain consistent with the previous release, but agree with the suggestion here to remove it now that Helm is preferred.

Thanks @swatisehgal for picking up the release process fixes!

[ffromani]

I added install.yaml to remain consistent with the previous release, but agree with the suggestion here to remove it now that Helm is preferred.

Thanks @swatisehgal for picking up the release process fixes!

ok, what about this then: keep the artifact for consistency, but add a fat big disclaimer that install.yaml is provided for consistency and the helm chart is actually preferred from this release on?

[pravk03]

Both work for me. It may be ok removing it altogether if it avoids the confusion.

[ffromani]

ok, so let's be conservative: I'll edit the release 0.2.0 to clearly point out that install.yaml is shipped for compatibility but legacy, that we prefer users to use helm charts, and that from 0.3.0 on we will stop shipping the install.yaml and only provide helm charts.