Romuald Atchadé - OOO until Jan 11th, 2026 authored Apr 28, 2025 and Love Bhardwaj committed Aug 19, 2025

Promote FF_RETRIEVE_POD_WARNING_EVENTS to a config print_pod_warning_events

Closes #38479 and gitlab-org/charts/gitlab-runner#499

See merge request !5377



Merged-by: Romuald Atchadé <ratchade@gitlab.com>
Approved-by: Roshni Sarangadharan <rsarangadharan@gitlab.com>
Approved-by: Georgi N. Georgiev <ggeorgiev@gitlab.com>
Reviewed-by: Georgi N. Georgiev <ggeorgiev@gitlab.com>
Reviewed-by: Romuald Atchadé <ratchade@gitlab.com>
Reviewed-by: Roshni Sarangadharan <rsarangadharan@gitlab.com>

This reverts commit b6104181.

Romuald Atchadé - OOO until Jan 11th, 2026 authored Apr 28, 2025 and Love Bhardwaj committed Aug 19, 2025

Promote FF_RETRIEVE_POD_WARNING_EVENTS to a config print_pod_warning_events

Closes #38479 and gitlab-org/charts/gitlab-runner#499

See merge request gitlab-org/gitlab-runner!5377



Merged-by: Romuald Atchadé <ratchade@gitlab.com>
Approved-by: Roshni Sarangadharan <rsarangadharan@gitlab.com>
Approved-by: Georgi N. Georgiev <ggeorgiev@gitlab.com>
Reviewed-by: Georgi N. Georgiev <ggeorgiev@gitlab.com>
Reviewed-by: Romuald Atchadé <ratchade@gitlab.com>
Reviewed-by: Roshni Sarangadharan <rsarangadharan@gitlab.com>

Axel von Bertoldi authored Jun 13, 2025 and Love Bhardwaj committed Aug 20, 2025

Mysteriously, this test recently started failing with an "operation not
permitted" error. I say Mysteriously because:
- neither the test nor production code have changed in a while. The test
  fails on older stable branches (at least as far back as 17-11-stable).
- the test fails in older CI images (at least 3 versions back), so
  changes in the image is not the cause either.

This short script is enough to reproduce the error:

    package main

    import "syscall"

    func main() {
            newRLimit := syscall.Rlimit{
                    Max: uint64(106),
                    Cur: uint64(106),
            }

            err := syscall.Setrlimit(syscall.RLIMIT_NOFILE, &newRLimit)
            if err != nil {
                    panic(err)
            }

            newRLimit.Max = uint64(107)
            newRLimit.Cur = uint64(107)

            err = syscall.Setrlimit(syscall.RLIMIT_NOFILE, &newRLimit)
            if err != nil {
                    panic(err)
            }

    }

At least in docker, it looks like increasing RLIMIT_NOFILE is not
allowed.

The "solution" is to not call the cleanup function that attempts to
restore the RLIMIT_NOFILE.

Backport PrintPodWarningEvents config

See merge request gitlab-org/gitlab-runner!5788