gomod: use top level go mod for controller/sidecar #49
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To help with dependency management, shift from using separate go mods for controller and sidecar, and instead use a top level go mod for these buildable components. client and proto still have separate go (sub)mods because they are pulled in by drivers or other operators, and keeping their dependency lists small is important.
This also allows us to deduplicate the vendor dir that was previously kept separately for both components.