| Age | Commit message (Collapse) | Author |
|
|
|
Automatic merge from submit-queue
Proposal for adding PVC info to VolumeStats
Flushes out details for part 1 of the changes described in
[#855](https://github.com/kubernetes/community/pull/855)
Feature: [#363](https://github.com/kubernetes/features/issues/363)
|
|
|
|
|
|
s/kublet/kubelet
|
|
|
|
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
Proposal for growing persistent volumes
cc @kubernetes/sig-storage-pr-reviews @liggitt @eparis
|
|
type and to specify a default value for CacheSize.
|
|
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
Update pull-requests.md
|
|
p0lyn0mial/add_an_example_to_apiserver-build-in-admission-plugins
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
|
|
|
|
Modify Eviction Strategy to take Priority into account
|
|
Fix a typo.
|
|
|
|
The expand controller doesn't really have a desired state of world
|
|
|
|
|
|
|
|
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] https://github.com/kubernetes/kubernetes/commit/7885aaf6896d66a69658a9f55cd6063488ad3e06
|
|
Based on code (hmmm...), clarify that wait for attach should wait up to 10 minutes.
|
|
|
|
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.
|
|
|
|
sample apiserver that deals with admission registration.
close #47868
|
|
Automatic merge from submit-queue
Update event_compression.md
|
|
Automatic merge from submit-queue
Update jess' email
|
|
Signed-off-by: Jess Frazelle <acidburn@google.com>
|
|
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
|
|
fix bad url
|
|
|
|
Automatic merge from submit-queue
Update alpha field guidance
Summarizing outcome of discussions with @kubernetes/sig-api-machinery-misc
ref:
* https://docs.google.com/document/d/1wuoSqHkeT51mQQ7dIFhUKrdi3-1wbKrNWeIL4cKb9zU/edit#
* https://github.com/kubernetes/kubernetes/issues/34508#issuecomment-319412303
* https://www.youtube.com/watch?v=bzSK00TxEx0&list=PL69nYSiGNLP21oW3hbLyjjj4XhrwKxH2R&index=4&t=2580 (43:00-59:00)
* https://github.com/kubernetes/kubernetes/issues/30819
|
|
fix bad url in kubectl-create-from-env-file.md
|
|
Automatic merge from submit-queue
add guidelines for merge commits
Well, against merge commits, to be more accurate.
|
|
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
|
|
Proposal for publishing and communicating status of patch releases
|
|
Automatic merge from submit-queue
Update control-plane-resilience.md
|
|
Automatic merge from submit-queue
Update core-metrics-pipeline.md
|
|
Automatic merge from submit-queue
Update sysctl.md
|
|
Automatic merge from submit-queue
Update apiserver-build-in-admission-plugins.md
|