Skip to content
Snippets Groups Projects
Select Git revision
  • 8e48d97392c3f9e24e319116fd00d590e70eb727
  • main default protected
  • renovate/main-linters
  • renovate/main-ghcr.io-renovatebot-base-image-10.x
  • renovate/main-ghcr.io-containerbase-devcontainer-13.x
  • next
  • revert-31645-feat/rename-gradle-wrapper-validation-action
  • renovate/main-redis-5.x
  • fix/36615b-branch-reuse-no-cache
  • chore/punycode
  • fix/36615-branch-reuse-bug
  • refactor/pin-new-value
  • feat/36219--git-x509-signing
  • feat/structured-logger
  • hotfix/39.264.1
  • feat/skip-dangling
  • gh-readonly-queue/next/pr-36034-7a061c4ca1024a19e2c295d773d9642625d1c2be
  • hotfix/39.238.3
  • refactor/gitlab-auto-approve
  • feat/template-strings
  • gh-readonly-queue/next/pr-35654-137d934242c784e0c45d4b957362214f0eade1d7
  • 41.24.0
  • 41.23.5
  • 41.23.4
  • 41.23.3
  • 41.23.2
  • 41.23.1
  • 41.23.0
  • 41.22.0
  • 41.21.4
  • 41.21.3
  • 41.21.2
  • 41.21.1
  • 41.21.0
  • 41.20.2
  • 41.20.1
  • 41.20.0
  • 41.19.0
  • 41.18.4
  • 41.18.3
  • 41.18.2
41 results

workers

Name Last commit Last update
..
developer-workspace/codespaces
developer-workspace/common
developer-workspace/gitpod
developer-workspace/README.md
README.md

Ephemeral developer workspaces

Aiming to provide better developer experience when making contributions to kube-prometheus, whether by actively developing new features/bug fixes or by reviewing pull requests, we want to provide ephemeral developer workspaces with everything already configured (as far as tooling makes it possible).

Those developer workspaces should provide a brand new kubernetes cluster, where kube-prometheus can be easily deployed and the contributor can easily see the impact that a pull request is proposing.

Today there is 2 providers in the market:

Codespaces

Unfortunately, Codespaces is not available for everyone. If you are fortunate to have access to it, you can open a new workspace from a specific branch, or even from Pull Requests.

image

image

After your workspace start, you can deploy a kube-prometheus inside a Kind cluster inside by running make deploy.

If you are reviewing a PR, you'll have a fully-functional kubernetes cluster, generating real monitoring data that can be used to review if the proposed changes works as described.

If you are working on new features/bug fixes, you can regenerate kube-prometheus's YAML manifests with make generate and deploy it again with make deploy.

Gitpod

Gitpod is already available to everyone to use for free. It can also run commands that we speficy in the .gitpod.yml file located in the root directory of the git repository, so even the cluster creation can be fully automated.

You can use the same workflow as mentioned in the Codespaces section, however Gitpod doesn't have native support for any kubernetes distribution. The workaround is to create a full QEMU Virtual Machine and deploy k3s inside this VM. Don't worry, this whole process is already fully automated, but due to the workaround the whole workspace may be very slow.

To open up a workspace with Gitpod, you can install the Google Chrome extension to add a new button to Github UI and use it on PRs or from the main page. Or by directly typing in the browser http://gitpod.io/#https://github.com/prometheus-operator/kube-prometheus/pull/<Pull Request Number> or just http://gitpod.io/#https://github.com/prometheus-operator/kube-prometheus

image