import devel, design, and proposals from kubernetes #118
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Automatic merge from submit-queue component feature config proposal This adds a proposal for a simple mechanism to pass runtime config to kube system components. Motivation is to have a consistent way to toggle new features that are not tied to an API group. Feedback appreciated @mikedanese @lavalamp @kubernetes/sig-api-machinery @kubernetes/sig-cluster-lifecycle @kubernetes/sig-node <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30003) <!-- Reviewable:end -->
Automatic merge from submit-queue doc third party resource usage more cleanly fix #29002 release-note-none <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/29431) <!-- Reviewable:end -->
Automatic merge from submit-queue HyperLink not found and can't redirect HyperLink "http://kubernetes.io/v1.1/docs/design/expansion.html" not found and can't redirected, should be changed to "http://kubernetes.io/kubernetes/v1.1/docs/design/expansion.html" <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/29609) <!-- Reviewable:end -->
Automatic merge from submit-queue Fix some typos in control-plane-resilience.md Fix some typos in control-plane-resilience.md <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30209) <!-- Reviewable:end -->
Automatic merge from submit-queue fix mistakes in api_changes.md <!-- Checklist for submitting a Pull Request Please remove this comment block before submitting. 1. Please read our [contributor guidelines](https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md). 2. See our [developer guide](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md). 3. If you want this PR to automatically close an issue when it is merged, add `fixes #<issue number>` or `fixes #<issue number>, fixes #<issue number>` to close multiple issues (see: https://github.com/blog/1506-closing-issues-via-pull-requests). 4. Follow the instructions for [labeling and writing a release note for this PR](https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes) in the block below. --> ```release-note fix mistakes in api_changes.md ``` Signed-off-by: Xianglin Gao <[email protected]> <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.kubernetes.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/30426) <!-- Reviewable:end -->
Automatic merge from submit-queue Add Node.js `kubernetes-client` to client-libraries.md
Automatic merge from submit-queue docs/proposal: add proposal for kubectl login This PR updates kubernetes/enhancements#32 and kubernetes/kubernetes#25758 by adding a proposal for a "kubectl login" command. It's a bit more involved than the implementation discussed with @deads2k in #25758, by proposing a long term goal for the overall subcommand. cc @kubernetes/sig-auth @kubernetes/kubectl
Automatic merge from submit-queue fix a typo in nodeaffinity
fixes #24078 --namespace is a very common flag for nearly every kubectl command we have. We should claim -n for it.
Automatic merge from submit-queue re-organize development.md Addresses issue #13876; reorganizes and cleans up parts of development.md; splits out the godep section for managing `vendor/` tree dependencies into a new godep.md file. ```release-note The developer guide has been reorganized to facilitate the majority of new developers working on Kubernetes. ``` Signed-off-by: Mike Brown <[email protected]>
Signed-off-by: Crazykev <[email protected]>
fix wrong path for all registries
Automatic merge from submit-queue Remove incorrect docs about unset fields in NetworkPolicyPeer While hammering out the semantics of not-present vs present-but-empty, we appear to have added incorrect clarifications to NetworkPolicyPeer, where the semantics of PodSelector not being present is supposed to be "do what NamespaceSelector" says, not "select no pods", and likewise with NamespaceSelector not being present. I think it's clearest if we just don't say anything, since we already said "Exactly one of the following must be specified" above. Alternatively we could be redundant and say "(If not provided, then NamespaceSelector must be set.)" or something like that. @caseydavenport @thockin
Signed-off-by: Huamin Chen <[email protected]>
Automatic merge from submit-queue kubelet eviction on inode exhaustion Add support for kubelet to monitor for inode exhaustion of either image or rootfs, and in response, attempt to reclaim node level resources and/or evict pods.
Automatic merge from submit-queue Implement dynamic provisioning (beta) of PersistentVolumes via StorageClass Implemented according to PR #26908. There are several patches in this PR with one huge code regen inside. * Please review the API changes (the first patch) carefully, sometimes I don't know what the code is doing... * `PV.Spec.Class` and `PVC.Spec.Class` is not implemented, use annotation `volume.alpha.kubernetes.io/storage-class` * See e2e test and integration test changes - Kubernetes won't provision a thing without explicit configuration of at least one `StorageClass` instance! * Multiple provisioning volume plugins can coexist together, e.g. HostPath and AWS EBS. This is important for Gluster and RBD provisioners in #25026 * Contradicting the proposal, `claim.Selector` and `volume.alpha.kubernetes.io/storage-class` annotation are **not** mutually exclusive. They're both used for matching existing PVs. However, only `volume.alpha.kubernetes.io/storage-class` is used for provisioning, configuration of provisioning with `Selector` is left for (near) future. * Documentation is missing. Can please someone write some while I am out? For now, AWS volume plugin accepts classes with these parameters: ``` kind: StorageClass metadata: name: slow provisionerType: kubernetes.io/aws-ebs provisionerParameters: type: io1 zone: us-east-1d iopsPerGB: 10 ``` * parameters are case-insensitive * `type`: `io1`, `gp2`, `sc1`, `st1`. See AWS docs for details * `iopsPerGB`: only for `io1` volumes. I/O operations per second per GiB. AWS volume plugin multiplies this with size of requested volume to compute IOPS of the volume and caps it at 20 000 IOPS (maximum supported by AWS, see AWS docs). * of course, the plugin will use some defaults when a parameter is omitted in a `StorageClass` instance (`gp2` in the same zone as in 1.3). GCE: ``` apiVersion: extensions/v1beta1 kind: StorageClass metadata: name: slow provisionerType: kubernetes.io/gce-pd provisionerParameters: type: pd-standard zone: us-central1-a ``` * `type`: `pd-standard` or `pd-ssd` * `zone`: GCE zone * of course, the plugin will use some defaults when a parameter is omitted in a `StorageClass` instance (SSD in the same zone as in 1.3 ?). No OpenStack/Cinder yet @kubernetes/sig-storage
Automatic merge from submit-queue more explictly about NoDiskConflicts policy and applicable volume types partially clarify #29670 @kubernetes/sig-scheduling
Signed-off-by: Xianglin Gao <[email protected]>
Signed-off-by: Crazykev <[email protected]>
Signed-off-by: Crazykev <[email protected]>
Automatic merge from submit-queue correct specifies in aws_under_the_hood
Signed-off-by: yupeng <[email protected]>
…ress-design-proposal Automatic merge from submit-queue Federated Ingress Proposal cc: @kubernetes/sig-cluster-federation @mfanjie
Automatic merge from submit-queue update gazel usage in bazel.md **What this PR does / why we need it**: Now run the newest gazel have to specify the '-root' argument to update a single BUILD file. So updated the gazel usage.
Automatic merge from submit-queue Add reviewable notes to CONTRIBUTING @kubernetes/contributor-experience
Automatic merge from submit-queue Fix container to pod in resource-qos.md `...then the container is classified as Guaranteed.` Here `container` should be `pod`.
Automatic merge from submit-queue Added comments on running update-bazel.sh in "$GOPATH/src/k8s.io/kubernetes" **What this PR does / why we need it**: This path made `hack/update-bazel.sh` to accept `$GOPATH` with multiple path.
Automatic merge from submit-queue Remove a few versioned-warnings that snuck in, again
Automatic merge from submit-queue fix typo in podaffinity.md
Automatic merge from submit-queue fix the mistake type <!-- Thanks for sending a pull request! Here are some tips for you: 1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md 2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md 3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes --> **What this PR does / why we need it**: **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes # **Special notes for your reviewer**: **Release note**: <!-- Steps to write your release note: 1. Use the release-note-* labels to set the release note state (if you have access) 2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. --> ```release-note ``` Signed-off-by: yupeng <[email protected]>
Automatic merge from submit-queue Fix typo in e2e tests doc
Document that we are currently holding off on adding new approvers until the reviewers process is in place. And set a target deadline.
All of the tracking is happening here kubernetes-retired/contrib#1389 point people at it.
michelleN
changed the title
|
Thanks! I'm going to merge and we can iterate from there. The original authors signed the Google CLA at the time those commits were contributed. |
|
Thanks @bgrant0607 ! |
|
for repos which use the bot to merge (do we do that here?) |
|
@eparis This repo doesn't yet have bot automation. |
danehans
pushed a commit
to danehans/community
that referenced
this pull request
Jul 18, 2023
This adds an entry for the User Experience WG. Signed-off-by: Venil Noronha <[email protected]>
kevin-wangzefeng
pushed a commit
to kevin-wangzefeng/community
that referenced
this pull request
Sep 8, 2023
add documents of KEAW2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.