Skip to content

Commit

Permalink
Merge pull request #2723 from gnufied/update-new-sections-for-fsgroup
Browse files Browse the repository at this point in the history
Add new sections in kep
  • Loading branch information
k8s-ci-robot committed May 12, 2021
2 parents ee4751c + afa595b commit 90424fd
Showing 1 changed file with 5 additions and 23 deletions.
28 changes: 5 additions & 23 deletions keps/sig-storage/2317-fsgroup-on-mount/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -351,35 +351,17 @@ _This section must be completed when targeting beta graduation to a release._

## Implementation History

<!--
Major milestones in the lifecycle of a KEP should be tracked in this section.
Major milestones might include:
- the `Summary` and `Motivation` sections being merged, signaling SIG acceptance
- the `Proposal` section being merged, signaling agreement on a proposed design
- the date implementation started
- the first Kubernetes release where an initial version of the KEP was available
- the version of Kubernetes where the KEP graduated to general availability
- when the KEP was retired or superseded
-->
- Feb 2 2021: KEP merged into kubernetes/enhancements repo

## Drawbacks

<!--
Why should this KEP _not_ be implemented?
-->
- N/A

## Alternatives

<!--
What other approaches did you consider, and why did you rule them out? These do
not need to be as detailed as the proposal, but should include enough
information to express the idea and why it was not acceptable.
-->
- An alternative to supplying fsgroup of the pod to the CSI driver is to mount volumes with 777 permissions or run pods. Both of these alternatives are not
great and not backward compatible.

## Infrastructure Needed (Optional)

<!--
Use this section if you need things from the project/SIG. Examples include a
new subproject, repos requested, or GitHub details. Listing these here allows a
SIG to get the process for these resources started right away.
-->
- Azure Cloudprovider access

0 comments on commit 90424fd

Please sign in to comment.