etcd: adjust govulncheck memory limits

[ivanvc]

The job gets stuck when running the govulncheck command at the repository's root. Following Grafana, it seems to be reaching the memory limit.

Based on historical usage, I initially configured it to use at most 1Gi. However, usage seems to increase if there's a vulnerability in the code (right now, we should get a job failure because the main branch is still using Go 1.22.6).

Reference:

• https://monitoring-eks.prow.k8s.io/d/96Q8oOOZk/builds?var-org=etcd-io&var-repo=etcd&var-job=pull-etcd-govulncheck&orgId=1&refresh=30s&from=now-24h&to=now&var-build=All
• https://prow.k8s.io/job-history/gs/kubernetes-jenkins/pr-logs/directory/pull-etcd-govulncheck

[ivanvc]

/cc @jmhbnz

[jmhbnz]

This was on my list, I had noticed it having trouble. Thanks Ivan, let's see how it behaves with a bit more memory 🙏🏻

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ivanvc, jmhbnz

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

The pull request process is described here

Needs approval from an approver in each of these files:

• config/jobs/etcd/OWNERS [jmhbnz]

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

[k8s-ci-robot]

@ivanvc: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key etcd-presubmits.yaml using file config/jobs/etcd/etcd-presubmits.yaml

In response to this:

The job gets stuck when running the govulncheck command at the repository's root. Following Grafana, it seems to be reaching the memory limit.

Based on historical usage, I initially configured it to use at most 1Gi. However, usage seems to increase if there's a vulnerability in the code (right now, we should get a job failure because the main branch is still using Go 1.22.6).

Reference:

• https://monitoring-eks.prow.k8s.io/d/96Q8oOOZk/builds?var-org=etcd-io&var-repo=etcd&var-job=pull-etcd-govulncheck&orgId=1&refresh=30s&from=now-24h&to=now&var-build=All
• https://prow.k8s.io/job-history/gs/kubernetes-jenkins/pr-logs/directory/pull-etcd-govulncheck

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.

[ivanvc]

@jmhbnz, it now failed as expected. Refer to: etcd-io/etcd#18573 (comment)

Edit: scratch that, it seems to be another issue(?)

[ivanvc]

That was a fluke. It worked as expected the second time: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/etcd-io_etcd/18573/pull-etcd-govulncheck/1833616886273675264