Optimized apply

[TortillaZHawaii]

This will take in the output from Compare and apply the calls using already existing forwardingrules.ForwardingRules repository. Calls are paralellised at each stage: delete, patch, create to speed up the whole process.

This isn't used yet.

I also vendored in errgroup which is a wrapper for sync.Waitgroup with error handling. More info at golang.org/x/sync/errgroup.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: TortillaZHawaii

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [TortillaZHawaii]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[TortillaZHawaii]

/assign @mmamczur

[TortillaZHawaii]

/retest

E2E errors out on stuff unrelated to this PR:

go: github.com/google/ko@v0.12.0: version constraints conflict:
	github.com/google/ko@v0.12.0 indirectly requires github.com/garyburd/redigo@v0.0.0-20150301180006-535138d7bcd7: reading https://proxy.golang.org/github.com/garyburd/redigo/@v/v0.0.0-20150301180006-535138d7bcd7.mod: 404 Not Found
	server response:
	not found: github.com/garyburd/redigo@v0.0.0-20150301180006-535138d7bcd7: invalid version: git ls-remote -q origin in /tmp/gopath/pkg/mod/cache/vcs/b2205dabeb4c506b231f579c1f1c721eea341c0e28510e9185c87fd93afeaafd: exit status 128:
		fatal: could not read Username for 'https://github.com/': terminal prompts disabled
	Confirm the import path was entered correctly.
	If this is a private repository, see https://golang.org/doc/faq#git_https for additional information.

[TortillaZHawaii]

/retest

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[TortillaZHawaii]

/close

[k8s-ci-robot]

@TortillaZHawaii: Closed this PR.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.