diff options
| -rw-r--r-- | README.md | 2 | ||||
| -rw-r--r-- | access.md | 2 | ||||
| -rw-r--r-- | admission_control.md | 2 | ||||
| -rw-r--r-- | admission_control_limit_range.md | 2 | ||||
| -rw-r--r-- | admission_control_resource_quota.md | 2 | ||||
| -rw-r--r-- | architecture.md | 2 | ||||
| -rw-r--r-- | clustering.md | 2 | ||||
| -rw-r--r-- | clustering/README.md | 3 | ||||
| -rw-r--r-- | command_execution_port_forwarding.md | 3 | ||||
| -rw-r--r-- | event_compression.md | 2 | ||||
| -rw-r--r-- | expansion.md | 3 | ||||
| -rw-r--r-- | identifiers.md | 2 | ||||
| -rw-r--r-- | namespaces.md | 3 | ||||
| -rw-r--r-- | networking.md | 2 | ||||
| -rw-r--r-- | persistent-storage.md | 2 | ||||
| -rw-r--r-- | principles.md | 2 | ||||
| -rw-r--r-- | resources.md | 2 | ||||
| -rw-r--r-- | secrets.md | 2 | ||||
| -rw-r--r-- | security.md | 2 | ||||
| -rw-r--r-- | security_context.md | 3 | ||||
| -rw-r--r-- | service_accounts.md | 3 | ||||
| -rw-r--r-- | simple-rolling-update.md | 2 |
22 files changed, 48 insertions, 2 deletions
@@ -31,4 +31,6 @@ Finally, Kubernetes aspires to be an extensible, pluggable, building-block OSS p For more about the Kubernetes architecture, see [architecture](architecture.md). +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> @@ -262,4 +262,6 @@ 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/admission_control.md b/admission_control.md index 4094156b..5870a601 100644 --- a/admission_control.md +++ b/admission_control.md @@ -93,4 +93,6 @@ will ensure the following: If at any step, there is an error, the request is canceled. +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/admission_control_limit_range.md b/admission_control_limit_range.md index c1914478..e5363cea 100644 --- a/admission_control_limit_range.md +++ b/admission_control_limit_range.md @@ -146,4 +146,6 @@ It is expected we will want to define limits for particular pods or containers b To make a **LimitRangeItem** more restrictive, we will intend to add these additional restrictions at a future point in time. +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/admission_control_resource_quota.md b/admission_control_resource_quota.md index cd9282df..754e5a00 100644 --- a/admission_control_resource_quota.md +++ b/admission_control_resource_quota.md @@ -167,4 +167,6 @@ services 3 5 ``` +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/architecture.md b/architecture.md index 6c82896e..71d606a1 100644 --- a/architecture.md +++ b/architecture.md @@ -58,4 +58,6 @@ All other cluster-level functions are currently performed by the Controller Mana The [`replicationcontroller`](../replication-controller.md) is a mechanism that is layered on top of the simple [`pod`](../pods.md) API. We eventually plan to port it to a generic plug-in mechanism, once one is implemented. +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/clustering.md b/clustering.md index 95ff3ccc..3e9972ce 100644 --- a/clustering.md +++ b/clustering.md @@ -74,4 +74,6 @@ This flow has the admin manually approving the kubelet signing requests. This i  +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/clustering/README.md b/clustering/README.md index dfd55e96..07dcc7b3 100644 --- a/clustering/README.md +++ b/clustering/README.md @@ -39,4 +39,7 @@ If you are using boot2docker and get warnings about clock skew (or if things are 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/command_execution_port_forwarding.md b/command_execution_port_forwarding.md index 056814e7..7d110c3f 100644 --- a/command_execution_port_forwarding.md +++ b/command_execution_port_forwarding.md @@ -157,4 +157,7 @@ access. Additional work is required to ensure that multiple command execution or port 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/event_compression.md b/event_compression.md index 4178393c..40dc9e52 100644 --- a/event_compression.md +++ b/event_compression.md @@ -92,4 +92,6 @@ This demonstrates what would have been 20 separate entries (indicating schedulin * PR [#4444](https://github.com/GoogleCloudPlatform/kubernetes/pull/4444): Switch events history to use LRU cache instead of map +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/expansion.md b/expansion.md index 01a774cb..4f4511ce 100644 --- a/expansion.md +++ b/expansion.md @@ -399,4 +399,7 @@ spec: restartPolicy: Never ``` + +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/identifiers.md b/identifiers.md index e192b1ed..49068cc8 100644 --- a/identifiers.md +++ b/identifiers.md @@ -106,4 +106,6 @@ objectives. 1. This may correspond to Docker's container ID. +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/namespaces.md b/namespaces.md index 547d040b..cd8b5280 100644 --- a/namespaces.md +++ b/namespaces.md @@ -348,4 +348,7 @@ to remove that Namespace from the 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/networking.md b/networking.md index 5a4a5835..35248a71 100644 --- a/networking.md +++ b/networking.md @@ -190,4 +190,6 @@ External IP assignment would also simplify DNS support (see below). IPv6 would be a nice option, also, but we can't depend on it yet. Docker support is in progress: [Docker issue #2974](https://github.com/dotcloud/docker/issues/2974), [Docker issue #6923](https://github.com/dotcloud/docker/issues/6923), [Docker issue #6975](https://github.com/dotcloud/docker/issues/6975). Additionally, direct ipv6 assignment to instances doesn't appear to be supported by major cloud providers (e.g., AWS EC2, 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/persistent-storage.md b/persistent-storage.md index 9cc92b42..585cd281 100644 --- a/persistent-storage.md +++ b/persistent-storage.md @@ -228,4 +228,6 @@ The ```PersistentVolumeClaimBinder``` will reconcile this by removing the claim 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/principles.md b/principles.md index e1bd97da..5071e89d 100644 --- a/principles.md +++ b/principles.md @@ -69,4 +69,6 @@ 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/resources.md b/resources.md index 9539bed2..229e9b76 100644 --- a/resources.md +++ b/resources.md @@ -227,4 +227,6 @@ This is the amount of time a container spends accessing disk, including actuator * Compressible? yes +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> @@ -590,4 +590,6 @@ source. Both containers will have the following files present on their filesyst /etc/secret-volume/password +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/security.md b/security.md index 90dc3237..bbb735eb 100644 --- a/security.md +++ b/security.md @@ -131,4 +131,6 @@ The controller manager for Replication Controllers and other future controllers The Kubernetes pod scheduler is responsible for reading data from the pod to fit it onto a node in the cluster. At a minimum, it needs access to view the ID of a pod (to craft the binding), its current state, any resource information necessary to identify placement, and other data relevant to concerns like anti-affinity, zone or region preference, or custom logic. It does not need the ability to modify pods or see other resources, only to create bindings. It should not need the ability to delete bindings unless the scheduler takes control of relocating components on failed hosts (which could be implemented by 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/security_context.md b/security_context.md index cbf525a8..ad83a6bd 100644 --- a/security_context.md +++ b/security_context.md @@ -170,5 +170,6 @@ will be denied by default. In the future the admission plugin will base this de configurable policies that reside within the [service account](https://github.com/GoogleCloudPlatform/kubernetes/pull/2297). - +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/service_accounts.md b/service_accounts.md index 896bd68e..61237853 100644 --- a/service_accounts.md +++ b/service_accounts.md @@ -177,5 +177,6 @@ Finally, it may provide an interface to automate creation of new serviceAccounts to GET serviceAccounts to see what has been created. - +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> diff --git a/simple-rolling-update.md b/simple-rolling-update.md index 45005353..0f2fe9e6 100644 --- a/simple-rolling-update.md +++ b/simple-rolling-update.md @@ -105,4 +105,6 @@ then ```foo-next``` is synthesized using the pattern ```<controller-name>-<hash- * Goto Rollout with ```foo``` and ```foo-next``` trading places. +<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() +<!-- END MUNGE: GENERATED_ANALYTICS --> |