You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 4, 2020. It is now read-only.
Describe the bug
Ingress trait and ComponentSchematic documentation are not clear on some things about using Ingress, such as:
how to front multiple ComponentSchematics with a single ingress
how to most compactly define multiple Ingress paths that apply to the same ApplicationConfig
how to indicate that an Ingress path should apply to any hostname
Specifically, I'm trying to recreate the Istio BookInfo demo as a Rudr app definition. I can easily create a Kubernetes Ingress to do what's desired, as below:
but the BookInfo app depends on various Services existing as well, some of which (reviews) have selectors that select pods from multiple Deployments. It's not clear whether I can just define them as separate ComponentSchematics and then reference them all from a single ApplicationConfig somehow, or if I need to do something different, or if this is not actually (currently) possible to define in OAM and/or Rudr.
The text was updated successfully, but these errors were encountered:
@omkensey Hi Joe, the OAM spec has been released to v1alpha2 which is slightly different, for example, ComponentSchematic is gone :-) Please check this slides for a diff.
In general, traffic mgmt related apps like BookInfo should be able to be modeled easily with OAM.
The mapping would be:
Component - Deployment
Trait - Service/Ingress per Deployment
Scope - Service/Ingress/APIGateway across Deployments
ApplicationConfiguration - a YAML file to grouping Component/Trait/Scope together
We will start working on implementing Scope in Crossplane ASAP, and at the meantime, it would be grateful if you can try to category BookInfo API resources into the OAM objects above.
Note that in v1alpha2, OAM defines K8s resource directly in YAML files, please heck this example.
Describe the bug
Ingress trait and ComponentSchematic documentation are not clear on some things about using Ingress, such as:
Specifically, I'm trying to recreate the Istio BookInfo demo as a Rudr app definition. I can easily create a Kubernetes Ingress to do what's desired, as below:
but the BookInfo app depends on various Services existing as well, some of which (reviews) have selectors that select pods from multiple Deployments. It's not clear whether I can just define them as separate ComponentSchematics and then reference them all from a single ApplicationConfig somehow, or if I need to do something different, or if this is not actually (currently) possible to define in OAM and/or Rudr.
The text was updated successfully, but these errors were encountered: