Go 1.13 Meta-Issue

[DirectXMan12]

Go 1.13 is out 🎉 !

Things we can now do:

• Banish Gopkg.toml into the shadow realm (⚠️ Remove dep usage and Gopkg.* #598)
• Clean up the various scripts referencing Gopkg.toml (⚠️ Remove dep usage and Gopkg.* #598)

Things we can do now-ish

For everything below, we'll need to figure out a potential impact of aggressively switching to Go 1.13 as the min-supported-go-version. I expect Kubernetes will soon-ish, so it might not be that bad for us to do so now. That being said, it's almost certainly a breaking change.

• switch go.mod over to go1.13, so we can use new features
• Prune any uses of xerrors
• Figure out where we want to use %w instead of %v in Errorf
• Figure out if there are spots where we wanted to use wrapping errors but couldn't, and come up with a plan for switching over (relatedly, provide transition plans for folks using apierrors.IsXYZ) -- will be a ⚠️ breaking change
• revive the structured errors code/figure out what we want to do with that
• figure out if we want to prune uses of GO111MODULE=on from our scripts?

[DirectXMan12]

/kind feature
/priority important soon

/good-first-issue

(the script stuff is a good first issue, a few of the other items are help-wanted -- feel free to ask if you're not sure)

[k8s-ci-robot]

@DirectXMan12:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/kind feature
/priority important soon

/good-first-issue

(the script stuff is a good first issue, a few of the other items are help-wanted -- feel free to ask if you're not sure)

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/test-infra repository.

[k8s-ci-robot]

@DirectXMan12: The label(s) priority/important, priority/soon cannot be appled. These labels are supported: api-review, community/discussion, community/maintenance, community/question, cuj/build-train-deploy, cuj/multi-user, platform/aws, platform/azure, platform/gcp, platform/minikube, platform/other

In response to this:

/kind feature
/priority important soon

/good-first-issue

(the script stuff is a good first issue, a few of the other items are help-wanted -- feel free to ask if you're not sure)

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/test-infra repository.

[DirectXMan12]

/priority important-soon

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[DirectXMan12]

/remove-lifecycle stale