Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

This page discusses the options for the _ingress.tpl to generate different resources:

Problem:

→ In the current implementation the template is able to generate only for nginx and Istio GW/VS
→ for each ingress definition for each VS a separate GW is created, which is generally not correct.
    Instead a single GW should be provided, which should be used by all VCs

→ if a "commonGW" is used, the GW needs to be created during the Ingress setup phase (described in OOM documentation)


Proposal:

  • Create new "global.Ingress" option to select the provider resource (NginxIngress, Istio, GW-API)
  • For "Ingress" provide setting for the class (e.g. nginx, traefik)
  • Provide a "shared Gateway" name as option, which is refered by the VC/HTTPRoute,...


Istio-Ingress Provider

Options: no commonGW (not optimal or wrong) → currently implemented

draw.io Diagram
bordertrue
diagramNameIstio-GW_VS
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth1353
revision412


Special case: TCP Routes (e.g. Kafka)

draw.io Diagram
bordertrue
diagramNameIstio-TCP-GW_VS
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth14531613
revision25

Options: commonGW → needs to be checked, if it is working

draw.io Diagram
bordertrue
diagramNameIstio-VS
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth13331453
revision48


Gateway-API Provider

Options: commonGW

draw.io Diagram
bordertrue
diagramNameGW-API-HR
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth1353
revision9


Special case: TCP Routes (e.g. Kafka)

draw.io Diagram
bordertrue
diagramNameGW-API-TCP
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth1533
revision5


Special case: UDP Routes (e.g. DCAE SNMP Trap collector)

draw.io Diagram
bordertrue
diagramNameGW-API-TCP
simpleViewerfalse
linksauto
tbstyletop
lboxtrue
diagramWidth1533
revision5