diff options
| author | guineveresaenger <guineveresaenger@gmail.com> | 2017-11-03 16:55:51 -0700 |
|---|---|---|
| committer | guineveresaenger <guineveresaenger@gmail.com> | 2017-11-03 16:55:51 -0700 |
| commit | a6dcf8678b5c3febaacf079b28174b4a2cbd88e2 (patch) | |
| tree | 913bdbfb61d604ca9543955b861970e02996a5a2 | |
| parent | b41c258f983f6a0ecb49a169a61673a1017639f8 (diff) | |
removed autogenerated munge analytics from files
171 files changed, 1 insertions, 764 deletions
diff --git a/contributors/design-proposals/README.md b/contributors/design-proposals/README.md index 0f27f108..dbdfb6c9 100644 --- a/contributors/design-proposals/README.md +++ b/contributors/design-proposals/README.md @@ -9,7 +9,3 @@ Note that a number of these documents are historical and may be out of date or u TODO: Add the current status to each document and clearly indicate which are up to date. TODO: Document the [proposal process](../devel/faster_reviews.md#1-dont-build-a-cathedral-in-one-pr). - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/api-machinery/admission_control.md b/contributors/design-proposals/api-machinery/admission_control.md index a7330104..dec92334 100644 --- a/contributors/design-proposals/api-machinery/admission_control.md +++ b/contributors/design-proposals/api-machinery/admission_control.md @@ -99,8 +99,3 @@ following: - If operation=connect, exec If at any step, there is an error, the request is canceled. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/api-machinery/admission_control_extension.md b/contributors/design-proposals/api-machinery/admission_control_extension.md index 70343623..c7e7f1b7 100644 --- a/contributors/design-proposals/api-machinery/admission_control_extension.md +++ b/contributors/design-proposals/api-machinery/admission_control_extension.md @@ -632,9 +632,4 @@ Some options: It should be easy for a novice Kubernetes administrator to apply simple policy rules to the cluster. In the future it is desirable to have many such policy engines enabled via extension to enable quick policy -customization to meet specific needs. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> +customization to meet specific needs.
\ No newline at end of file diff --git a/contributors/design-proposals/api-machinery/aggregated-api-servers.md b/contributors/design-proposals/api-machinery/aggregated-api-servers.md index 24ca495b..d1299a19 100644 --- a/contributors/design-proposals/api-machinery/aggregated-api-servers.md +++ b/contributors/design-proposals/api-machinery/aggregated-api-servers.md @@ -268,8 +268,3 @@ There were other alternatives that we had discussed. providing a centralised authentication and authorization service which all of the servers can use. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/api-machinery/api-chunking.md b/contributors/design-proposals/api-machinery/api-chunking.md index f7d51023..4930192a 100644 --- a/contributors/design-proposals/api-machinery/api-chunking.md +++ b/contributors/design-proposals/api-machinery/api-chunking.md @@ -175,8 +175,3 @@ The initial chunking implementation would focus on consistent listing on server For the initial alpha release, chunking would be behind a feature flag and attempts to provide the `continue` or `limit` flags should be ignored. While disabled, a `continue` token should never be returned by the server as part of a list. Future work might offer more options for clients to page in an inconsistent fashion, or allow clients to directly specify the parts of the namespace / name keyspace they wish to range over (paging). - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/api-machinery/api-group.md b/contributors/design-proposals/api-machinery/api-group.md index 28b98216..442c9ca8 100644 --- a/contributors/design-proposals/api-machinery/api-group.md +++ b/contributors/design-proposals/api-machinery/api-group.md @@ -113,7 +113,3 @@ To expose a list of the supported Openshift groups to clients, OpenShift just ha ## Future work 1. Dependencies between groups: we need an interface to register the dependencies between groups. It is not our priority now as the use cases are not clear yet. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/api-machinery/apiserver-watch.md b/contributors/design-proposals/api-machinery/apiserver-watch.md index ef395036..7e90d9b6 100644 --- a/contributors/design-proposals/api-machinery/apiserver-watch.md +++ b/contributors/design-proposals/api-machinery/apiserver-watch.md @@ -137,8 +137,3 @@ the same time, we can introduce an additional etcd event type: EtcdResync However, this might turn out to be unnecessary optimization if apiserver will always keep up (which is possible in the new design). We will work out all necessary details at that point. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/api-machinery/auditing.md b/contributors/design-proposals/api-machinery/auditing.md index b4e1d91e..c3f978d9 100644 --- a/contributors/design-proposals/api-machinery/auditing.md +++ b/contributors/design-proposals/api-machinery/auditing.md @@ -374,7 +374,3 @@ Below are the possible future extensions to the auditing mechanism: * Define how filters work. They should enable dropping sensitive fields from the request/response/storage objects. * Allow setting a unique identifier which allows matching audit events across apiserver and federated servers. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/api-machinery/client-package-structure.md b/contributors/design-proposals/api-machinery/client-package-structure.md index 37991402..1aa47b18 100644 --- a/contributors/design-proposals/api-machinery/client-package-structure.md +++ b/contributors/design-proposals/api-machinery/client-package-structure.md @@ -307,7 +307,3 @@ that client will not have to change their code until they are deliberately upgrading their import. We probably will want to generate some sort of stub test with a clientset, to ensure that we don't change the interface. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/api-machinery/controller-ref.md b/contributors/design-proposals/api-machinery/controller-ref.md index ec2db536..eee9629a 100644 --- a/contributors/design-proposals/api-machinery/controller-ref.md +++ b/contributors/design-proposals/api-machinery/controller-ref.md @@ -415,7 +415,3 @@ Summary of significant revisions to this document: * Specify ControllerRef-related behavior changes upon upgrade/downgrade. * [Implementation](#implementation) * List all work to be done and mark items already completed as of this edit. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/api-machinery/event_compression.md b/contributors/design-proposals/api-machinery/event_compression.md index e041affe..9d6acf42 100644 --- a/contributors/design-proposals/api-machinery/event_compression.md +++ b/contributors/design-proposals/api-machinery/event_compression.md @@ -162,8 +162,3 @@ compressing multiple recurring events in to a single event. single event to optimize etcd storage. * PR [#4444](http://pr.k8s.io/4444): Switch events history to use LRU cache instead of map. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/api-machinery/extending-api.md b/contributors/design-proposals/api-machinery/extending-api.md index c9aeb449..f5e2de6a 100644 --- a/contributors/design-proposals/api-machinery/extending-api.md +++ b/contributors/design-proposals/api-machinery/extending-api.md @@ -196,8 +196,3 @@ Thus, listing a third-party resource can be achieved by listing the directory: ``` ${standard-k8s-prefix}/third-party-resources/${third-party-resource-namespace}/${third-party-resource-name}/${resource-namespace}/ ``` - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/api-machinery/garbage-collection.md b/contributors/design-proposals/api-machinery/garbage-collection.md index 0bf42e5d..4ee1cabc 100644 --- a/contributors/design-proposals/api-machinery/garbage-collection.md +++ b/contributors/design-proposals/api-machinery/garbage-collection.md @@ -349,9 +349,3 @@ In case the garbage collector is mistakenly deleting objects, we should provide * Before an object is deleted from the registry, the API server clears fields like DeletionTimestamp, then creates the object in /archive and sets a TTL. * Add a `kubectl restore` command, which takes a resource/name pair as input, creates the object with the spec stored in the /archive, and deletes the archived object. - - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/api-machinery/metadata-policy.md b/contributors/design-proposals/api-machinery/metadata-policy.md index f924bc65..68f144a1 100644 --- a/contributors/design-proposals/api-machinery/metadata-policy.md +++ b/contributors/design-proposals/api-machinery/metadata-policy.md @@ -130,8 +130,3 @@ single scheduler, as opposed to choosing a scheduler, a desire mentioned in `MetadataPolicy` could be used. Issue #17324 proposes to create a generalized API for matching "claims" to "service classes"; matching a pod to a scheduler would be one use for such an API. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/api-machinery/protobuf.md b/contributors/design-proposals/api-machinery/protobuf.md index 1203c42f..455cc955 100644 --- a/contributors/design-proposals/api-machinery/protobuf.md +++ b/contributors/design-proposals/api-machinery/protobuf.md @@ -473,8 +473,3 @@ The generated protobuf will be checked with a verify script before merging. ## Open Questions * Is supporting stored protobuf files on disk in the kubectl client worth it? - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/api-machinery/server-get.md b/contributors/design-proposals/api-machinery/server-get.md index 085feb41..ef68e125 100644 --- a/contributors/design-proposals/api-machinery/server-get.md +++ b/contributors/design-proposals/api-machinery/server-get.md @@ -177,7 +177,3 @@ fall back to client side functions. Server side code would reuse the existing display functions but replace TabWriter with either a structured writer or the tabular form. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/api-machinery/synchronous-garbage-collection.md b/contributors/design-proposals/api-machinery/synchronous-garbage-collection.md index 66518620..df4595c9 100644 --- a/contributors/design-proposals/api-machinery/synchronous-garbage-collection.md +++ b/contributors/design-proposals/api-machinery/synchronous-garbage-collection.md @@ -167,7 +167,3 @@ To make the new kubectl compatible with the 1.4 and earlier masters, kubectl nee 1.4 `kubectl delete rc/rs` uses `DeleteOptions.OrphanDependents=true`, which is going to be converted to `DeletePropagationBackground` (see [API Design](#api-changes)) by a 1.5 master, so its behavior keeps the same. Pre 1.4 `kubectl delete` uses `DeleteOptions.OrphanDependents=nil`, so does the 1.4 `kubectl delete` for resources other than rc and rs. The option is going to be converted to `DeletePropagationDefault` (see [API Design](#api-changes)) by a 1.5 master, so these commands behave the same as when working with a 1.4 master. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/apps/OBSOLETE_templates.md b/contributors/design-proposals/apps/OBSOLETE_templates.md index 50712932..a1213830 100644 --- a/contributors/design-proposals/apps/OBSOLETE_templates.md +++ b/contributors/design-proposals/apps/OBSOLETE_templates.md @@ -562,8 +562,3 @@ Openshift handles template processing via a server endpoint which consumes a tem produced by processing the template. It is also possible to handle the entire template processing flow via the client, but this was deemed undesirable as it would force each client tool to reimplement template processing (e.g. the standard CLI tool, an eclipse plugin, a plugin for a CI system like Jenkins, etc). The assumption in this proposal is that server side template processing is the preferred implementation approach for this reason. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/apps/cronjob.md b/contributors/design-proposals/apps/cronjob.md index 1ce926ea..41ae7a47 100644 --- a/contributors/design-proposals/apps/cronjob.md +++ b/contributors/design-proposals/apps/cronjob.md @@ -333,7 +333,3 @@ Below are the possible future extensions to the Job controller: happening in [#18827](https://issues.k8s.io/18827). * Be able to specify more general template in `.spec` field, to create arbitrary types of resources. This relates to the work happening in [#18215](https://issues.k8s.io/18215). - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/apps/daemon.md b/contributors/design-proposals/apps/daemon.md index 7edc2c25..bd2f281e 100644 --- a/contributors/design-proposals/apps/daemon.md +++ b/contributors/design-proposals/apps/daemon.md @@ -201,7 +201,3 @@ restartPolicy set to Always. - Should work similarly to [Deployment](http://issues.k8s.io/1743). - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/apps/deploy.md b/contributors/design-proposals/apps/deploy.md index 0cc5dec0..5e5ac75a 100644 --- a/contributors/design-proposals/apps/deploy.md +++ b/contributors/design-proposals/apps/deploy.md @@ -138,7 +138,3 @@ Users sometimes need to temporarily disable a deployment. See issue [#14516](htt ### Perm-failed Deployments The deployment could be marked as "permanently failed" for a given spec hash so that the system won't continue thrashing on a doomed deployment. The users can retry a failed deployment with `kubectl rollout retry`. See issue [#14519](https://github.com/kubernetes/kubernetes/issues/14519). - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/apps/deployment.md b/contributors/design-proposals/apps/deployment.md index 5256ffeb..16c35dfe 100644 --- a/contributors/design-proposals/apps/deployment.md +++ b/contributors/design-proposals/apps/deployment.md @@ -257,8 +257,3 @@ Apart from the above, we want to add support for the following: - https://github.com/kubernetes/kubernetes/issues/1743 has most of the discussion that resulted in this proposal. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/apps/indexed-job.md b/contributors/design-proposals/apps/indexed-job.md index bc2860b9..84d68653 100644 --- a/contributors/design-proposals/apps/indexed-job.md +++ b/contributors/design-proposals/apps/indexed-job.md @@ -894,7 +894,3 @@ is verbose. For StatefulSet, this is less of a problem. This differs from StatefulSet in that StatefulSet uses names and not indexes. StatefulSet is intended to support ones to tens of things. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/apps/job.md b/contributors/design-proposals/apps/job.md index 4028de33..2094b125 100644 --- a/contributors/design-proposals/apps/job.md +++ b/contributors/design-proposals/apps/job.md @@ -206,7 +206,3 @@ Below are the possible future extensions to the Job controller: by providing pointers to Pods in the JobStatus ([see comment](https://github.com/kubernetes/kubernetes/pull/11746/files#r37142628)). * help users avoid non-unique label selectors ([see this proposal](../../docs/design/selector-generation.md)) - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/apps/selector-generation.md b/contributors/design-proposals/apps/selector-generation.md index 9b4b51fa..e0b3bf22 100644 --- a/contributors/design-proposals/apps/selector-generation.md +++ b/contributors/design-proposals/apps/selector-generation.md @@ -174,7 +174,3 @@ Docs will be edited to show examples without a `job.spec.selector`. We probably want as much as possible the same behavior for Job and ReplicationController. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/apps/stateful-apps.md b/contributors/design-proposals/apps/stateful-apps.md index 9a6cbf99..286f57da 100644 --- a/contributors/design-proposals/apps/stateful-apps.md +++ b/contributors/design-proposals/apps/stateful-apps.md @@ -355,9 +355,3 @@ Requested features: StatefulSets were formerly known as PetSets and were renamed to be less "cutesy" and more descriptive as a prerequisite to moving to beta. No animals were harmed in the making of this proposal. - - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/architecture/architecture.md b/contributors/design-proposals/architecture/architecture.md index 4d5d7ad0..367d7e20 100644 --- a/contributors/design-proposals/architecture/architecture.md +++ b/contributors/design-proposals/architecture/architecture.md @@ -246,7 +246,3 @@ itself: A single Kubernetes cluster may span multiple availability zones. However, for the highest availability, we recommend using [cluster federation](../multicluster/federation.md). - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/architecture/identifiers.md b/contributors/design-proposals/architecture/identifiers.md index a37411f9..977c0c99 100644 --- a/contributors/design-proposals/architecture/identifiers.md +++ b/contributors/design-proposals/architecture/identifiers.md @@ -107,7 +107,3 @@ from whence it came. unique across time. 1. This may correspond to Docker's container ID. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/architecture/namespaces.md b/contributors/design-proposals/architecture/namespaces.md index b0cd2129..a5536cba 100644 --- a/contributors/design-proposals/architecture/namespaces.md +++ b/contributors/design-proposals/architecture/namespaces.md @@ -363,8 +363,3 @@ storage. At this point, all content associated with that Namespace, and the Namespace itself are gone. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/architecture/principles.md b/contributors/design-proposals/architecture/principles.md index e0f513f8..ae98d660 100644 --- a/contributors/design-proposals/architecture/principles.md +++ b/contributors/design-proposals/architecture/principles.md @@ -96,7 +96,3 @@ TODO * [Eric Raymond's 17 UNIX rules](https://en.wikipedia.org/wiki/Unix_philosophy#Eric_Raymond.E2.80.99s_17_Unix_Rules) - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/auth/access.md b/contributors/design-proposals/auth/access.md index b23e463b..549a922d 100644 --- a/contributors/design-proposals/auth/access.md +++ b/contributors/design-proposals/auth/access.md @@ -370,7 +370,3 @@ Improvements: - Policies to drop logging for high rate trusted API calls, or by users performing audit or other sensitive functions. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/auth/apparmor.md b/contributors/design-proposals/auth/apparmor.md index 825427bf..34ecf978 100644 --- a/contributors/design-proposals/auth/apparmor.md +++ b/contributors/design-proposals/auth/apparmor.md @@ -300,7 +300,3 @@ documentation for following this process in a Kubernetes environment. ``` $ apparmor_parser --remove /path/to/profile ``` - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/auth/enhance-pluggable-policy.md b/contributors/design-proposals/auth/enhance-pluggable-policy.md index 14fff3dd..29eff236 100644 --- a/contributors/design-proposals/auth/enhance-pluggable-policy.md +++ b/contributors/design-proposals/auth/enhance-pluggable-policy.md @@ -422,8 +422,3 @@ type LocalResourceAccessReviewResponse struct { Groups []string } ``` - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/auth/image-provenance.md b/contributors/design-proposals/auth/image-provenance.md index d80ec684..942ea416 100644 --- a/contributors/design-proposals/auth/image-provenance.md +++ b/contributors/design-proposals/auth/image-provenance.md @@ -324,8 +324,3 @@ Additionally, just sending all the fields of just the Pod kind also has problems - because we do not know which fields of an object are inspected by the backend, caching of decisions is not effective. Sending fewer fields allows caching. - sending fewer fields makes it possible to rev the version of the webhook request slower than the version of our internal objects (e.g. pod v2 could still use imageReview v1.) probably lots more reasons. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/auth/pod-security-context.md b/contributors/design-proposals/auth/pod-security-context.md index bfaffa59..29ff7ff0 100644 --- a/contributors/design-proposals/auth/pod-security-context.md +++ b/contributors/design-proposals/auth/pod-security-context.md @@ -368,7 +368,3 @@ E2E test cases will be added to test the correct determination of the security c 1. The Kubelet will use the new fields on the `PodSecurityContext` for host namespace control 2. The Kubelet will be modified to correctly implement the backward compatibility and effective security context determination defined here - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/auth/secrets.md b/contributors/design-proposals/auth/secrets.md index 29d18411..d0b69719 100644 --- a/contributors/design-proposals/auth/secrets.md +++ b/contributors/design-proposals/auth/secrets.md @@ -622,7 +622,3 @@ on their filesystems: /etc/secret-volume/username /etc/secret-volume/password - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/auth/security.md b/contributors/design-proposals/auth/security.md index b1aeacbd..846b2c39 100644 --- a/contributors/design-proposals/auth/security.md +++ b/contributors/design-proposals/auth/security.md @@ -212,7 +212,3 @@ a separate component that can delete bindings but not create them). The scheduler may need read access to user or project-container information to determine preferential location (underspecified at this time). - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/auth/security_context.md b/contributors/design-proposals/auth/security_context.md index 76bc8ee8..d7a3e458 100644 --- a/contributors/design-proposals/auth/security_context.md +++ b/contributors/design-proposals/auth/security_context.md @@ -186,7 +186,3 @@ privileged. Contexts that attempt to define a UID or SELinux options will be denied by default. In the future the admission plugin will base this decision upon configurable policies that reside within the [service account](http://pr.k8s.io/2297). - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/auth/service_accounts.md b/contributors/design-proposals/auth/service_accounts.md index 79902140..af72e467 100644 --- a/contributors/design-proposals/auth/service_accounts.md +++ b/contributors/design-proposals/auth/service_accounts.md @@ -204,7 +204,3 @@ Finally, it may provide an interface to automate creation of new serviceAccounts. In that case, the user may want to GET serviceAccounts to see what has been created. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/autoscaling/horizontal-pod-autoscaler.md b/contributors/design-proposals/autoscaling/horizontal-pod-autoscaler.md index 1ac9c24b..98ad92ef 100644 --- a/contributors/design-proposals/autoscaling/horizontal-pod-autoscaler.md +++ b/contributors/design-proposals/autoscaling/horizontal-pod-autoscaler.md @@ -254,10 +254,3 @@ autoscaler to create a new pod. Discussed in issue [#3247](https://github.com/k * *[future]* **When scaling down, make more educated decision which pods to kill.** E.g.: if two or more pods from the same replication controller are on the same node, kill one of them. Discussed in issue [#4301](https://github.com/kubernetes/kubernetes/issues/4301). - - - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/autoscaling/hpa-v2.md b/contributors/design-proposals/autoscaling/hpa-v2.md index 9f814ef5..22d3fe22 100644 --- a/contributors/design-proposals/autoscaling/hpa-v2.md +++ b/contributors/design-proposals/autoscaling/hpa-v2.md @@ -285,7 +285,3 @@ come from the [custom metrics API](custom-metrics-api.md), which is an adapter API which sources metrics directly from the monitoring pipeline. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/autoscaling/initial-resources.md b/contributors/design-proposals/autoscaling/initial-resources.md index 432f6021..3462a204 100644 --- a/contributors/design-proposals/autoscaling/initial-resources.md +++ b/contributors/design-proposals/autoscaling/initial-resources.md @@ -70,6 +70,3 @@ and should be introduced shortly after the first version is done: * add estimation as annotations for those containers that already has resources set * support for other data sources like [Hawkular](http://www.hawkular.org/) -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/aws/aws_under_the_hood.md b/contributors/design-proposals/aws/aws_under_the_hood.md index 13ad435e..603e794a 100644 --- a/contributors/design-proposals/aws/aws_under_the_hood.md +++ b/contributors/design-proposals/aws/aws_under_the_hood.md @@ -303,8 +303,3 @@ These scripts are responsible for mounting and formatting volumes, downloading Salt and Kubernetes from the S3 bucket, and then triggering Salt to actually install Kubernetes. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/cli/kubectl-extension.md b/contributors/design-proposals/cli/kubectl-extension.md index 8764e74e..1589f4c3 100644 --- a/contributors/design-proposals/cli/kubectl-extension.md +++ b/contributors/design-proposals/cli/kubectl-extension.md @@ -1,36 +1,3 @@ -<!-- BEGIN MUNGE: UNVERSIONED_WARNING --> - -<!-- BEGIN STRIP_FOR_RELEASE --> - -<img src="http://kubernetes.io/kubernetes/img/warning.png" alt="WARNING" - width="25" height="25"> -<img src="http://kubernetes.io/kubernetes/img/warning.png" alt="WARNING" - width="25" height="25"> -<img src="http://kubernetes.io/kubernetes/img/warning.png" alt="WARNING" - width="25" height="25"> -<img src="http://kubernetes.io/kubernetes/img/warning.png" alt="WARNING" - width="25" height="25"> -<img src="http://kubernetes.io/kubernetes/img/warning.png" alt="WARNING" - width="25" height="25"> - -<h2>PLEASE NOTE: This document applies to the HEAD of the source tree</h2> - -If you are using a released version of Kubernetes, you should -refer to the docs that go with that version. - -<!-- TAG RELEASE_LINK, added by the munger automatically --> -<strong> -The latest release of this document can be found -[here](http://releases.k8s.io/release-1.3/docs/proposals/kubectl-extension.md). - -Documentation for other releases can be found at -[releases.k8s.io](http://releases.k8s.io). -</strong> --- - -<!-- END STRIP_FOR_RELEASE --> - -<!-- END MUNGE: UNVERSIONED_WARNING --> # Kubectl Extension diff --git a/contributors/design-proposals/cli/kubectl-login.md b/contributors/design-proposals/cli/kubectl-login.md index a333e9dc..01ab19bd 100644 --- a/contributors/design-proposals/cli/kubectl-login.md +++ b/contributors/design-proposals/cli/kubectl-login.md @@ -214,7 +214,3 @@ Phase 2: Further improvements will require adding more authentication providers, and adapting existing plugins to take advantage of challenge based authentication. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/cli/kubectl_apply_getsetdiff_last_applied_config.md b/contributors/design-proposals/cli/kubectl_apply_getsetdiff_last_applied_config.md index 67bcc860..af3c0ff8 100644 --- a/contributors/design-proposals/cli/kubectl_apply_getsetdiff_last_applied_config.md +++ b/contributors/design-proposals/cli/kubectl_apply_getsetdiff_last_applied_config.md @@ -190,7 +190,3 @@ instead of by the configuration. 4. Verify the last-applied-config has been updated - `kubectl apply view-last-applied -f deployment_nginx.yaml` - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/cli/simple-rolling-update.md b/contributors/design-proposals/cli/simple-rolling-update.md index c4a5f671..ea385311 100644 --- a/contributors/design-proposals/cli/simple-rolling-update.md +++ b/contributors/design-proposals/cli/simple-rolling-update.md @@ -124,8 +124,3 @@ rollout with the old version * Set `desired-replicas` annotation on `foo` to match the annotation on `foo-next` * Goto Rollout with `foo` and `foo-next` trading places. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/cloud-provider/cloud-provider-refactoring.md b/contributors/design-proposals/cloud-provider/cloud-provider-refactoring.md index e716d90b..0d25ccab 100644 --- a/contributors/design-proposals/cloud-provider/cloud-provider-refactoring.md +++ b/contributors/design-proposals/cloud-provider/cloud-provider-refactoring.md @@ -161,8 +161,3 @@ Release 1.9: All of the legacy cloud providers will be completely removed in thi * Cloud specific operations will be moved out of kube-apiserver using the external admission controller pattern mentioned above. * All cloud specific volume controller loops (attach, detach, provision operation controllers) will be switched to using flex volumes. Flex volumes do not need in-tree cloud specific calls. * As the final step, all of the cloud provider specific code will be moved out of tree. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/cluster-lifecycle/bootstrap-discovery.md b/contributors/design-proposals/cluster-lifecycle/bootstrap-discovery.md index 210c91be..e9dad621 100644 --- a/contributors/design-proposals/cluster-lifecycle/bootstrap-discovery.md +++ b/contributors/design-proposals/cluster-lifecycle/bootstrap-discovery.md @@ -242,7 +242,3 @@ The binding of the `system:bootstrappers` (or similar) group to the ability to s - Initial proposal ([@jbeda](https://github.com/jbeda)): [link](https://github.com/kubernetes/community/blob/cb9f198a0763e0a7540cdcc9db912a403ab1acab/contributors/design-proposals/bootstrap-discovery.md) - v1.6 updates ([@jbeda](https://github.com/jbeda)): [link](https://github.com/kubernetes/community/blob/d8ce9e91b0099795318bb06c13f00d9dad41ac26/contributors/design-proposals/bootstrap-discovery.md) - v1.8 updates ([@luxas](https://github.com/luxas)) - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/cluster-lifecycle/cluster-deployment.md b/contributors/design-proposals/cluster-lifecycle/cluster-deployment.md index e9ca8d54..12ed2cf4 100644 --- a/contributors/design-proposals/cluster-lifecycle/cluster-deployment.md +++ b/contributors/design-proposals/cluster-lifecycle/cluster-deployment.md @@ -165,7 +165,3 @@ this by distributing deployment scripts via a docker image so that user will run ```docker run gcr.io/google_containers/deploy_kubernetes:v1.2 up --num-nodes=3 --provider=aws``` - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/cluster-lifecycle/clustering.md b/contributors/design-proposals/cluster-lifecycle/clustering.md index ca42035b..e681d8e9 100644 --- a/contributors/design-proposals/cluster-lifecycle/clustering.md +++ b/contributors/design-proposals/cluster-lifecycle/clustering.md @@ -121,8 +121,3 @@ the `queue` policy defined above. This manual intervention could be replaced by code that can verify the signing requests via other means.  - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/cluster-lifecycle/clustering/README.md b/contributors/design-proposals/cluster-lifecycle/clustering/README.md index d7e2e2e0..9fe1f027 100644 --- a/contributors/design-proposals/cluster-lifecycle/clustering/README.md +++ b/contributors/design-proposals/cluster-lifecycle/clustering/README.md @@ -29,7 +29,3 @@ If you have the fswatch utility installed, you can have it monitor the file system and automatically rebuild when files have changed. Just do a `make watch`. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/cluster-lifecycle/dramatically-simplify-cluster-creation.md b/contributors/design-proposals/cluster-lifecycle/dramatically-simplify-cluster-creation.md index 78a1089a..a76e11da 100644 --- a/contributors/design-proposals/cluster-lifecycle/dramatically-simplify-cluster-creation.md +++ b/contributors/design-proposals/cluster-lifecycle/dramatically-simplify-cluster-creation.md @@ -259,8 +259,3 @@ It also doesn't require kubelet to do TLS bootstrapping - kubeadm handles that. ## See also * [Joe Beda's "K8s the hard way easier"](https://docs.google.com/document/d/1lJ26LmCP-I_zMuqs6uloTgAnHPcuT7kOYtQ7XSgYLMA/edit#heading=h.ilgrv18sg5t) which combines Kelsey's "Kubernetes the hard way" with history of proposed UX at the end (scroll all the way down to the bottom). - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/cluster-lifecycle/ha_master.md b/contributors/design-proposals/cluster-lifecycle/ha_master.md index b225e667..3d0de1f1 100644 --- a/contributors/design-proposals/cluster-lifecycle/ha_master.md +++ b/contributors/design-proposals/cluster-lifecycle/ha_master.md @@ -231,6 +231,3 @@ will be in the same version. * Apiserver talks only to a local etcd replica which will be in a compatible version * We assume we will introduce this setup after we upgrade to etcd v3 so we don't need to cover upgrading database. -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/cluster-lifecycle/high-availability.md b/contributors/design-proposals/cluster-lifecycle/high-availability.md index 4026ebe7..d893c597 100644 --- a/contributors/design-proposals/cluster-lifecycle/high-availability.md +++ b/contributors/design-proposals/cluster-lifecycle/high-availability.md @@ -2,7 +2,3 @@ This document is deprecated. For more details about running a highly available cluster master, please see the [admin instructions document](https://kubernetes.io/docs/admin/high-availability/). - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/cluster-lifecycle/kubelet-tls-bootstrap.md b/contributors/design-proposals/cluster-lifecycle/kubelet-tls-bootstrap.md index 75d90b4c..f725b1a9 100644 --- a/contributors/design-proposals/cluster-lifecycle/kubelet-tls-bootstrap.md +++ b/contributors/design-proposals/cluster-lifecycle/kubelet-tls-bootstrap.md @@ -237,7 +237,3 @@ auth. - supplemental policy (e.g. cluster CA only issues 30-day certs for hostnames *.k8s.example.com, each new cert must have fresh keys, ...) - fully automated provisioning (using a handshake protocol or external list of authorized machines) - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/cluster-lifecycle/local-cluster-ux.md b/contributors/design-proposals/cluster-lifecycle/local-cluster-ux.md index 26ac926d..8dac84bd 100644 --- a/contributors/design-proposals/cluster-lifecycle/local-cluster-ux.md +++ b/contributors/design-proposals/cluster-lifecycle/local-cluster-ux.md @@ -154,8 +154,3 @@ minikube -> docker -> localkube - The latest version of Minikube is guaranteed to support the latest release of Kubernetes, including documentation. - The Google Cloud SDK will package minikube and provide utilities for configuring kubectl to use it, but will not in any other way wrap minikube. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/cluster-lifecycle/runtimeconfig.md b/contributors/design-proposals/cluster-lifecycle/runtimeconfig.md index b2ed83dd..c247eff8 100644 --- a/contributors/design-proposals/cluster-lifecycle/runtimeconfig.md +++ b/contributors/design-proposals/cluster-lifecycle/runtimeconfig.md @@ -64,6 +64,3 @@ APIs and not flags ([#12245](https://issues.k8s.io/12245)). When that is added, could be handled by versioned component config and the component flags deprecated. -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/cluster-lifecycle/self-hosted-kubelet.md b/contributors/design-proposals/cluster-lifecycle/self-hosted-kubelet.md index d2318bea..765086f2 100644 --- a/contributors/design-proposals/cluster-lifecycle/self-hosted-kubelet.md +++ b/contributors/design-proposals/cluster-lifecycle/self-hosted-kubelet.md @@ -128,8 +128,3 @@ register itself with a given taint when it first contacts the API server. Given that, a kubelet could register itself with a given taint such as “component=kubelet”, and a kubelet pod could exist that has a toleration to that taint, ensuring it is the only pod the “bootstrap” kubelet runs. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/instrumentation/core-metrics-pipeline.md b/contributors/design-proposals/instrumentation/core-metrics-pipeline.md index 7da3e61e..7a355e59 100644 --- a/contributors/design-proposals/instrumentation/core-metrics-pipeline.md +++ b/contributors/design-proposals/instrumentation/core-metrics-pipeline.md @@ -148,7 +148,3 @@ Suggested, tentative future work, which may be covered by future proposals: - Decide on the format, name, and kubelet endpoint for publishing these metrics. - Integrate with the CRI to allow compatibility with a greater number of runtimes, and to create a better runtime abstraction. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/instrumentation/monitoring_architecture.md b/contributors/design-proposals/instrumentation/monitoring_architecture.md index e60f274c..1b4cd206 100644 --- a/contributors/design-proposals/instrumentation/monitoring_architecture.md +++ b/contributors/design-proposals/instrumentation/monitoring_architecture.md @@ -196,8 +196,3 @@ Prometheus format.  - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/instrumentation/performance-related-monitoring.md b/contributors/design-proposals/instrumentation/performance-related-monitoring.md index 7937dbdd..145d0d29 100644 --- a/contributors/design-proposals/instrumentation/performance-related-monitoring.md +++ b/contributors/design-proposals/instrumentation/performance-related-monitoring.md @@ -110,7 +110,3 @@ We should monitor other aspects of the system, which may indicate saturation of Basic ideas: - queue length for queues in the system, - wait time for WaitGroups. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/instrumentation/resource-metrics-api.md b/contributors/design-proposals/instrumentation/resource-metrics-api.md index 3e3df2be..b5840b75 100644 --- a/contributors/design-proposals/instrumentation/resource-metrics-api.md +++ b/contributors/design-proposals/instrumentation/resource-metrics-api.md @@ -146,6 +146,3 @@ Depending on the further requirements the following features may be added: - possibility to query for window sizes and aggregation functions (though single window size/aggregation function per request) - cluster level metrics -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/multi-platform.md b/contributors/design-proposals/multi-platform.md index 8606d410..99c37bba 100644 --- a/contributors/design-proposals/multi-platform.md +++ b/contributors/design-proposals/multi-platform.md @@ -527,6 +527,3 @@ The 30th of November 2015, a tracking issue about making Kubernetes run on ARM w The 27th of April 2016, Kubernetes `v1.3.0-alpha.3` was released, and it became the first release that was able to run the [docker getting started guide](http://kubernetes.io/docs/getting-started-guides/docker/) on `linux/amd64`, `linux/arm`, `linux/arm64` and `linux/ppc64le` without any modification. -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/multicluster/control-plane-resilience.md b/contributors/design-proposals/multicluster/control-plane-resilience.md index 7b30f588..174e7de0 100644 --- a/contributors/design-proposals/multicluster/control-plane-resilience.md +++ b/contributors/design-proposals/multicluster/control-plane-resilience.md @@ -233,7 +233,3 @@ be automated and continuously tested. </tr> </table> - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/multicluster/federated-api-servers.md b/contributors/design-proposals/multicluster/federated-api-servers.md index ff214c23..00b1c23b 100644 --- a/contributors/design-proposals/multicluster/federated-api-servers.md +++ b/contributors/design-proposals/multicluster/federated-api-servers.md @@ -2,7 +2,3 @@ Moved to [aggregated-api-servers.md](../api-machinery/aggregated-api-servers.md) since cluster federation stole the word "federation" from this effort and it was very confusing. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/multicluster/federated-ingress.md b/contributors/design-proposals/multicluster/federated-ingress.md index 07e75b0c..c2cb3793 100644 --- a/contributors/design-proposals/multicluster/federated-ingress.md +++ b/contributors/design-proposals/multicluster/federated-ingress.md @@ -188,7 +188,3 @@ Assuming that GCP-only (see above) is complete: In theory the same approach as "Cross-cloud via GCP" above could be used, except that AWS infrastructure would be used to get traffic first to an AWS cluster, and then proxied onwards to non-AWS and/or on-prem clusters. Detail docs TBD. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/multicluster/federated-replicasets.md b/contributors/design-proposals/multicluster/federated-replicasets.md index 8b48731c..9ed57bc7 100644 --- a/contributors/design-proposals/multicluster/federated-replicasets.md +++ b/contributors/design-proposals/multicluster/federated-replicasets.md @@ -506,8 +506,3 @@ target cluster, to watch changes in every target cluster etcd regarding the posted LRS's and if any violation from the scheduled number of replicase is detected the scheduling code is re-called for re-scheduling purposes. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/multicluster/federated-services.md b/contributors/design-proposals/multicluster/federated-services.md index 8ec9ca29..a43726d4 100644 --- a/contributors/design-proposals/multicluster/federated-services.md +++ b/contributors/design-proposals/multicluster/federated-services.md @@ -513,7 +513,3 @@ state, and apply changes to the underlying kubernetes clusters accordingly. They also have the anti-entropy mechanism for reconciling Cluster Federation "desired desired" state against kubernetes "actual desired" state. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/multicluster/federation-lite.md b/contributors/design-proposals/multicluster/federation-lite.md index 549f98df..afdd6c02 100644 --- a/contributors/design-proposals/multicluster/federation-lite.md +++ b/contributors/design-proposals/multicluster/federation-lite.md @@ -195,7 +195,3 @@ Initially therefore, the GCE changes will be to: 1. change the kubernetes cloud provider to iterate through relevant zones when resolving items 1. tag GCE PD volumes with the appropriate zone information - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/multicluster/federation-phase-1.md b/contributors/design-proposals/multicluster/federation-phase-1.md index 157b5668..25d27ee6 100644 --- a/contributors/design-proposals/multicluster/federation-phase-1.md +++ b/contributors/design-proposals/multicluster/federation-phase-1.md @@ -400,8 +400,3 @@ This part has been included in the section “Federated Service” of document “[Federated Cross-cluster Load Balancing and Service Discovery Requirements and System Design](federated-services.md))”. Please refer to that document for details. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/multicluster/federation.md b/contributors/design-proposals/multicluster/federation.md index fc595123..21c159d7 100644 --- a/contributors/design-proposals/multicluster/federation.md +++ b/contributors/design-proposals/multicluster/federation.md @@ -641,8 +641,3 @@ does each replica find the other replicas and how do clients find their primary zookeeper replica? And now how do I do a shared, highly available redis database? Use a few common specific use cases like this to flesh out the detailed API and semantics of Cluster Federation. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/network/command_execution_port_forwarding.md b/contributors/design-proposals/network/command_execution_port_forwarding.md index a7175403..b4545662 100644 --- a/contributors/design-proposals/network/command_execution_port_forwarding.md +++ b/contributors/design-proposals/network/command_execution_port_forwarding.md @@ -152,7 +152,3 @@ forwarding connections from different clients are not able to see each other's data. This can most likely be achieved via SELinux labeling and unique process contexts. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/network/flannel-integration.md b/contributors/design-proposals/network/flannel-integration.md index 465ee5e6..3448ab28 100644 --- a/contributors/design-proposals/network/flannel-integration.md +++ b/contributors/design-proposals/network/flannel-integration.md @@ -126,7 +126,3 @@ This proposal is really just a call for community help in writing a Kubernetes x * Investigate flannel server running on every node (as done in the reference implementation mentioned above) * Use flannel reservation mode to support node controller podcidr allocation - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/network/network-policy.md b/contributors/design-proposals/network/network-policy.md index 32f7c016..6a4b01a8 100644 --- a/contributors/design-proposals/network/network-policy.md +++ b/contributors/design-proposals/network/network-policy.md @@ -297,8 +297,3 @@ spec: ## References - https://github.com/kubernetes/kubernetes/issues/22469 tracks network policy in kubernetes. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/network/networking.md b/contributors/design-proposals/network/networking.md index 89b600df..6540a567 100644 --- a/contributors/design-proposals/network/networking.md +++ b/contributors/design-proposals/network/networking.md @@ -186,7 +186,3 @@ AWS started rolling out basic but direct ipv6 assignment to instances doesn't appear to be supported by other major cloud providers (e.g. GCE) yet. We'd happily take pull requests from people running Kubernetes on bare metal, though. :-) - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/network/service-discovery.md b/contributors/design-proposals/network/service-discovery.md index 66e497e7..c3da6b2b 100644 --- a/contributors/design-proposals/network/service-discovery.md +++ b/contributors/design-proposals/network/service-discovery.md @@ -60,10 +60,3 @@ The fragment below is taken from the service section of the kubernetes.json were Five service annotations are proposed as a standard way to describe a service endpoint. These five annotation are promoted as a Kubernetes standard, so that services can be discovered and a service catalog can be build to facilitate service consumers. - - - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/network/service-external-name.md b/contributors/design-proposals/network/service-external-name.md index eaab4c51..69073f8b 100644 --- a/contributors/design-proposals/network/service-external-name.md +++ b/contributors/design-proposals/network/service-external-name.md @@ -154,8 +154,3 @@ result in a failure during server certificate validation. This is acknowledged and left for future consideration. For the time being, users and administrators might need to ensure that the server certificates also mentions the Kubernetes name as an alternate host name. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/all-in-one-volume.md b/contributors/design-proposals/node/all-in-one-volume.md index 9c91f102..e1796817 100644 --- a/contributors/design-proposals/node/all-in-one-volume.md +++ b/contributors/design-proposals/node/all-in-one-volume.md @@ -299,8 +299,3 @@ spec: path: my-group/my-password mode: 511 ``` - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/annotations-downward-api.md b/contributors/design-proposals/node/annotations-downward-api.md index 8b6933d5..dcad5ab1 100644 --- a/contributors/design-proposals/node/annotations-downward-api.md +++ b/contributors/design-proposals/node/annotations-downward-api.md @@ -62,6 +62,3 @@ env: In general, this environment downward API part will be implemented in the same place as the other metadata - as a label conversion function. -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/configmap.md b/contributors/design-proposals/node/configmap.md index 658ac73b..55571448 100644 --- a/contributors/design-proposals/node/configmap.md +++ b/contributors/design-proposals/node/configmap.md @@ -294,7 +294,3 @@ spec: In the future, we may add the ability to specify an init-container that can watch the volume contents for updates and respond to changes when they occur. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/container-init.md b/contributors/design-proposals/node/container-init.md index 8b955c87..e26f92b4 100644 --- a/contributors/design-proposals/node/container-init.md +++ b/contributors/design-proposals/node/container-init.md @@ -438,7 +438,3 @@ master and Kubelet is tracked in issue [#4855](https://github.com/kubernetes/kub * Unify pod QoS class with init containers * Implement container / image volumes to make composition of runtime from images efficient - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/container-runtime-interface-v1.md b/contributors/design-proposals/node/container-runtime-interface-v1.md index e8e55c00..9e89abf5 100644 --- a/contributors/design-proposals/node/container-runtime-interface-v1.md +++ b/contributors/design-proposals/node/container-runtime-interface-v1.md @@ -260,8 +260,3 @@ can potentially become a very thin daemon. * Metrics: [#27097](https://issues.k8s.io/27097) * Log management: [#24677](https://issues.k8s.io/24677) - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/disk-accounting.md b/contributors/design-proposals/node/disk-accounting.md index d11c7a6f..eaee0ead 100644 --- a/contributors/design-proposals/node/disk-accounting.md +++ b/contributors/design-proposals/node/disk-accounting.md @@ -580,8 +580,3 @@ Capacity in MB = 1638400 * 512 * 128 bytes = 100 GB * If you use a non-default location for docker storage, change `/var/lib/docker` in the examples to your storage location. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/downward_api_resources_limits_requests.md b/contributors/design-proposals/node/downward_api_resources_limits_requests.md index bebf05ab..9c5872d0 100644 --- a/contributors/design-proposals/node/downward_api_resources_limits_requests.md +++ b/contributors/design-proposals/node/downward_api_resources_limits_requests.md @@ -616,7 +616,3 @@ and export GOMAXPROCS=$(CPU_LIMIT)" ``` - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/dynamic-kubelet-configuration.md b/contributors/design-proposals/node/dynamic-kubelet-configuration.md index 8ca0e99c..188fb84f 100644 --- a/contributors/design-proposals/node/dynamic-kubelet-configuration.md +++ b/contributors/design-proposals/node/dynamic-kubelet-configuration.md @@ -308,6 +308,3 @@ There is discussion in [#10179](https://github.com/kubernetes/kubernetes/issues/ + Reconciling configuration with objects added after the completion of a rollout, e.g. new `Nodes`. + Pausing/resuming a rollout. -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/envvar-configmap.md b/contributors/design-proposals/node/envvar-configmap.md index 5a398873..9464a1af 100644 --- a/contributors/design-proposals/node/envvar-configmap.md +++ b/contributors/design-proposals/node/envvar-configmap.md @@ -182,7 +182,3 @@ cm2_key2="b" Add similar support for Secrets. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/expansion.md b/contributors/design-proposals/node/expansion.md index 4f2f6f40..7e1c65fb 100644 --- a/contributors/design-proposals/node/expansion.md +++ b/contributors/design-proposals/node/expansion.md @@ -410,8 +410,3 @@ spec: value: "http://gitserver.$(POD_NAMESPACE):$(SERVICE_PORT)" restartPolicy: Never ``` - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/kubelet-auth.md b/contributors/design-proposals/node/kubelet-auth.md index c4d35dd9..cb34f65d 100644 --- a/contributors/design-proposals/node/kubelet-auth.md +++ b/contributors/design-proposals/node/kubelet-auth.md @@ -101,6 +101,3 @@ This mode allows any authenticated request. * Add support for CRL revocation for x509 client certificate authentication (http://issue.k8s.io/18982) -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/kubelet-cri-logging.md b/contributors/design-proposals/node/kubelet-cri-logging.md index 41c5cc9c..4c5f4450 100644 --- a/contributors/design-proposals/node/kubelet-cri-logging.md +++ b/contributors/design-proposals/node/kubelet-cri-logging.md @@ -233,8 +233,3 @@ evolves. [4] rkt support: https://github.com/systemd/systemd/pull/4179 - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/kubelet-eviction.md b/contributors/design-proposals/node/kubelet-eviction.md index 0b627b97..61caf170 100644 --- a/contributors/design-proposals/node/kubelet-eviction.md +++ b/contributors/design-proposals/node/kubelet-eviction.md @@ -472,8 +472,3 @@ for eviction. Instead `DaemonSet` should ideally include Guaranteed pods only. The pod eviction may evict more pods than needed due to stats collection timing gap. This can be mitigated by adding the ability to get root container stats on an on-demand basis (https://github.com/google/cadvisor/issues/1247) in the future. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/kubelet-hypercontainer-runtime.md b/contributors/design-proposals/node/kubelet-hypercontainer-runtime.md index c3da7d9a..8aba0b1a 100644 --- a/contributors/design-proposals/node/kubelet-hypercontainer-runtime.md +++ b/contributors/design-proposals/node/kubelet-hypercontainer-runtime.md @@ -38,8 +38,3 @@ runtime. The HyperContainer runtime is maintained by <https://github.com/kubernetes/frakti>. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/kubelet-rkt-runtime.md b/contributors/design-proposals/node/kubelet-rkt-runtime.md index 84aac8cc..98a06187 100644 --- a/contributors/design-proposals/node/kubelet-rkt-runtime.md +++ b/contributors/design-proposals/node/kubelet-rkt-runtime.md @@ -97,7 +97,3 @@ In the future, some of these decisions are expected to be changed such that rkt 5. Revendor rktlet into `pkg/kubelet/rktshim`, and start deprecating the `pkg/kubelet/rkt` package. 6. Eventually replace the current `pkg/kubelet/rkt` package. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/kubelet-systemd.md b/contributors/design-proposals/node/kubelet-systemd.md index b4277cfa..8c69dc8f 100644 --- a/contributors/design-proposals/node/kubelet-systemd.md +++ b/contributors/design-proposals/node/kubelet-systemd.md @@ -401,7 +401,3 @@ Some OS distributions will fix this bug in versions of docker <= 1.0.9, so opera be aware of how their version of `docker` was packaged when using this feature. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/node-allocatable.md b/contributors/design-proposals/node/node-allocatable.md index e4d3061a..76a1a423 100644 --- a/contributors/design-proposals/node/node-allocatable.md +++ b/contributors/design-proposals/node/node-allocatable.md @@ -334,8 +334,3 @@ according to `KubeReserved`. The community should be notified that an update to schedulers is recommended, but if a scheduler is not updated it falls under the above case of "scheduler is not allocatable-resources aware". - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/pod-lifecycle-event-generator.md b/contributors/design-proposals/node/pod-lifecycle-event-generator.md index 207d6a17..65afcd0a 100644 --- a/contributors/design-proposals/node/pod-lifecycle-event-generator.md +++ b/contributors/design-proposals/node/pod-lifecycle-event-generator.md @@ -194,8 +194,3 @@ redundant syncs. * Instruct pod workers to set up a wake-up call if syncing failed, so that it can retry. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/pod-pid-namespace.md b/contributors/design-proposals/node/pod-pid-namespace.md index 43c38f22..6ac16b3b 100644 --- a/contributors/design-proposals/node/pod-pid-namespace.md +++ b/contributors/design-proposals/node/pod-pid-namespace.md @@ -70,8 +70,3 @@ to disable the shared PID namespace in the subsequent release. [1]: https://blog.phusion.nl/2015/01/20/docker-and-the-pid-1-zombie-reaping-problem/ - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/propagation.md b/contributors/design-proposals/node/propagation.md index 09f68edd..3c665552 100644 --- a/contributors/design-proposals/node/propagation.md +++ b/contributors/design-proposals/node/propagation.md @@ -309,7 +309,3 @@ These concerns are valid and we decide to limit the propagation mode to HostPath volume only, in HostPath, we expect any runtime should NOT perform any additional actions (such as clean up). This behavior is also consistent with current HostPath logic: kube does not take care of the content in HostPath either. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/resource-qos.md b/contributors/design-proposals/node/resource-qos.md index 14057b03..d2afdcbd 100644 --- a/contributors/design-proposals/node/resource-qos.md +++ b/contributors/design-proposals/node/resource-qos.md @@ -213,6 +213,3 @@ A strict hierarchy of user-specified numerical priorities is not desirable becau 1. Achieved behavior would be emergent based on how users assigned priorities to their pods. No particular SLO could be delivered by the system, and usage would be subject to gaming if not restricted administratively 2. Changes to desired priority bands would require changes to all user pod configurations. -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/runtime-client-server.md b/contributors/design-proposals/node/runtime-client-server.md index 16cc677c..b50e003d 100644 --- a/contributors/design-proposals/node/runtime-client-server.md +++ b/contributors/design-proposals/node/runtime-client-server.md @@ -200,7 +200,3 @@ This proposal is first filed by [@brendandburns](https://github.com/brendandburn * [kubernetes/13709](https://github.com/kubernetes/kubernetes/pull/13079) * [New container runtime interface](https://github.com/kubernetes/kubernetes/pull/25899) - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/runtime-pod-cache.md b/contributors/design-proposals/node/runtime-pod-cache.md index d4926c3e..49236ba0 100644 --- a/contributors/design-proposals/node/runtime-pod-cache.md +++ b/contributors/design-proposals/node/runtime-pod-cache.md @@ -167,7 +167,3 @@ by such periods and should improve Kubelet's perceived responsiveness. - Deprecate the old runtime cache. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/seccomp.md b/contributors/design-proposals/node/seccomp.md index 794e758c..a979cc2a 100644 --- a/contributors/design-proposals/node/seccomp.md +++ b/contributors/design-proposals/node/seccomp.md @@ -261,6 +261,3 @@ spec: emptyDir: {} ``` -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/secret-configmap-downwardapi-file-mode.md b/contributors/design-proposals/node/secret-configmap-downwardapi-file-mode.md index f9b3b5af..85ee9ccc 100644 --- a/contributors/design-proposals/node/secret-configmap-downwardapi-file-mode.md +++ b/contributors/design-proposals/node/secret-configmap-downwardapi-file-mode.md @@ -180,7 +180,3 @@ The are two downside: the file permissions will be the same on all. This is already the case for Key mappings and doesn't seem like a big issue either. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/selinux-enhancements.md b/contributors/design-proposals/node/selinux-enhancements.md index 3b3e168a..aec5533b 100644 --- a/contributors/design-proposals/node/selinux-enhancements.md +++ b/contributors/design-proposals/node/selinux-enhancements.md @@ -203,7 +203,3 @@ ensure things work as expected under rkt. The `VolumeHost` abstraction is used in a couple of PV controllers as NOP implementations. These should be altered to no longer include `GetRootContext`. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/node/selinux.md b/contributors/design-proposals/node/selinux.md index ece83d44..6cde471d 100644 --- a/contributors/design-proposals/node/selinux.md +++ b/contributors/design-proposals/node/selinux.md @@ -310,8 +310,3 @@ to manage labels individually. This allows the volume plugins to determine when they do and don't want this type of support from the Kubelet, and allows the criteria each plugin uses to evolve without changing the Kubelet. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/release/release-notes.md b/contributors/design-proposals/release/release-notes.md index 41b3ac4e..42f5ff24 100644 --- a/contributors/design-proposals/release/release-notes.md +++ b/contributors/design-proposals/release/release-notes.md @@ -186,7 +186,3 @@ Other notable changes * For now contributors should simply use the first PR that enables a new feature by default. We'll revisit if this does not work well. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/release/versioning.md b/contributors/design-proposals/release/versioning.md index 5b8dd66d..05e7faed 100644 --- a/contributors/design-proposals/release/versioning.md +++ b/contributors/design-proposals/release/versioning.md @@ -126,7 +126,3 @@ to go from 1.x to 1.x+y before they go to 2.x. There is a separate question of how to track the capabilities of a kubelet to facilitate rolling upgrades. That is not addressed here. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/resource-management/admission_control_limit_range.md b/contributors/design-proposals/resource-management/admission_control_limit_range.md index 3684b636..7dd454c7 100644 --- a/contributors/design-proposals/resource-management/admission_control_limit_range.md +++ b/contributors/design-proposals/resource-management/admission_control_limit_range.md @@ -228,6 +228,3 @@ the following would happen. 3. If the container is later resized, it's cpu would be constrained to between .1 and 1 and the ratio of limit to request could not exceed 4. -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/resource-management/admission_control_resource_quota.md b/contributors/design-proposals/resource-management/admission_control_resource_quota.md index 575db9a8..6ce9cf01 100644 --- a/contributors/design-proposals/resource-management/admission_control_resource_quota.md +++ b/contributors/design-proposals/resource-management/admission_control_resource_quota.md @@ -210,6 +210,3 @@ services 0 5 See [resource quota document](../admin/resource-quota.md) and the [example of Resource Quota](../admin/resourcequota/) for more information. -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/resource-management/gpu-support.md b/contributors/design-proposals/resource-management/gpu-support.md index 98364414..ad4383ac 100644 --- a/contributors/design-proposals/resource-management/gpu-support.md +++ b/contributors/design-proposals/resource-management/gpu-support.md @@ -271,6 +271,3 @@ or roles to schedule GPU workloads. Overcommitting or sharing the same device across different pods is not considered safe. It should be possible to segregate such GPU-sharing pods by user, namespace or a combination thereof. -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/resource-management/resource-quota-scoping.md b/contributors/design-proposals/resource-management/resource-quota-scoping.md index 5cffb998..edc6ed32 100644 --- a/contributors/design-proposals/resource-management/resource-quota-scoping.md +++ b/contributors/design-proposals/resource-management/resource-quota-scoping.md @@ -326,8 +326,3 @@ Appropriate unit and e2e testing will be authored. Existing resource quota documentation and examples will be updated. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/scalability/kubemark.md b/contributors/design-proposals/scalability/kubemark.md index e5f4b26b..533295e0 100644 --- a/contributors/design-proposals/scalability/kubemark.md +++ b/contributors/design-proposals/scalability/kubemark.md @@ -151,7 +151,3 @@ In the future we want to add following capabilities to the Kubemark system: - replaying real traffic reconstructed from the recorded Events stream, - simulating scraping things running on Nodes through Master proxy. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/scalability/scalability-testing.md b/contributors/design-proposals/scalability/scalability-testing.md index ae3e3534..0195d7b1 100644 --- a/contributors/design-proposals/scalability/scalability-testing.md +++ b/contributors/design-proposals/scalability/scalability-testing.md @@ -66,7 +66,3 @@ as not to collide. Complications may currently exist around container tracking and ownership in docker. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/scheduling/multiple-schedulers.md b/contributors/design-proposals/scheduling/multiple-schedulers.md index 1ea1b45c..1581a0d9 100644 --- a/contributors/design-proposals/scheduling/multiple-schedulers.md +++ b/contributors/design-proposals/scheduling/multiple-schedulers.md @@ -133,6 +133,3 @@ randomly among the top N nodes instead of the one with the highest score. - [#16845](https://github.com/kubernetes/kubernetes/issues/16845): scheduling groups of pods - [#17208](https://github.com/kubernetes/kubernetes/issues/17208): guide to writing a new scheduler -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/scheduling/nodeaffinity.md b/contributors/design-proposals/scheduling/nodeaffinity.md index 61e04169..adab5dde 100644 --- a/contributors/design-proposals/scheduling/nodeaffinity.md +++ b/contributors/design-proposals/scheduling/nodeaffinity.md @@ -240,7 +240,3 @@ The main related issue is [#341](https://github.com/kubernetes/kubernetes/issues Issue [#367](https://github.com/kubernetes/kubernetes/issues/367) is also related. Those issues reference other related issues. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/scheduling/podaffinity.md b/contributors/design-proposals/scheduling/podaffinity.md index 30bdb256..01947728 100644 --- a/contributors/design-proposals/scheduling/podaffinity.md +++ b/contributors/design-proposals/scheduling/podaffinity.md @@ -666,8 +666,3 @@ This proposal is to satisfy [#14816](https://github.com/kubernetes/kubernetes/is ** TODO: cite references ** - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/scheduling/rescheduler.md b/contributors/design-proposals/scheduling/rescheduler.md index faf53564..df36464a 100644 --- a/contributors/design-proposals/scheduling/rescheduler.md +++ b/contributors/design-proposals/scheduling/rescheduler.md @@ -118,6 +118,3 @@ For scaling up the cluster, a reasonable workflow might be: 1. rescheduler triggers cluster auto-scaler to add a node of the appropriate type for the PENDING Pod 1. the PENDING Pod schedules onto the new node (and possibly the rescheduler also moves other Pods onto that node) -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/scheduling/rescheduling-for-critical-pods.md b/contributors/design-proposals/scheduling/rescheduling-for-critical-pods.md index 525e0805..835088fc 100644 --- a/contributors/design-proposals/scheduling/rescheduling-for-critical-pods.md +++ b/contributors/design-proposals/scheduling/rescheduling-for-critical-pods.md @@ -82,7 +82,3 @@ The rescheduler control loop will be as follow: * wait until scheduler will schedule the critical addon * if there is no more critical addons for which we can help, ensure there is no node with the taint - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/scheduling/rescheduling.md b/contributors/design-proposals/scheduling/rescheduling.md index 1966de79..bbe63809 100644 --- a/contributors/design-proposals/scheduling/rescheduling.md +++ b/contributors/design-proposals/scheduling/rescheduling.md @@ -487,7 +487,3 @@ TODO. TODO: Add reference to this doc from docs/proposals/rescheduler.md - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/scheduling/resources.md b/contributors/design-proposals/scheduling/resources.md index 6b01dbeb..27b69e87 100644 --- a/contributors/design-proposals/scheduling/resources.md +++ b/contributors/design-proposals/scheduling/resources.md @@ -364,7 +364,3 @@ second. * Units: operations per second * Compressible? yes - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/scheduling/scheduler_extender.md b/contributors/design-proposals/scheduling/scheduler_extender.md index 1903535a..6a1ca16a 100644 --- a/contributors/design-proposals/scheduling/scheduler_extender.md +++ b/contributors/design-proposals/scheduling/scheduler_extender.md @@ -120,6 +120,3 @@ type ExtenderBindingArgs struct { Node string } ``` -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/scheduling/taint-toleration-dedicated.md b/contributors/design-proposals/scheduling/taint-toleration-dedicated.md index c523319f..e451f395 100644 --- a/contributors/design-proposals/scheduling/taint-toleration-dedicated.md +++ b/contributors/design-proposals/scheduling/taint-toleration-dedicated.md @@ -283,9 +283,3 @@ The relationship between taints and node drains is discussed in [#1574](https:// The concepts of taints and tolerations were originally developed as part of the Omega project at Google. - - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/storage/persistent-storage.md b/contributors/design-proposals/storage/persistent-storage.md index 7d413218..d91ee256 100644 --- a/contributors/design-proposals/storage/persistent-storage.md +++ b/contributors/design-proposals/storage/persistent-storage.md @@ -286,7 +286,3 @@ reference from the PV and change the PVs status to 'Released'. Admins can script the recycling of released volumes. Future dynamic provisioners will understand how a volume should be recycled. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/storage/pod-safety.md b/contributors/design-proposals/storage/pod-safety.md index 10f7589b..b7c7e8e1 100644 --- a/contributors/design-proposals/storage/pod-safety.md +++ b/contributors/design-proposals/storage/pod-safety.md @@ -400,8 +400,3 @@ and unambiguous way to end users. force deleting them. * Decision: YES - captured above. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/storage/volume-hostpath-qualifiers.md b/contributors/design-proposals/storage/volume-hostpath-qualifiers.md index b207253c..8afcc4e0 100644 --- a/contributors/design-proposals/storage/volume-hostpath-qualifiers.md +++ b/contributors/design-proposals/storage/volume-hostpath-qualifiers.md @@ -144,7 +144,3 @@ I don't think this problem is severe enough that we need to push to solve it; rather I think we can simply accept this minor race, and if runtimes eventually allow this we can begin to leverage them. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/storage/volume-provisioning.md b/contributors/design-proposals/storage/volume-provisioning.md index ff68d280..6764f487 100644 --- a/contributors/design-proposals/storage/volume-provisioning.md +++ b/contributors/design-proposals/storage/volume-provisioning.md @@ -494,7 +494,3 @@ parameters: # Cloud Providers Since the `volume.alpha.kubernetes.io/storage-class` is in use a `StorageClass` must be defined to support provisioning. No default is assumed as before. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/storage/volume-selectors.md b/contributors/design-proposals/storage/volume-selectors.md index c1915f99..5af92d0c 100644 --- a/contributors/design-proposals/storage/volume-selectors.md +++ b/contributors/design-proposals/storage/volume-selectors.md @@ -260,9 +260,3 @@ spec: ebs-volume-type: gp-ssd aws-availability-zone: us-east-1 ``` - - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/storage/volume-snapshotting.md b/contributors/design-proposals/storage/volume-snapshotting.md index 0d569618..0c3d42e2 100644 --- a/contributors/design-proposals/storage/volume-snapshotting.md +++ b/contributors/design-proposals/storage/volume-snapshotting.md @@ -516,8 +516,3 @@ spec: * POST https://www.googleapis.com/compute/v1/projects/example-project/zones/us-central1-f/disks/example-disk/createSnapshot - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/design-proposals/storage/volumes.md b/contributors/design-proposals/storage/volumes.md index 874dc2af..a963b279 100644 --- a/contributors/design-proposals/storage/volumes.md +++ b/contributors/design-proposals/storage/volumes.md @@ -476,7 +476,3 @@ spec: The cluster operator would need to manually `chgrp` and `chmod` the `/tmp/example-pod` on the host in order for the volume to be usable from the pod. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/README.md b/contributors/devel/README.md index ce8dd7a3..75319f67 100644 --- a/contributors/devel/README.md +++ b/contributors/devel/README.md @@ -79,7 +79,3 @@ Guide](http://kubernetes.io/docs/admin/). ## Building releases See the [kubernetes/release](https://github.com/kubernetes/release) repository for details on creating releases and related tools and helper scripts. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/adding-an-APIGroup.md b/contributors/devel/adding-an-APIGroup.md index fee831ed..8bbc2e93 100644 --- a/contributors/devel/adding-an-APIGroup.md +++ b/contributors/devel/adding-an-APIGroup.md @@ -2,8 +2,3 @@ Adding an API Group =============== Please refer to [api_changes.md](api_changes.md#making-a-new-api-group). - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/api-conventions.md b/contributors/devel/api-conventions.md index c76d6c61..2ac93bf7 100644 --- a/contributors/devel/api-conventions.md +++ b/contributors/devel/api-conventions.md @@ -1316,6 +1316,3 @@ be less than 256", "must be greater than or equal to 0". Do not use words like "larger than", "bigger than", "more than", "higher than", etc. * When specifying numeric ranges, use inclusive ranges when possible. -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/automation.md b/contributors/devel/automation.md index dda66b4c..1d019f2b 100644 --- a/contributors/devel/automation.md +++ b/contributors/devel/automation.md @@ -90,7 +90,3 @@ The simplest way is to comment `/retest`. Any pushes of new code to the PR will automatically trigger a new test. No human interraction is required. Note that if the PR has a `lgtm` label, it will be removed after the pushes. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/bazel.md b/contributors/devel/bazel.md index fdf28029..21b57ff6 100644 --- a/contributors/devel/bazel.md +++ b/contributors/devel/bazel.md @@ -93,6 +93,3 @@ Updating the `BUILD` file for a package will be required when: ## Contacts For help or discussion, join the [#bazel](https://kubernetes.slack.com/messages/bazel) channel on Kubernetes Slack. -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/cherry-picks.md b/contributors/devel/cherry-picks.md index c503476e..4d9e65f0 100644 --- a/contributors/devel/cherry-picks.md +++ b/contributors/devel/cherry-picks.md @@ -56,7 +56,3 @@ status of PRs labeled as `cherrypick-candidate`. considered implicit for all code within cherry-pick pull requests, ***unless there is a large conflict***. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/client-libraries.md b/contributors/devel/client-libraries.md index 6686fc7c..018c929e 100644 --- a/contributors/devel/client-libraries.md +++ b/contributors/devel/client-libraries.md @@ -1,7 +1,3 @@ ## Kubernetes API client libraries This document has been moved to https://kubernetes.io/docs/reference/client-libraries/. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/coding-conventions.md b/contributors/devel/coding-conventions.md index d15d7eb9..17c890a9 100644 --- a/contributors/devel/coding-conventions.md +++ b/contributors/devel/coding-conventions.md @@ -136,8 +136,3 @@ using the system](https://kubernetes.io/docs/user-guide/config-best-practices/) - Go - [Go landmines](https://gist.github.com/lavalamp/4bd23295a9f32706a48f) - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/collab.md b/contributors/devel/collab.md index 4cc24ac1..43416051 100644 --- a/contributors/devel/collab.md +++ b/contributors/devel/collab.md @@ -45,7 +45,3 @@ Maintainers can assign reviews to other maintainers, when appropriate. The assignee becomes the shepherd for that PR and is responsible for merging the PR once they are satisfied with it or else closing it. The assignee might request reviews from non-maintainers. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/community-expectations.md b/contributors/devel/community-expectations.md index b5271197..45200bc1 100644 --- a/contributors/devel/community-expectations.md +++ b/contributors/devel/community-expectations.md @@ -79,9 +79,3 @@ Many thanks in advance to everyone who contributes their time and effort to making Kubernetes both a successful system as well as a successful community. The strength of our software shines in the strengths of each individual community member. Thanks! - - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/container-runtime-interface.md b/contributors/devel/container-runtime-interface.md index 6a6a3159..96f5f10d 100644 --- a/contributors/devel/container-runtime-interface.md +++ b/contributors/devel/container-runtime-interface.md @@ -134,7 +134,3 @@ default in Kubelet**. - Email: sig-node (kubernetes-sig-node@googlegroups.com) - Slack: https://kubernetes.slack.com/messages/sig-node - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/controllers.md b/contributors/devel/controllers.md index f0df750e..4a82de02 100644 --- a/contributors/devel/controllers.md +++ b/contributors/devel/controllers.md @@ -155,8 +155,3 @@ func (c *Controller) processNextWorkItem() bool { } ``` - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/development.md b/contributors/devel/development.md index 8d217bf6..a3264c05 100644 --- a/contributors/devel/development.md +++ b/contributors/devel/development.md @@ -396,9 +396,6 @@ For mass automated fixups (e.g. automated doc formatting), use one or more commits for the changes to tooling and a final commit to apply the fixup en masse. This makes reviews easier. -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> [OS X GNU tools]: https://www.topbug.net/blog/2013/04/14/install-and-use-gnu-command-line-tools-in-mac-os-x [build/build-image/cross]: https://github.com/kubernetes/kubernetes/blob/master/build/build-image/cross diff --git a/contributors/devel/e2e-node-tests.md b/contributors/devel/e2e-node-tests.md index 734b190d..0dda84a3 100644 --- a/contributors/devel/e2e-node-tests.md +++ b/contributors/devel/e2e-node-tests.md @@ -227,7 +227,3 @@ The PR builder runs tests against the images listed in [jenkins-pull.properties] The post submit tests run against the images listed in [jenkins-ci.properties](https://github.com/kubernetes/kubernetes/tree/master/test/e2e_node/jenkins/jenkins-ci.properties) - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/e2e-tests.md b/contributors/devel/e2e-tests.md index 8c9ca393..0e8dd19f 100644 --- a/contributors/devel/e2e-tests.md +++ b/contributors/devel/e2e-tests.md @@ -804,8 +804,3 @@ You should also know the [testing conventions](coding-conventions.md#testing-con **HAPPY TESTING!** - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/faster_reviews.md b/contributors/devel/faster_reviews.md index 50223f68..37de43cb 100644 --- a/contributors/devel/faster_reviews.md +++ b/contributors/devel/faster_reviews.md @@ -1,7 +1,3 @@ # How to get faster PR reviews Merged with the [pull requests doc](pull-requests.md#best-practices-for-faster-reviews). - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> - []() - <!-- END MUNGE: GENERATED_ANALYTICS -->
\ No newline at end of file diff --git a/contributors/devel/flaky-tests.md b/contributors/devel/flaky-tests.md index 102cf1bc..f06bb078 100644 --- a/contributors/devel/flaky-tests.md +++ b/contributors/devel/flaky-tests.md @@ -188,7 +188,3 @@ exited -1, since that's what happens when you stop the replication controller. Happy flake hunting! - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/flexvolume.md b/contributors/devel/flexvolume.md index d967b1fe..8eab9574 100644 --- a/contributors/devel/flexvolume.md +++ b/contributors/devel/flexvolume.md @@ -131,9 +131,6 @@ Note: Secrets are passed only to "mount/unmount" call-outs. See [nginx.yaml] & [nginx-nfs.yaml] for a quick example on how to use Flexvolume in a pod. -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> [lvm]: https://github.com/kubernetes/kubernetes/blob/master/examples/volumes/flexvolume/lvm [nfs]: https://github.com/kubernetes/kubernetes/blob/master/examples/volumes/flexvolume/nfs diff --git a/contributors/devel/generating-clientset.md b/contributors/devel/generating-clientset.md index 9b8a2006..853bd7a1 100644 --- a/contributors/devel/generating-clientset.md +++ b/contributors/devel/generating-clientset.md @@ -43,8 +43,3 @@ If you are contributing code to k8s.io/kubernetes, try to use the generated clie If you need a stable Go client to build your own project, please refer to the [client-go repository](https://github.com/kubernetes/client-go). We are migrating k8s.io/kubernetes to use client-go as well, see issue [#35159](https://github.com/kubernetes/kubernetes/issues/35159). - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/getting-builds.md b/contributors/devel/getting-builds.md index 86563390..0ae7031b 100644 --- a/contributors/devel/getting-builds.md +++ b/contributors/devel/getting-builds.md @@ -46,7 +46,3 @@ Example installation: $ curl -sSL https://storage.googleapis.com/pub/gsutil.tar.gz | sudo tar -xz -C /usr/local/src $ sudo ln -s /usr/local/src/gsutil/gsutil /usr/bin/gsutil ``` - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/go-code.md b/contributors/devel/go-code.md index dc597bb8..80ffa9d5 100644 --- a/contributors/devel/go-code.md +++ b/contributors/devel/go-code.md @@ -26,7 +26,3 @@ and tips that our developers have found useful. - Consider making a separate Go tree for each project, which can make overlapping dependency management much easier. Remember to set the `$GOPATH` correctly! Consider [scripting](https://gist.github.com/timstclair/17ca792a20e0d83b06dddef7d77b1ea0) this. - Emacs users - setup [go-mode](https://github.com/dominikh/go-mode.el). - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/godep.md b/contributors/devel/godep.md index cc741f66..9b57fdcf 100644 --- a/contributors/devel/godep.md +++ b/contributors/devel/godep.md @@ -176,8 +176,3 @@ paths to coexist in the same git repo. The verifiers, including `hack/verify-godeps.sh` *must* pass for every pull request. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/gubernator.md b/contributors/devel/gubernator.md index 4e9b3a07..9e3855ff 100644 --- a/contributors/devel/gubernator.md +++ b/contributors/devel/gubernator.md @@ -134,7 +134,3 @@ How to contribute (see https://github.com/kubernetes/test-infra/blob/master/gube * Improve UI * Have separate folders of logs in rows instead of in one long column * Improve interface for adding additional features (maybe instead of textbox and checkbox, have chips) - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/instrumentation.md b/contributors/devel/instrumentation.md index d54bb45a..dfa21c69 100644 --- a/contributors/devel/instrumentation.md +++ b/contributors/devel/instrumentation.md @@ -213,8 +213,3 @@ metric could look as follows: kube_pod_restarts and on(namespace, pod) kube_pod_info{uuid=”ABC”} ``` - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/issues.md b/contributors/devel/issues.md index af8ee47b..77df3004 100644 --- a/contributors/devel/issues.md +++ b/contributors/devel/issues.md @@ -204,7 +204,3 @@ issues are work we would merge into the release if it gets done, but we wouldn't block the release on it. A few days before release, we will probably move all `priority/important-soon` and `priority/important-longterm` bugs out of that milestone in bulk. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/kubectl-conventions.md b/contributors/devel/kubectl-conventions.md index c1d54828..d9de594e 100644 --- a/contributors/devel/kubectl-conventions.md +++ b/contributors/devel/kubectl-conventions.md @@ -456,7 +456,3 @@ method which configures the generated namespace that callers of the generator * `--dry-run` should output the resource that would be created, without creating it. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/kubemark-guide.md b/contributors/devel/kubemark-guide.md index cb699a88..2c404424 100644 --- a/contributors/devel/kubemark-guide.md +++ b/contributors/devel/kubemark-guide.md @@ -254,7 +254,3 @@ We currently plan to extend kubemark along the following directions: to logs. - Create a Dashboard that lets easy viewing and comparison of these metrics across tests. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/logging.md b/contributors/devel/logging.md index 1241ee7f..12a719de 100644 --- a/contributors/devel/logging.md +++ b/contributors/devel/logging.md @@ -29,8 +29,3 @@ The following conventions for the glog levels to use. As per the comments, the practical default level is V(2). Developers and QE environments may wish to run at V(3) or V(4). If you wish to change the log level, you can pass in `-v=X` where X is the desired maximum level to log. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/mesos-style.md b/contributors/devel/mesos-style.md index 9d2f38c0..fbded425 100644 --- a/contributors/devel/mesos-style.md +++ b/contributors/devel/mesos-style.md @@ -210,9 +210,3 @@ Mesos is described [here](https://www.usenix.org/legacy/event/nsdi11/tech/full_p Omega is described [here](http://research.google.com/pubs/pub41684.html). Borg is described [here](http://research.google.com/pubs/pub43438.html). - - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/node-performance-testing.md b/contributors/devel/node-performance-testing.md index f156beec..4afa8d25 100644 --- a/contributors/devel/node-performance-testing.md +++ b/contributors/devel/node-performance-testing.md @@ -119,8 +119,3 @@ More details on benchmarking [here](https://golang.org/pkg/testing/). - (yujuhong) Measuring memory usage - Add section on monitoring kubelet metrics (e.g. with prometheus) - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/profiling.md b/contributors/devel/profiling.md index f50537f1..abe0ba78 100644 --- a/contributors/devel/profiling.md +++ b/contributors/devel/profiling.md @@ -40,7 +40,3 @@ to get 30 sec. CPU profile. To enable contention profiling you need to add line `rt.SetBlockProfileRate(1)` in addition to `m.mux.HandleFunc(...)` added before (`rt` stands for `runtime` in `master.go`). This enables 'debug/pprof/block' subpage, which can be used as an input to `go tool pprof`. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/pull-requests.md b/contributors/devel/pull-requests.md index 0f370e56..40ec31c0 100644 --- a/contributors/devel/pull-requests.md +++ b/contributors/devel/pull-requests.md @@ -327,7 +327,3 @@ Another phenomenon of open-source projects (where anyone can comment on any issu No document can take the place of common sense and good taste. Use your best judgment, while you put a bit of thought into how your work can be made easier to review. If you do these things your PRs will get merged with less friction. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/running-locally.md b/contributors/devel/running-locally.md index 1c990caa..077da2af 100644 --- a/contributors/devel/running-locally.md +++ b/contributors/devel/running-locally.md @@ -170,7 +170,3 @@ KUBE_DNS_DOMAIN="cluster.local" ``` To know more on DNS service you can check out the [docs](http://kubernetes.io/docs/admin/dns/). - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/scheduler.md b/contributors/devel/scheduler.md index 47985c98..a7a81a10 100644 --- a/contributors/devel/scheduler.md +++ b/contributors/devel/scheduler.md @@ -88,7 +88,3 @@ However, the choice of policies can be overridden by passing the command-line fl config file. (Note that the config file format is versioned; the API is defined in [plugin/pkg/scheduler/api](http://releases.k8s.io/HEAD/plugin/pkg/scheduler/api/)). Thus to add a new scheduling policy, you should modify [plugin/pkg/scheduler/algorithm/predicates/predicates.go](http://releases.k8s.io/HEAD/plugin/pkg/scheduler/algorithm/predicates/predicates.go) or add to the directory [plugin/pkg/scheduler/algorithm/priorities](http://releases.k8s.io/HEAD/plugin/pkg/scheduler/algorithm/priorities/), and either register the policy in `defaultPredicates()` or `defaultPriorities()`, or use a policy config file. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/scheduler_algorithm.md b/contributors/devel/scheduler_algorithm.md index dc98fe5e..1d3eb418 100644 --- a/contributors/devel/scheduler_algorithm.md +++ b/contributors/devel/scheduler_algorithm.md @@ -38,7 +38,3 @@ Currently, Kubernetes scheduler provides some practical priority functions, incl The details of the above priority functions can be found in [plugin/pkg/scheduler/algorithm/priorities](http://releases.k8s.io/HEAD/plugin/pkg/scheduler/algorithm/priorities/). Kubernetes uses some, but not all, of these priority functions by default. You can see which ones are used by default in [plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](http://releases.k8s.io/HEAD/plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go). Similar as predicates, you can combine the above priority functions and assign weight factors (positive number) to them as you want (check [scheduler.md](scheduler.md) for how to customize). - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/security-release-process.md b/contributors/devel/security-release-process.md index 8f47e1eb..b87c8f1b 100644 --- a/contributors/devel/security-release-process.md +++ b/contributors/devel/security-release-process.md @@ -226,8 +226,3 @@ Yes. CrashOverride will vouch for Acidburn joining the list on behalf of the "Seven" distribution. ``` - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/testing.md b/contributors/devel/testing.md index 17cfb812..d3adf0ed 100644 --- a/contributors/devel/testing.md +++ b/contributors/devel/testing.md @@ -219,7 +219,3 @@ version and the watch cache test is skipped. ## End-to-End tests Please refer to [End-to-End Testing in Kubernetes](e2e-tests.md). - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/update-release-docs.md b/contributors/devel/update-release-docs.md index d603b17f..68c6707c 100644 --- a/contributors/devel/update-release-docs.md +++ b/contributors/devel/update-release-docs.md @@ -106,7 +106,3 @@ docs go away. If the change added or deleted a doc, then update the corresponding `_includes/nav_vX.Y.html` file as well. - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/updating-docs-for-feature-changes.md b/contributors/devel/updating-docs-for-feature-changes.md index 309b809d..1171d397 100644 --- a/contributors/devel/updating-docs-for-feature-changes.md +++ b/contributors/devel/updating-docs-for-feature-changes.md @@ -70,7 +70,3 @@ Anyone making user facing changes to kubernetes. This is especially important f * Include screen shots or pictures in documents for GUIs * *TODO once we have a standard widget set we are happy with* - include diagrams to help describe complex ideas (not required yet) - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/vagrant.md b/contributors/devel/vagrant.md index 9ff414ff..1ecd8157 100644 --- a/contributors/devel/vagrant.md +++ b/contributors/devel/vagrant.md @@ -427,6 +427,3 @@ provider, which uses nfs by default. For example: export KUBERNETES_VAGRANT_USE_NFS=true ``` -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/writing-a-getting-started-guide.md b/contributors/devel/writing-a-getting-started-guide.md index b1d65d60..a879e27d 100644 --- a/contributors/devel/writing-a-getting-started-guide.md +++ b/contributors/devel/writing-a-getting-started-guide.md @@ -94,8 +94,3 @@ These guidelines say *what* to do. See the Rationale section for *why*. if you use another Configuration Management tool -- you just have to do some manual steps during testing and deployment. - - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/contributors/devel/writing-good-e2e-tests.md b/contributors/devel/writing-good-e2e-tests.md index 062af7f6..dd782d50 100644 --- a/contributors/devel/writing-good-e2e-tests.md +++ b/contributors/devel/writing-good-e2e-tests.md @@ -229,7 +229,3 @@ Unreachable nodes are evacuated and then repopulated upon rejoining [Disruptive] Note that opening issues for specific better tooling is welcome, and code implementing that tooling is even more welcome :-). - -<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> -[]() -<!-- END MUNGE: GENERATED_ANALYTICS --> |