Ensure GOMAXPROCS & GOMEMLIMIT align with K8s limits

[lburgazzoli]

Description

Set GOMAXPROCS and GOMEMLIMIT based on the CPU/memory limits
defined in the deployment manifests. This ensures optimal
resource utilization and prevents performance degradation
caused by CPU throttling or OOM issues in containerized Go apps.

References:

• https://www.ardanlabs.com/blog/2024/02/kubernetes-cpu-limits-go.html
• https://www.ardanlabs.com/blog/2024/02/kubernetes-memory-limits-go.html

Note

As of today, we do configure the operator Deployment with some
resources requests and limits, however, we do not configure the go
runtime according. At this stage this is just an hypothesis, but since
that on a large cluster, the GOMAXPROCS would be automatically
set to the number of cores, resulting in a sub-optimal setup as the
go runtime would assume it can use all the cores, However, we set
500m as resource limit for CPU so we won't be able to use more than
a single thread.

How Has This Been Tested?

Screenshot or short clip

Merge criteria

• You have read the contributors guide.
• Commit messages are meaningful - have a clear and concise summary and detailed explanation of what was changed and why.
• Pull Request contains a description of the solution, a link to the JIRA issue, and to any dependent or related Pull Request.
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign asanzgom for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

❌ Patch coverage is 0% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 23.96%. Comparing base (06a1b25) to head (c49a4d0).
⚠️ Report is 357 commits behind head on main.

Files with missing lines	Patch %	Lines
pkg/cluster/cluster_config.go	0.00%	5 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1755      +/-   ##
==========================================
- Coverage   23.97%   23.96%   -0.02%     
==========================================
  Files         172      172              
  Lines       11699    11704       +5     
==========================================
  Hits         2805     2805              
- Misses       8614     8619       +5     
  Partials      280      280              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[openshift-ci]

@lburgazzoli: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/ci-bundle-opendatahub-operator-rhoai-bundle	c49a4d0	link	true	/test ci-bundle-opendatahub-operator-rhoai-bundle
ci/prow/opendatahub-operator-e2e	c49a4d0	link	true	/test opendatahub-operator-e2e

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.