Clean up vendor dependencies

[Jeffwan]

As we migrate from dep to go modules. There's no need to keep vendor redirectory.

however, In order to remove it, there're some prerequisite steps.

1. Update update-codegen.sh to remove reference. Use code-generator from go mod.
2. python-sdk generation needs to be vendor independent. Similarly, we should use kube-openapi in go pkg.
3. Remove any vendor dependency in .travis.yaml or Dockerfile

[issue-label-bot]

Issue-Label Bot is automatically applying the labels:

Label	Probability
feature	0.73
area/operator	0.77

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

[issue-label-bot]

Issue-Label Bot is automatically applying the labels:

Label	Probability
feature	0.73
area/operator	0.77

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

[Jeffwan]

I did similar work for PyTorch and MXNet and I will take this one.

[gaocegege]

Since we cannot remove it from the .git history to reduce the repo size, can we just keep it?

[Jeffwan]

@gaocegege I don't quite understand that. Do you mean the repo size won't drop after vendor clean up? I think if there's reasonable request on vendor mode, we can keep it.

[terrytangyuan]

@gaocegege Well, technically it's possible to remove it from the history as well through git-filter-branch but can be dangerous. Unless there's strong reason to do that, e.g. accidentally pushed large files, we should refrain from doing so.

We can probably keep it around if really needed. Though one can always just use generate it on his own.

[gaocegege]

As you all know, vendor downloading in the Chinese mainland is sometimes affected for some unknown reasons. Thus prefer to keep it to make it easy for new contributors in China.

[terrytangyuan]

@gaocegege Good point. Is there any good/reliable workaround for that?

[gaocegege]

From our experience, we keep the vendor in git repository and check if it is updated in CI.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Jeffwan]

I agree on git-filter-branch , I think we consider to remove vendor in master, won't wipe git history. If we plan to do so, we need to be careful to only modify commits with vendor/ folder changes.

For China region, is there's a reliable GOPROXY people can use to speed up downloading?

[gaocegege]

Yeah, I think so. We can remove it safely.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Jeffwan]

I just remove vendor folder but there're still something left like updating ./hack/update-codegen.sh. I don't want to mix them together because vendor deletion is a very large PR..

For rest of the changes, I will make it later. (probably want for development branch done unless there're urgent needs). Major reason is to minimize the code change and make merge smooth later

[gaocegege]

Can we rename the issue since the vendor directory is already removed

[Jeffwan]

Can we rename the issue since the vendor directory is already removed

Sounds good. I rename it

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.