update glibc package to 2.35-r0 to resolve segfaults

[sunaydagli]

The alpine base image was updated to 3.22 in #961. However, the glibc seems to not be updated, causing segfaults. As a result, the glibc should be updated to the most up-to-date glibc from the existing package manager used, which is glibc version 2.35. On first analysis, this fixes the segfaults. When doing analysis, this was the output of ldd, which prompted this change.

kubectl exec -it $(kubectl get pod -l app=esp-envoy-failure -o jsonpath="{.items[0].metadata.name}") -c esp -- ldd /bin/envoy
/lib64/ld-linux-x86-64.so.2 (0x7e42fa9e0000)
libm.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7e42fa9e0000)
librt.so.1 => /lib64/ld-linux-x86-64.so.2 (0x7e42fa9e0000)
libdl.so.2 => /lib64/ld-linux-x86-64.so.2 (0x7e42fa9e0000)
libpthread.so.0 => /lib64/ld-linux-x86-64.so.2 (0x7e42fa9e0000)
libc.so.6 => /lib64/ld-linux-x86-64.so.2 (0x7e42fa9e0000)
ld-linux-x86-64.so.2 => /lib/ld-linux-x86-64.so.2 (0x7e42f7ec5000)
Error relocating /lib/ld-linux-x86-64.so.2: unsupported relocation type 37
Error relocating /bin/envoy: __memcpy_chk: symbol not found
Error relocating /bin/envoy: __vsnprintf_chk: symbol not found
Error relocating /bin/envoy: __memset_chk: symbol not found
Error relocating /bin/envoy: __longjmp_chk: symbol not found
Error relocating /bin/envoy: __strncpy_chk: symbol not found
Error relocating /bin/envoy: __strcpy_chk: symbol not found
Error relocating /bin/envoy: __fdelt_chk: symbol not found
Error relocating /bin/envoy: fcntl64: symbol not found
Error relocating /bin/envoy: __memmove_chk: symbol not found
Error relocating /bin/envoy: __cxa_thread_atexit_impl: symbol not found
Error relocating /bin/envoy: __strftime_l: symbol not found
command terminated with exit code 127

[sunaydagli]

/test ESPv2-presubmit

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: paulhong01, sunaydagli

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [paulhong01]

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

[google-oss-prow]

New changes are detected. LGTM label has been removed.

[google-oss-prow]

@sunaydagli: 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
ESPv2-cloud-run-e2e-cloud-function-http-bookstore	234ac59	link	true	/test ESPv2-cloud-run-e2e-cloud-function-http-bookstore
ESPv2-cloud-run-e2e-app-engine-http-bookstore	234ac59	link	true	/test ESPv2-cloud-run-e2e-app-engine-http-bookstore
ESPv2-presubmit-tsan	234ac59	link	true	/test ESPv2-presubmit-tsan
ESPv2-anthos-cloud-run-e2e-anthos-cloud-run-http-bookstore	234ac59	link	true	/test ESPv2-anthos-cloud-run-e2e-anthos-cloud-run-http-bookstore

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/test-infra repository. I understand the commands that are listed here.