Automatic merge from submit-queue
Flexvolume Dynamic Plugin Discovery: Added comments about possible driver installation actions
Made it explicit that driver uninstalls are allowed, and cautioned against uninstalling while a volume depends on the driver.
/sig storage
/assign @chakri-nelluri @saad-ali
Automatic merge from submit-queue
add apiserver-count fix proposal
This is a proposal to fix the apiserver-count issue at https://github.com/kubernetes/kubernetes/issues/22609. I would appreciate a review on the proposal.
- [x] Add ConfigMap for configurable options
- [ ] Find out dependencies on the Endpoints API and add them to the proposal
New labels are being used to signify that a PR should not be merged if
it's got a missing release note and/or requires a release note.
Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
Fix some wording.
Remove the demand for validation to fail. It also says to clearthose
fields, which more closely models non-existent fields.
Change the tombstone (proposed - nobody is using this yet, obviously).
This format matches what gengo uses for other tags.
In order to reduce the memory allocation impact of very large LIST
operations against the Kubernetes apiserver, it should be possible to
receive a single large list as many individual requests to the
server.
Automatic merge from submit-queue
Backoff policy and failed pod limit
This update addresses problems raised in https://github.com/kubernetes/kubernetes/issues/30243 and https://github.com/kubernetes/kubernetes/issues/43964.
@erictune I've mentioned this to you during last sig-apps, ptal
@kubernetes/sig-apps-feature-requests ptal
@lukasheinrich @nickschuch @Yancey1989 @sstarcher @maximz fyi since you all were interested in this
Automatic merge from submit-queue
provides an example on how to register custom admission plugin.
this PR adds an example that highlights relevant parts of source code from sample apiserver that deals with admission registration.
close#47868
Automatic merge from submit-queue
Remove getvolume, as it is not supported and ignored
Based on discussion on kubernetes-sig-storage:
Some drivers implemented getvolume, some didn't[4]. Is it expected to be a name of an existing volume on the storage? Can nodename+volumename be considered unique?
[Chakri] GetVolumeName is not supported and is ignored. You don’t have to implement it.
[4] 7885aaf689
Based on discussion on kubernetes-sig-storage:
2. Some drivers implemented getvolume, some didn't[4]. Is it expected to be a name of an existing volume on the storage? Can nodename+volumename be considered unique?
[Chakri] GetVolumeName is not supported and is ignored. You don’t have to implement it.
Automatic merge from submit-queue
[Proposal] Allow a Pod Security Policy to managing access to the Flexvolumes
This PR proposes to add the `AllowedFlexVolumes` to a PSP to control pod's access to the different Flexvolume drivers.
PTAL @smarterclayton @pweil- @mfojtik
Automatic merge from submit-queue
add design proposals owners
Can I get a few sig leads to propose reasonable reviewers for blunderbuss to use when assigning PRs in this dir?
I started with the top level [OWNERS](https://github.com/kubernetes/kubernetes/blob/master/OWNERS) from k/k.
If you make comment's with github handle's that should be included, I'll add them to the list of reviewers.
**NOTE** - Approvers isn't turned on yet in this repo so adding LGTM (anyone in the org can do this) will put the PR in the queue to be merged. Being a reviewer just means you can be auto-assigned to design-proposals reviews.
Automatic merge from submit-queue
Redesign mount propagation
The proposal won't work as it was merged, it makes too many directories as shared (see #648).
A different approach is needed, I've chosen 'Add an option in VolumeMount API', but I would be fine also with 'Add an option in HostPathVolumeSource', there is only very small difference to me.
The proposal also describes how it will be implemented, especially during alpha phase.
Fixes#648
@kubernetes/sig-node-proposals @kubernetes/sig-storage-proposals
Automatic merge from submit-queue
Dynamic Flexvolume plugin discovery proposal.
This lays out the design for the improved deployment story of Flexvolume, making it easier to work with out-of-tree volume plugins before CSI comes to fruition.
Automatic merge from submit-queue
Updating FlexVolume doc with capabilities addition.
The following PR introduces a FlexVolume API change, so the documentation needs to be updated.
https://github.com/kubernetes/kubernetes/pull/47503
Automatic merge from submit-queue
Device Plugin Design Proposal
Notes for reviewers
First proposal submitted to the community repo, please advise if something's not right with the format or procedure, etc.
cc @vishh @derekwaynecarr
Automatic merge from submit-queue
Replace KUBERNETES_PROVIDER with --provider
Since 07c6da22fe, KUBERNETES_PROVIDER
has been deprecated. So this PR replaces KUBERNETES_PROVIDER with
the option --provider to specify a provider on e2e test.
Automatic merge from submit-queue
Proposal for taking mount option to GA
Also add support for specifying mount options
in storage classes.
cc @kubernetes/sig-storage-api-reviews @liggitt
Since 07c6da22fe, KUBERNETES_PROVIDER
has been deprecated. So this PR replaces KUBERNETES_PROVIDER with
the option --provider to specify a provider on e2e test.
Automatic merge from submit-queue
HugePages proposal
A pod may request a number of huge pages. The `scheduler` is able to place the pod on a node that can satisfy that request. The `kubelet` advertises an allocatable number of huge pages to support scheduling decisions. A pod may consume hugepages via `hugetlbfs` or `shmget`.
Planned as Alpha for Kubernetes 1.8 release.
See feature: https://github.com/kubernetes/features/issues/275
@kubernetes/sig-scheduling-feature-requests
@kubernetes/sig-scheduling-misc
@kubernetes/sig-node-proposals
@kubernetes/api-approvers
@kubernetes/api-reviewers
Automatic merge from submit-queue
contributors/devel: add welcome-to-kubernetes-new-developer-guide.md
Add a new 1-page document targeted to brand new developers. Some of this information is duplicated elsewhere but there is no "onboarding" doc for Kubernetes developers (as far as I could discern).
Review welcome!
@grodrigues3 and @pwittrock have already done a couple rounds of review on this in Google docs.
Thanks!
e2e test finds a suitable util.sh from "--provider" option.
However the e2e test way of community repo didn't show the setting of
the option and the gce's util.sh was selected as the default.
This patch fixes it.
`kubernetes/test-infra` pull requests #3766 and #3898 changed the
behavior of the OWNERS process slightly. This patch updates the
documenation to be more up-to-date.
Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
Move from design doc to state-of-the-world doc
The OWNERS feature has been implemented for a while now. Let's
document how it actually works
I originally started this with the intent of fleshing out measurable
critera for adding/removing OWNERS, but as I dug into it, I realized I
need more time to explore useful metrics. Let's find out if this is
enough of a rewrite to call incremental progress