Remove TLS EOF errors from logs

[aledbf]

Description

Remove noisy log http: TLS handshake error from XXX.XXX.XXX.XXX:XXXXX: EOF due to clients using plain TCP connections instead of TLS. One of the sources for these errors are the load balancer checks.

How to test

• Port forward ws-proxy TLS port running kubectl port-forward svc/ws-proxy 9090 &
• Using netcat check we can reach the port nc -zv localhost 9090
• Check the ws-proxy pod log does not contains lines like http: TLS handshake error from XXX.XXX.XX.XX:XXXX: EOF

Release Notes

NONE

Build Options:

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish Options

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer Options

• with-ee-license
• with-dedicated-emulation
• with-ws-manager-mk2
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment Options:

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• /werft with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

[werft-gitpod-dev-com]

started the job as gitpod-build-aledbf-error-log.1 because the annotations in the pull request description changed
(with .werft/ from main)

[werft-gitpod-dev-com]

started the job as gitpod-build-aledbf-error-log.2 because the annotations in the pull request description changed
(with .werft/ from main)