Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-3599

Federation egress-gateway gets wrong update of network gateway endpoints

XMLWordPrintable

    • False
    • None
    • False
    • Release Notes
    • Release Note Not Required
    • Proposed
    • Hide

      Here the former associated ticket

      See the blueprints attached to the case

      Show
      Here the former associated ticket See the blueprints attached to the case

      Linked to this ticket

      It appears that instead of just the remote IPs, in our federation-egress gateway we're routing requests to extra IPs which point to its own federation-ingress.

      Here an example of the egress-gateway logs

      2023-03-23T18:35:57.901620Z	debug	federation	adding import for service {Name:nginx Namespace:bookinfo Hostname:nginx.bookinfo.svc.green-exports.local} as {Name:nginx Namespace:green-workload Hostname:nginx.green-workload.svc.red-imports.local}	component=federation-registry
2023-03-23T18:35:57.901639Z	debug	federation	adding endpoint for imported service: addr=35.180.219.47, port=15443, host=nginx.bookinfo.svc.green-exports.local	component=federation-registry
2023-03-23T18:35:57.901650Z	debug	federation	adding endpoint for imported service: addr=13.37.33.162, port=15443, host=nginx.bookinfo.svc.green-exports.local	component=federation-registry
2023-03-23T18:35:57.901659Z	debug	federation	adding endpoint for imported service: addr=15.236.147.201, port=15443, host=nginx.bookinfo.svc.green-exports.local	component=federation-registry
2023-03-23T18:35:57.901665Z	debug	federation	adding endpoint for imported service: addr=18.133.20.159, port=15443, host=nginx.bookinfo.svc.green-exports.local	component=federation-registry
2023-03-23T18:35:57.901670Z	debug	federation	adding endpoint for imported service: addr=35.177.165.55, port=15443, host=nginx.bookinfo.svc.green-exports.local	component=federation-registry
2023-03-23T18:35:57.901675Z	debug	federation	adding endpoint for imported service: addr=35.179.84.234, port=15443, host=nginx.bookinfo.svc.green-exports.local	component=federation-registry
2023-03-23T18:35:57.901683Z	debug	federation	adding endpoint for imported service: addr=10.129.2.31, port=15443, host=nginx.green-workload.svc.red-imports.local	component=federation-registry

      In v2.1, we pulled the NetworkGateways from istio's env and filtered them using s.network.
      In the next versions, we don't have this filter anymore (cf. v2.2 or v2.3) which causes the extra endpoints entries.

        1.
        		 Port egress-gateway wrong network gateway endpoints fix in maistra-2.3 Sub-task Closed Blocker Brian Mangoenpawiro
        2.
        		 Port egress-gateway wrong network gateway endpoints fix in maistra-2.2 Sub-task Closed Blocker Brian Mangoenpawiro

            _bmangoen Brian Mangoenpawiro
            _bmangoen Brian Mangoenpawiro
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: