Update release tools

[kvaps]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR is needed to test the functionality introduced in kubernetes-csi/csi-release-tools#121

Squashed 'release-tools/' changes from c6a88c6e..ece0f500

ece0f500 check namespace for snapshot-controller
3b6d17b1 Merge pull request #118 from pohly/cloud-build-timeout
9318c6cc cloud build: double the timeout, now 1 hour
86ff5802 Merge pull request #116 from andyzhangx/export-image-name
c3a96625 allow export image name and registry name

git-subtree-dir: release-tools
git-subtree-split: ece0f500ed9ee6c197ffce6d410d12edd8bf7365

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Welcome @kvaps!

It looks like this is your first PR to kubernetes-csi/csi-driver-host-path 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-csi/csi-driver-host-path has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @kvaps. Thanks for your PR.

I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[xing-yang]

/ok-to-test

[xing-yang]

/assign @pohly

[pohly]

Please re-do the git subtree pull with the --squash option.

I know, we (someone?) needs to update the README.md...

[pohly]

There are no changes left?

I think this was supposed to be a test PR for kubernetes-csi/csi-release-tools#121, right?

That means you have to point git subtree at a repo and commit which includes the non-upstream csi-release-tools changes.

[kvaps]

Yeah, sorry, I was just bit confused by amount of repos 😅 and forget to do subtree pull in this one

[xing-yang]

Please copy the commit message from "5961195" to the PR description for the record.

[xing-yang]

/hold

This is a test PR. Adding hold to avoid it from being merged.

[pohly]

Looks good to me.

[pohly]

/hold

This is a test PR. Adding hold to avoid it from being merged.

We used to have a unit test which prevents merging if it detects new commits, but squashing circumvents that check.

I guess our rule should be:

• squash if you intend to get the PR merged and the squashed commit is really from upstream csi-release-tools
• don't squash when testing additional commits before merging into csi-release-tools

Oh, and a PR description which makes the intention clear 😉

[pohly]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kvaps, pohly

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:

• release-tools/OWNERS [pohly]

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

[pohly]

It's okay to merge this because it squashed the exact same commit that I just approved for csi-release-tools.

[pohly]

/hold cancel

[kvaps]

/retest

[pohly]

Fix for failing tests is here: kubernetes/test-infra#20596

[pohly]

/retest

[pohly]

/lgtm

[k8s-ci-robot]

@kvaps: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
pull-kubernetes-csi-csi-driver-host-path-1-17-on-kubernetes-1-17	a489085	link	/test pull-kubernetes-csi-csi-driver-host-path-1-17-on-kubernetes-1-17
pull-kubernetes-csi-csi-driver-host-path-1-20-on-kubernetes-1-20	44fb49f	link	/test pull-kubernetes-csi-csi-driver-host-path-1-20-on-kubernetes-1-20

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.