From 986b930f20a16ac037278bd13a661171fcb3baa6 Mon Sep 17 00:00:00 2001
From: Hongchao Deng <hongchaodeng1@gmail.com>
Date: Fri, 12 Jun 2020 21:24:24 -0700
Subject: [PATCH] add ingress example

---
 design/resource-dependency.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/design/resource-dependency.md b/design/resource-dependency.md
index 0508a822..fb7ee400 100644
--- a/design/resource-dependency.md
+++ b/design/resource-dependency.md
@@ -97,6 +97,12 @@ In OAM, we model EtcdCluster as Component and EtcdBackup as Trait.
 However, the EtcdBackup depends on the connection secret specified in `status.connSecret` field of EtcdCluster.
 In other words, the EtcdBackup trait depends on EtcdCluster component.
 
+### 6. Ingress after component
+
+We have an ingress implementation that requires the microservice component must be setup before applying ingress entry.
+In this case, the ingress trait should only be created after the component is ready.
+
+
 ## Proposal
 
 The overall idea is to have each resource specify data inputs coming from data outputs (i.e. other resources' fields).
@@ -321,3 +327,5 @@ In this section we are providing more solution examples for dependency use cases
             - name: my-secret-binding
               fieldPath: status.ready
     ```
+
+3.