Review README files

[rojkov]

Some files got outdated. For example cmd/gpu_plugin/README.md describes the installation procedure like we still use dep instead of go mod.

[mythi]

We just did a bunch of updates. What is outdated?

like we still use dep instead of go mod.

Where's this?

[rojkov]

Particularly this
https://github.com/intel/intel-device-plugins-for-kubernetes/blob/master/cmd/gpu_plugin/README.md#getting-the-source-code

It's not needed nowadays to clone the repo into a specific path.

[rojkov]

This section https://github.com/intel/intel-device-plugins-for-kubernetes#running-e2e-tests needs to be included in the README's ToC.

[mythi]

It's not needed nowadays to clone the repo into a specific path.

true. I touched this part last time (f145541) and IIRC my thinking was that this gives a consistent starting point/path for each higher level section without any bigger re-work...

[mythi]

Next steps:

• in all of the READMEs, highlight the container image availability and the possibility to deploy using kubectl apply without cloning the repo
• change git cloning (go get does not work) to be path agnostic (GOPATH no longer relevant)

[pohly]

the possibility to deploy using kubectl apply without cloning the repo

Also make sure that those deployment files always pull an image that is compatible with the deployment.

In PMEM-CSI, we ensure that for releases, but not for the development branch, and already had issue reports twice because users were using deployment files from an old revision of our master branch with the latest, incompatible "canary" images.

[tkhred]

Hi, based on the following PR, the plugin has already supported k8s 1.18.

#365

I think it is a critical problem. (Actually, we need several days to know that the plugin supports 1.18 or not.)

Could you consider to update the top page README first?

[mythi]

Could you consider to update the top page README first?

I just opened a PR to work on updates in the top page README. What is the concern? In principle, the release branches should be used for work that requires stability.

[tkhred]

Sorry that I asked without checking your project plan. Our team will test the master branch with k8s 1.18 and I believe we can wait for the official v0.18 release.

[mythi]

@tkhred no problem at all. we're planning to make a v0.18 shortly (#251) you'r reminder is a valid task for #251!