updates to service injection policy proposal

Signed-off-by: Jess Frazelle <acidburn@google.com>
kubernetes · Jan 5, 2017 · a9b411d · a9b411d
1 parent 4c8f98a
commit a9b411d
Showing 1 changed file with 16 additions and 10 deletions.
diff --git a/...ign-proposals/service_injection_policy.md → ...ign-proposals/service-injection-policy.md b/...ign-proposals/service_injection_policy.md → ...ign-proposals/service-injection-policy.md
@@ -25,17 +25,13 @@ information into every pod spec where it is needed.
 1.  As a user, I want to be able to describe a way that pods should be injected
     with the information to consume a particular service in a loosely-coupled
     way, so that I can concisely model the information about how the service
-    should be consumed without altering every consuming pod spec
-
-<!--
-2.  As a user, I want a controller that manage pods to create a new generation
-    of pods when the pods that controller's pods should be injected with
-    information about a new set of services
--->
+    should be consumed without altering every consuming pod spec.
 
 ### Loose coupling between services and their consumers
 
-
+Using a Service Injection Policy allows pod authors to not have to explicitly
+set information for every pod. The information will be injected based off the
+policy's LabelSelector.
 
 ## Proposed Changes
 
@@ -61,5 +57,15 @@ type ServiceInjectionPolicySpec struct {
 ## Examples
 
 ```yaml
-
-```
+kind: ServiceInjectionPolicy
+apiVersion: extensions/v1beta1
+metadata:
+  name: allow-database
+  namespace: myns
+spec:
+  labelSelector:
+    matchLabels:
+      role: frontend
+  env:
+    - DB_PORT: 6379
+```