Skip to content
This repository has been archived by the owner on Jun 8, 2022. It is now read-only.

Commit

Permalink
add ingress example
Browse files Browse the repository at this point in the history
Signed-off-by: Hongchao Deng <[email protected]>
  • Loading branch information
hongchaodeng committed Jun 13, 2020
1 parent 20e743c commit 09cf22d
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions design/resource-dependency.md
Original file line number Diff line number Diff line change
Expand Up @@ -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).
Expand Down Expand Up @@ -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.

0 comments on commit 09cf22d

Please sign in to comment.