WIP: Add context to more places

[justinsb]

This is to add context to all callsites for vfs.Context

Note: I don't think we should do this yet ... I think at the least we need to:

1. figure out how to get a context in the RenderAWS / RenderTerraform / etc methods.
2. do something better for tests, like maybe ContextForTest that puts the testing.T into the context, maybe in future sets up a logger that goes to the test output. That could be quite handy, but this is more of a nice-to-have that would be nice to introduce at the same time.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from justinsb by writing /assign @justinsb in a comment. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

@justinsb: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kops-e2e-k8s-gce-cilium	35a4f92	link	true	/test pull-kops-e2e-k8s-gce-cilium
pull-kops-e2e-aws-upgrade-125-ko125-to-klatest-kolatest-many-addons	35a4f92	link	false	/test pull-kops-e2e-aws-upgrade-125-ko125-to-klatest-kolatest-many-addons
pull-kops-e2e-cni-flannel	35a4f92	link	true	/test pull-kops-e2e-cni-flannel
pull-kops-e2e-k8s-aws-calico	35a4f92	link	true	/test pull-kops-e2e-k8s-aws-calico
pull-kops-e2e-cni-calico	35a4f92	link	true	/test pull-kops-e2e-cni-calico
pull-kops-e2e-cni-kuberouter	35a4f92	link	true	/test pull-kops-e2e-cni-kuberouter
pull-kops-e2e-cni-cilium-eni	35a4f92	link	true	/test pull-kops-e2e-cni-cilium-eni
pull-kops-e2e-cni-amazonvpc	35a4f92	link	false	/test pull-kops-e2e-cni-amazonvpc
pull-kops-e2e-cni-calico-ipv6	35a4f92	link	true	/test pull-kops-e2e-cni-calico-ipv6
pull-kops-e2e-cni-cilium	35a4f92	link	true	/test pull-kops-e2e-cni-cilium
pull-kops-e2e-cni-cilium-ipv6	35a4f92	link	true	/test pull-kops-e2e-cni-cilium-ipv6
pull-kops-e2e-cni-cilium-etcd	35a4f92	link	true	/test pull-kops-e2e-cni-cilium-etcd
pull-kops-verify-govet	35a4f92	link	true	/test pull-kops-verify-govet
pull-kops-build	35a4f92	link	true	/test pull-kops-build
pull-kops-test	35a4f92	link	true	/test pull-kops-test
pull-kops-verify-golangci-lint	35a4f92	link	true	/test pull-kops-verify-golangci-lint

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[k8s-ci-robot]

@justinsb: PR needs rebase.

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-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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and 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:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closed this PR.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and 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:

• Reopen this PR with /reopen
• Mark this PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

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