fix Sets the requests equals to limits.

[lvarin]

Summary by Sourcery

Set CPU limits in Kubernetes container resources to match CPU requests and update tests to verify this behavior.

Bug Fixes:

• Ensure that CPU limits are set in the Kubernetes container resources to match the CPU requests.

Tests:

• Add test assertions to verify that CPU limits are correctly set in the Kubernetes container resources.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request adds functionality to set CPU limits in the Kubernetes container resources. Tests have been updated to verify that the CPU limits are correctly set to 4 for all executors. Additionally, a JSON comparison test has been commented out.

File-Level Changes

Files	Changes
src/test/java/uk/ac/ebi/tsc/tesk/k8s/convert/TesKubernetesConverterTest.java src/test/resources/fromTesToK8s/taskmaster_param.json	Updated tests to include checks for CPU limits in the container resources.
src/main/java/uk/ac/ebi/tsc/tesk/k8s/convert/TesKubernetesConverter.java	Implemented setting of CPU limits in the Kubernetes container resources.

---

Tips

• Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
• Continue your discussion with Sourcery by replying directly to review comments.
• You can change your review settings at any time by accessing your dashboard:
  • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
  • Change the review language;
• You can always contact us if you have any questions or feedback.

[sourcery-ai]

Hey @lvarin - I've reviewed your changes - here's some feedback:

Overall Comments:

• Could you provide more context on the motivation behind this change? The PR title suggests uncertainty about its value.
• Consider keeping or updating the commented-out test case to maintain test coverage.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟡 Testing: 1 issue found
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.}

[sourcery-ai]

question (testing): Consider re-enabling JSON comparison test

The commented-out JSON comparison test could provide a comprehensive check to ensure the entire JSON structure is as expected. Consider re-enabling it or providing a reason for its removal.

[lvarin]

Done

[sourcery-ai]

Thank you for re-enabling the JSON comparison test, @lvarin. This will help ensure that the entire JSON structure is validated comprehensively. If you encounter any issues with this test or need further assistance, feel free to reach out. Great job!