[Tradeoff] Using ISTIO ?

gbutheau-ads commented 3 years ago

User story description: "As a Product Owner I would like to understand the benefits of adding a service mesh like Istio in COPRS, and to check the compatibility with the current ecosystem especially Kafka, so that I can decide to deploy it or not in COPRS."

Acceptance criteria:

[x] tradeoff synthesis is detailed in a dedicated workshop
[x] tradeoff criteria include at leaste the technical pros/cons, cost, performance, stability, license, security, monitoring
[x] tradeoff criteria weights are discussed with Airbus before releasing tradeoff conclusions

Definition of Done The User Story is considered completed when...

Acceptance criteria are full filled
Other potential conditions

cbouisson-csgroup commented 3 years ago

See also CNI

gbutheau-ads commented 2 years ago

With @tllabres-ads we reviewed the tradeoff conclusions that pointed out Apache Apisix as Ingress Controller and Linkerd as a service mesh. We'll need a formal review all together to discuss these choices however implementation can start based on it.

cbouisson-csgroup commented 2 years ago

Trade-off : https://github.com/COPRS/infrastructure/wiki/Networking-trade-off Workshop : Monday 3 January (ADS validate trade-off)

COPRS / rs-issues

[Tradeoff] Using ISTIO ? #102