@rifelpet which AWS account(s) are we speaking about (we have multiple)?

Signed-off-by: Vince Prignano [email protected]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes/k8s.io/pull/2270#pullrequestreview-692038528" title="Approved">CecileRobertMichon</a>, <a href="https://github.com/kubernetes/k8s.io/pull/2270#" title="Author self-approved">vincepri</a>

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

The pull request process is described here

<details > Needs approval from an approver in each of these files:

• k8s.gcr.io/images/k8s-staging-cluster-api/OWNERS [CecileRobertMichon,vincepri]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":[]} -->

They are using git-sync and have had a bunch of ideas for improvements. I have had a hard time finding enough time to devote to this and they offered to help.

@nan-yu @janetkuo

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes/k8s.io/pull/2270#" title="Author self-approved">vincepri</a>

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

The pull request process is described here

<details > Needs approval from an approver in each of these files:

• k8s.gcr.io/images/k8s-staging-cluster-api/OWNERS [vincepri]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":[]} -->

Signed-off-by: Vince Prignano [email protected]

@thockin is just merging this enough or do i still need to run some stuff by hand? (if i remember right you were making changes there, is it already done?)

/assign @thockin

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes/k8s.io/pull/2269#" title="Author self-approved">vincepri</a> To complete the pull request process, please assign dims after the PR has been reviewed. You can assign the PR to them by writing /assign @dims in a comment when ready.

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

<details open> Needs approval from an approver in each of these files:

• dns/OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":["dims"]} -->

Signed-off-by: Vince Prignano [email protected]

OK, I published the release in github

I was holding the release announcement until this went in. :)

@mkorbi: Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository. Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

<details>

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. </details>

/lgtm

Known members of the community and nothing against this at all. So welcome here as well.

The v3.3.3 release is missing from the git-sync repo. Happy for this to get merge anyway, but wanted to flag this.

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

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.

<details>

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. </details> <!-- test report -->

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-contributor-experience at kubernetes/community. /lifecycle stale

New Repo, Staging Repo, or migrate existing

<!-- Rules for migrating existing repos - https://git.k8s.io/community/github-management/kubernetes-repositories.md#rules-for-donated-repositories --> https://github.com/IBM/ibm-vpc-block-csi-driver

Requested name for new repository

ibm-vpc-block-csi-driver

Which Organization should it reside

kubernetes-sigs

If not a staging repo, who should have admin access

arahamad meghnasiingh

If not a staging repo, who should have write access

I will setup later once repo will be ready

If not a staging repo, who should be listed as approvers in OWNERS

arahamad meghnasiingh

If not a staging repo, who should be listed in SECURITY_CONTACTS

meghnasiingh ambiknai

What should the repo description be

IBM VPC Block CSI driver is responsible to manage the lifecycle of vpc block volume in kubernetes or openshift cluster based on IBM VPC

What SIG and subproject does this fall under in sigs.yaml

sig-storage

Approvals

Please prove you have followed the appropriate approval process for this new repo by including links to the relevant approvals (meeting minutes, e-mail thread, etc.) Will add, to whom I should get approval, I have approval from my org

Authoritative requirements are here: https://git.k8s.io/community/github-management/kubernetes-repositories.md

tl;dr (but really you should read the linked doc, this may be stale)

• If this is a core repository, then sig-architecture must approve
• If this is a SIG repository, then this must follow the procedure spelled out in that SIG's charter

Additional context for request

This is ibm vpc block volume driver(csi based) for kubenetes and openshift cluster based on IBM VPC infrastructure

/lgtm

@nikhita I guess we have followed all steps, can we move this on ?

AFAIK packages are actually still built with some shell scripts

https://github.com/kubernetes/release/tree/master/hack/rapture -> https://github.com/kubernetes/release/blob/eff40a556b1f7ec298a7f376588bd8c4a16d0cf2/hack/rapture/k8s-rapture.sh#L178 https://github.com/kubernetes/release/blob/eff40a556b1f7ec298a7f376588bd8c4a16d0cf2/hack/rapture/k8s-rapture.sh#L123

-> https://github.com/kubernetes/release/blob/master/packages/rpm/docker-build.sh https://github.com/kubernetes/release/blob/master/packages/deb/jenkins.sh

however since this is essentially not versioned with kubernetes, it's tricky to safely fix this. https://github.com/kubernetes/release/issues/1913

Bumps golang.org/x/tools from 0.1.3 to 0.1.4. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/golang/tools/commit/d824a7481dff873bb36f76c5b92c46c97852d52e"><code>d824a74</code></a> gopls/doc: include instructions for compiling generic code</li> <li><a href="https://github.com/golang/tools/commit/6d3e43932267c52ce8491fbdc1385202c8cf36d6"><code>6d3e439</code></a> gopls/doc: add instructions for working with generic code</li> <li><a href="https://github.com/golang/tools/commit/4c651fc1fc751d8e42d6b4f099ee1b9df6404e07"><code>4c651fc</code></a> internal/lsp/source: add inferred types to generic function hover</li> <li><a href="https://github.com/golang/tools/commit/d25f9066828099517056ecb554d8d0b84f026ddd"><code>d25f906</code></a> internal/lsp: do not block on channel when there is an error</li> <li><a href="https://github.com/golang/tools/commit/463a76b3dc7546fb34cbac5dbc48b4ed68eb96e8"><code>463a76b</code></a> internal/lsp: only reload invalid metadata when necessary</li> <li><a href="https://github.com/golang/tools/commit/116feaea4581560a370de353120153502e19fc48"><code>116feae</code></a> internal/lsp: move the progress tracker to the session</li> <li><a href="https://github.com/golang/tools/commit/3f7c32638c09af103a99661c2dba5837243fc88b"><code>3f7c326</code></a> gopls/internal/regtest: skip the flaky TestResolveImportCycle</li> <li><a href="https://github.com/golang/tools/commit/b12e6172dcbceeb9b1b898035a3299c248210c8c"><code>b12e617</code></a> internal/lsp/cache: don't delete metadata until it's reloaded</li> <li><a href="https://github.com/golang/tools/commit/4b484fb1367ed62d15dd9142cbd1d7c1b74becce"><code>4b484fb</code></a> internal/lsp: exclude the module cache from the workspace</li> <li><a href="https://github.com/golang/tools/commit/9a55cb1fbb78265fb924e3698f1a064c015ca962"><code>9a55cb1</code></a> internal/lsp/command: minor clean-up of StartDebugging description</li> <li>Additional commits viewable in <a href="https://github.com/golang/tools/compare/v0.1.3...v0.1.4">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes/release/pull/2145#" title="Author self-approved">dependabot[bot]</a>, <a href="https://github.com/kubernetes/release/pull/2145#pullrequestreview-691381899" title="Approved">saschagrunert</a>

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

The pull request process is described here

<details > Needs approval from an approver in each of these files:

• OWNERS [saschagrunert]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":[]} -->

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: <a href="https://github.com/kubernetes/k8s.io/pull/2267#" title="Author self-approved">thockin</a>

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

The pull request process is described here

<details > Needs approval from an approver in each of these files:

• k8s.gcr.io/images/k8s-staging-git-sync/OWNERS [thockin]

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment </details> <!-- META={"approvers":[]} -->

cc @nan-yu @janetkuo