Update k8s dependencies to v0.24.3

[aledbf]

Description

• Update k8s dependencies to v0.24.3
• Remove empty status and resource definitions from manifests

Related Issue(s)

fixes #8529
fixes #11136

How to test

• Check workspaces work as usual
• Check the generated manifests do not contain empty status or resource definitions

docker run --entrypoint sh --rm \
  eu.gcr.io/gitpod-core-dev/build/installer:aledbf-k8s24.11 -c "cat /app/installer" >gitpod-installer

chmod +x gitpod-installer

cat <<EOF >values.yaml
apiVersion: v1
domain: fake.gitpod.io
EOF

./gitpod-installer render --use-experimental-config --config values.yaml > manifests.yaml

Release Notes

NONE

Werft options:

• /werft with-preview

[aledbf]

/werft run

👍 started the job as gitpod-build-aledbf-k8s24.1
(with .werft/ from main)

[aledbf]

/werft run with-preview

👍 started the job as gitpod-build-aledbf-k8s24.7
(with .werft/ from main)

[corneliusludmann]

It seems like this pull request implements item (3) as described in #11136, right?

I actually miss the discussion on this issue why we have decided to implement that solution and not one of the other proposed ones? 🤔

[corneliusludmann]

Would you mind also removing this:

gitpod/install/kots/manifests/gitpod-installer-job.yaml

Lines 314 to 318 in 1b1248d

	# Workaround for #8532 and #8529
	echo "Gitpod: Remove the StatefulSet status object for OpenVSX Proxy"
	yq eval-all --inplace \
	'del(select(.kind == "StatefulSet" and .metadata.name == "openvsx-proxy").status)' \
	"${GITPOD_OBJECTS}/templates/gitpod.yaml"

[aledbf]

It seems like this pull request implements item (3) as described in #11136, right?

Yes.

I actually miss the discussion on this issue why we have decided to implement that solution and not one of the other proposed ones? thinking

Sorry, I assumed the only "real" option is 3.

1. Post-process with yq

Too complex to maintain

2. Lock the versions to the Kubernetes versions we support

We already do that (to some extent), pinning the versions with leeway.

[aledbf]

Would you mind also removing this:

gitpod/install/kots/manifests/gitpod-installer-job.yaml

Lines 314 to 318 in 1b1248d

	# Workaround for #8532 and #8529
	echo "Gitpod: Remove the StatefulSet status object for OpenVSX Proxy"
	yq eval-all --inplace \
	'del(select(.kind == "StatefulSet" and .metadata.name == "openvsx-proxy").status)' \
	"${GITPOD_OBJECTS}/templates/gitpod.yaml"

done

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

<sup><sub>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sub></sup>

[aledbf]

/werft run with-preview

👍 started the job as gitpod-build-aledbf-k8s24.15
(with .werft/ from main)

[aledbf]

/werft run with-preview with-clean-slate-deployment

👍 started the job as gitpod-build-aledbf-k8s24.16
(with .werft/ from main)

[aledbf]

@csweichel @Furisto @akosyakov @geropl friendly ping :)

[aledbf]

/werft run with-preview with-clean-slate-deployment

👍 started the job as gitpod-build-aledbf-k8s24.20
(with .werft/ from main)

[AlexTugarev]

@aledbf, it seems this PR breaks the installer's render test. I see changes to the golden files of the installer tests, and I'm missing test run in the most recent build job of this PR.

Which version of the test data is correct?

[AlexTugarev]

📦 cached install/installer:raw-app

The tests were definitely not executed. Seems like cache control (invalidation) is broken in this area.

[aledbf]

@AlexTugarev #12299