Uploaded image for project: 'FlightPath'
  1. FlightPath
  2. FLPATH-2398

[ro] Optimizer app requires network policy to apply recommendations via workflow

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • optimization-plugin
    • False
    • Hide

      None

      Show
      None
    • False

      Description of the problem:

      The optimizer app requires a networkpolicy to apply recommendations via the patch workflow.

      With a networkpolicy, the optimizer pod logs would show:

       

      2025-06-11 16:43:29,308 [Optimizer]  INFO o.Optimizer - started OptimizerTask
      2025-06-11 16:43:29,308 [Optimizer]  INFO o.Optimizer - creating token
      2025-06-11 16:43:29,454 [Optimizer]  INFO o.Optimizer - fetching recommendations
      2025-06-11 16:43:29,454 [Optimizer]  INFO o.Optimizer - fetching recommendations for cluster resourceopt
      2025-06-11 16:43:39,107 [Optimizer]  INFO o.Optimizer - parsing and filtering recommendations
      2025-06-11 16:43:39,111 [Optimizer]  INFO o.Optimizer - parsed 10 recommendations
      2025-06-11 16:45:50,754 [Optimizer] ERROR o.Optimizer - org.apache.http.conn.ConnectTimeoutException: Connect to patch-k8s-resource.sonataflow-infra:80 [patch-k8s-resource.sonataflow-infra/172.30.7.204] failed: Connection timed out
      2025-06-11 16:45:50,755 [Optimizer]  INFO o.Optimizer - started OptimizerTask
      2025-06-11 16:45:50,755 [Optimizer]  INFO o.Optimizer - creating token
      2025-06-11 16:45:50,860 [Optimizer]  INFO o.Optimizer - fetching recommendations
      2025-06-11 16:45:50,861 [Optimizer]  INFO o.Optimizer - fetching recommendations for cluster resourceopt
      2025-06-11 16:45:52,133 [Optimizer]  INFO o.Optimizer - parsing and filtering recommendations
      2025-06-11 16:45:52,137 [Optimizer]  INFO o.Optimizer - parsed 10 recommendations
      2025-06-11 16:48:01,826 [Optimizer] ERROR o.Optimizer - org.apache.http.conn.ConnectTimeoutException: Connect to patch-k8s-resource.sonataflow-infra:80 [patch-k8s-resource.sonataflow-infra/172.30.7.204] failed: Connection timed out
      2025-06-11 16:48:01,826 [Optimizer]  INFO o 

       

       

      Then I applied the network policy with this step:

       

      # label the two workspaces
      oc label namespace optimizer name=optimizer-ns-label
      oc label namespace sonataflow-infra name=sonataflow-infra-ns-label 
      
      # Create network policy referencing the labels to allow intra ns communication
      
      apiVersion: networking.k8s.io/v1
      kind: NetworkPolicy
      metadata:
        generation: 1
        name: allow-optimizer-to-sonataflow-infra
        namespace: sonataflow-infra
      spec:
        ingress:
        - from:
          - namespaceSelector:
              matchLabels:
                name: optimizer-ns-label
        podSelector: {}
        policyTypes:
        - Ingress

       

      After applying network policy the workflow was properly triggered:

      2025-06-11 16:59:09,941 [Optimizer]  INFO o.Optimizer - applied recommendation d09cc5d9-daa9-4752-a9b5-9e0030878235
      2025-06-11 16:59:12,391 [Optimizer]  INFO o.Optimizer - executed workflow instance 3ad9157c-ea79-425d-8df4-9c8cb23d778b
      2025-06-11 16:59:12,392 [Optimizer]  INFO o.Optimizer - applied recommendation 203bd95c-4a49-43dc-a630-36ded53e374f
      2025-06-11 16:59:13,010 [Optimizer]  INFO o.Optimizer - executed workflow instance d338b1fe-30d7-4ca6-be09-eda90cd62c90
      2025-06-11 16:59:13,011 [Optimizer]  INFO o.Optimizer - applied recommendation b449f919-4ba0-4b82-9491-990c834a7594
      2025-06-11 16:59:13,900 [Optimizer]  INFO o.Optimizer - executed workflow instance fcd6da25-6cd4-4dd3-9a0e-45daeabc7d1d
      2025-06-11 16:59:13,900 [Optimizer]  INFO o.Optimizer - applied recommendation ffa31ff1-e7c5-4a24-869e-a8f833bc63e6
      2025-06-11 16:59:13,901 [Optimizer]  INFO o.Optimizer - started OptimizerTask
      2025-06-11 16:59:13,904 [Optimizer]  INFO o.Optimizer - creating token
      2025-06-11 16:59:14,021 [Optimizer]  INFO o.Optimizer - fetching recommendations
      2025-06-11 16:59:14,022 [Optimizer]  INFO o.Optimizer - fetching recommendations for cluster resourceopt newer than 2025-06-11T16:51:59.438324Z
      2025-06-11 16:59:15,004 [Optimizer]  INFO o.Optimizer - parsing and filtering recommendations
      2025-06-11 16:59:15,005 [Optimizer]  INFO o.Optimizer - parsed 0 recommendations
      2025-06-11 16:59:15,005 [Optimizer]  INFO o.Optimizer - started OptimizerTask
      2025-06-11 16:59:15,006 [Optimizer]  INFO o.Optimizer - creating to 

       

      This was with RHDH 1.6 and M6 Orchestrator.

       

              ydayagi yaron dayagi
              chadcrum Chad Crum
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: