[CI] Bump memory for k8s discovery e2e tests

[ruizhang0101]

Router resources 2G→4G; engine requestMemory 30Gi→40Gi across e2e values files.

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request increases the requested memory for serving engines from 30Gi to 40Gi and router memory limits/requests from 2G to 4G across multiple configuration files. The reviewer suggests using binary SI suffixes (e.g., '4Gi' instead of '4G') for the router resources to prevent potential Out-Of-Memory (OOM) issues in Kubernetes and to maintain consistency with other memory definitions in the files.

[gemini-code-assist]

In Kubernetes, it is recommended to use binary SI suffixes (such as Gi for Gibibytes) instead of decimal suffixes (such as G for Gigabytes) for memory requests and limits. Using decimal units can lead to a ~7.3% reduction in allocated memory compared to binary units, which might cause unexpected Out-Of-Memory (OOM) issues. Additionally, using Gi here maintains consistency with the requestMemory: "40Gi" defined in the same file.

      memory: "4Gi"
    limits:
      cpu: "1"
      memory: "4Gi"

[gemini-code-assist]

In Kubernetes, it is recommended to use binary SI suffixes (such as Gi for Gibibytes) instead of decimal suffixes (such as G for Gigabytes) for memory requests and limits. Using decimal units can lead to a ~7.3% reduction in allocated memory compared to binary units, which might cause unexpected Out-Of-Memory (OOM) issues. Additionally, using Gi here maintains consistency with the requestMemory: "40Gi" defined in the same file.

      memory: "4Gi"
    limits:
      cpu: "1"
      memory: "4Gi"

[gemini-code-assist]

In Kubernetes, it is recommended to use binary SI suffixes (such as Gi for Gibibytes) instead of decimal suffixes (such as G for Gigabytes) for memory requests and limits. Using decimal units can lead to a ~7.3% reduction in allocated memory compared to binary units, which might cause unexpected Out-Of-Memory (OOM) issues. Additionally, using Gi here maintains consistency with the requestMemory: "40Gi" defined in the same file.

      memory: "4Gi"
    limits:
      cpu: "1"
      memory: "4Gi"

[gemini-code-assist]

In Kubernetes, it is recommended to use binary SI suffixes (such as Gi for Gibibytes) instead of decimal suffixes (such as G for Gigabytes) for memory requests and limits. Using decimal units can lead to a ~7.3% reduction in allocated memory compared to binary units, which might cause unexpected Out-Of-Memory (OOM) issues. Additionally, using Gi here maintains consistency with the requestMemory: "40Gi" defined in the same file.

      memory: "4Gi"
    limits:
      cpu: "1"
      memory: "4Gi"