gcp-filestore-csi-driver icon indicating copy to clipboard operation
gcp-filestore-csi-driver copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

[release-1.6] issue-639: Add labels from command line option to filestore backup resource

Open bharath-b-rh opened this issue 1 year ago • 2 comments

This is a manual cherry-pick of https://github.com/kubernetes-sigs/gcp-filestore-csi-driver/pull/640

NONE

The automated cherry-pick https://github.com/kubernetes-sigs/gcp-filestore-csi-driver/pull/888 had merge conflicts, hence created a manual cherry-pick after rebase.

/assign @leiyiz

bharath-b-rh avatar Aug 27 '24 04:08 bharath-b-rh

Hi @bharath-b-rh. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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-sigs/prow repository.

k8s-ci-robot avatar Aug 27 '24 04:08 k8s-ci-robot

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bharath-b-rh Once this PR has been reviewed and has the lgtm label, please assign songjiaxun for approval. 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:

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 avatar Aug 27 '24 04:08 k8s-ci-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 avatar Nov 25 '24 05:11 k8s-triage-robot

/remove-lifecycle stale

bharath-b-rh avatar Nov 25 '24 09:11 bharath-b-rh

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 avatar Feb 23 '25 09:02 k8s-triage-robot

/remove-lifecycle stale

bharath-b-rh avatar Feb 24 '25 04:02 bharath-b-rh

Commits part of release-1.9, hence closing this PR.

/close

bharath-b-rh avatar Feb 24 '25 04:02 bharath-b-rh