[proxy] add a liveness check

[kylos101]

Description

This is an initial iteration, to setup a liveness check for caddy using the existing /live endpoint on the readiness port. If the problem continues, where new cells sometimes fail the installation because all proxy pods never become ready, we'll want to add a more complex liveness check, perhaps using wait4x, where we check 8003 and 9545 and other ports for "liveness".

E.g.

ProbeHandler: corev1.ProbeHandler{
		Exec: &v1.ExecAction{
			Command: []string{"wait4x", "http", "http://127.0.0.1:9545", "&&", "wait4x", "http", "http://127.0.0.1:8003"},
		},
	},

Reference for the wait4x idea: #8777

Related Issue(s)

Fixes ENG-1889

How to test

Documentation

Preview status

Gitpod was successfully deployed to your preview environment.

• 🏷️ Name - kylos101-eng-1889
• 🔗 URL - kylos101-eng-1889.preview.gitpod-dev.com/workspaces.
• 📚 Documentation - See our internal documentation for information on how to interact with your preview environment.
• 📦 Version - kylos101-ENG-1889-gha.23578
• 🗒️ Logs - GCP Logs Explorer

Build Options

Build

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

Publish

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

Installer

• analytics=segment
• with-dedicated-emulation
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment / Integration Tests

• /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 preemptible
  Saves cost. Untick this only if you're really sure you need a non-preemtible machine.
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
• with-monitoring

/hold