mention lattice w.r.t egress_rules

alfred-huangjian · Jan 28, 2015 · c7bc4f8 · c7bc4f8
1 parent 534fccf
commit c7bc4f8
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/doc/lrps.md b/doc/lrps.md
@@ -177,9 +177,9 @@ Diego can open and expose arbitrary `ports` inside the container.  Currently, if
 
 There are plans to generalize this interface and make it possible to build custom service discovery solutions on top of Diego.  The API is likely to change in backward-incompatible ways as we work these requirements out.
 
-By default network access for any container is limited but some LRPs might need specific network access and that can be setup using `egress_rules` field.
+By default network access for any container is limited but some LRPs might need specific network access and that can be setup using `egress_rules` field.  Rules are evaluated in reverse order of their position, i.e., the last one takes precedence.
 
-Rules are evaluated in reverse order of their position, i.e., the last one takes precedence.
+> Lattice users: Lattice is intended to be a single-tenant cluster environment.  In Lattice there are no network access constraints on the containers so there is no need ot specify `egress_rules`.
 
 #### `ports` [optional]