enhancements icon indicating copy to clipboard operation
enhancements copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

Option to Preserve default file mode bit (Mode\DefaultMode) set in AtomicWriter volumes

Open abhisheksinghbaghel opened this issue 3 years ago • 14 comments

  • One-line enhancement description (can be used as a release note): Option to Preserve default file mode bit (Mode\DefaultMode) set in AtomicWriter volumes
  • Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/pull/2606
  • Discussion Link: https://github.com/kubernetes/kubernetes/issues/57923
  • Primary contact (assignee): @abhisheksinghbaghel
  • Responsible SIGs: sig-storage
  • Enhancement target (which target equals to which milestone):
    • Alpha release target (x.y): 1.22
    • Beta release target (x.y):
    • Stable release target (x.y):
  • [x] Alpha
    • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/2606
    • [x] Code (k/k) update PR(s): https://github.com/kubernetes/kubernetes/pull/101016
    • [ ] Docs (k/website) update PR(s):

/sig storage xref https://github.com/kubernetes/enhancements/pull/2606

abhisheksinghbaghel avatar Apr 07 '21 19:04 abhisheksinghbaghel

For the discussion link, is it pointing to the right link?

I think we have one issue outstanding long time here: https://github.com/kubernetes/kubernetes/issues/57923

Jiawei0227 avatar Apr 07 '21 20:04 Jiawei0227

For the discussion link, is it pointing to the right link?

I think we have one issue outstanding long time here: kubernetes/kubernetes#57923

Accidently deleted '3' at the end. Thanks for catching it!

abhisheksinghbaghel avatar Apr 07 '21 20:04 abhisheksinghbaghel

/sig storage

abhisheksinghbaghel avatar Apr 07 '21 20:04 abhisheksinghbaghel

/milestone v1.22 /stage alpha

JamesLaverack avatar Apr 29 '21 18:04 JamesLaverack

@JamesLaverack Can you please remove this from v1.22 milestone? We discussed about this in today's SIG-Storage meeting and decided that this needs more discussions. So we are only doing design in 1.22.

xing-yang avatar May 06 '21 19:05 xing-yang

Okay. I've marked this as "Removed from Milestone" on the tracking sheet. Thank you for letting me know. :)

JamesLaverack avatar May 06 '21 22:05 JamesLaverack

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

k8s-triage-robot avatar Aug 04 '21 22:08 k8s-triage-robot

/remove-lifecycle stale

Jiawei0227 avatar Aug 12 '21 18:08 Jiawei0227

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and 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 issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or 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 10 '21 18:11 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and 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 issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or 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 avatar Dec 10 '21 19:12 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and 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 issue is closed

You can:

  • Reopen this issue or PR with /reopen
  • Mark this issue or 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-triage-robot avatar Jan 09 '22 19:01 k8s-triage-robot

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and 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 issue is closed

You can:

  • Reopen this issue or PR with /reopen
  • Mark this issue or 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.

k8s-ci-robot avatar Jan 09 '22 19:01 k8s-ci-robot

/reopen /remote-lifecycle frozen

gnufied avatar Jan 11 '23 18:01 gnufied

@gnufied: Reopened this issue.

In response to this:

/reopen /remote-lifecycle frozen

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 avatar Jan 11 '23 18:01 k8s-ci-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues 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 issue is closed

You can:

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

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

/close not-planned

k8s-triage-robot avatar Feb 10 '23 19:02 k8s-triage-robot

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues 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 issue is closed

You can:

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

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

/close not-planned

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 avatar Feb 10 '23 19:02 k8s-ci-robot