Add contributing guidelines with a local kubernetes cluster or minikube

[gtsiolis]

Problem to solve

Following the proposal in #6466, we'd like to do as part of making it easier for everyone to contribute to Gitpod and one of the steps we need to make is introduce some contributing guidelines with a local kubernetes cluster or minikube. 🧊

Looping in @iQQBot as they were interested in helping, see #6466. 🏀

[iQQBot]

/assign

[iQQBot]

I will finish at this weekend

[gtsiolis]

Hey @iQQBot! Did you have the chance to take a look at this?

[iQQBot]

What I want to do is a developer friendly documentation

They don't need

1. real world domain
2. real https certificate

They can compile, deploy and test on it

For this reason, I need to make Gitpod able to trust the built-in certificates
#6590
and make leeway support minio instead of just GCP
gitpod-io/leeway#70

But neither of these PRs have been merged into the main branch yet

[iQQBot]

Given that we are currently optimizing the installer experience, and that the helm charts will soon be deprecated, I suggest waiting for the installer release to continue this work

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[shaal]

Please add meta: never-stale

[atduarte]

Replacing the owner team with self-hosted, as they would be the best team to update guidelines regarding using the installer for contribution workflows. cc @lucasvaltl

[lucasvaltl]

I suspect that #9075 might help with this :)

[corneliusludmann]

Closing this in favor of #9075.