| commit | 6888873fad889bfb7cd594b4208798f80eb60f43 | [log] [tgz] |
|---|---|---|
| author | Tim Windelschmidt <tim@monogon.tech> | Thu Aug 03 14:25:28 2023 +0000 |
| committer | Tim Windelschmidt <tim@monogon.tech> | Tue Aug 29 10:08:29 2023 +0000 |
| tree | 860ca3a83e6a6667888ec8595cc332f44e1cb6aa | |
| parent | 29ac140c4cbdb8dd8d71863de8c9b4473a1c0215 [diff] |
metropolis/node: dont allocate node ports in constructor All good things are three, and this should be the final installment in the saga of getting ports reserved. The Kubernetes codebase always starts a recovery after initialization of a new port allocator, which currently makes it very unhappy as we already allocated the system ports, but we are trying to do the same in the recovery by pretending to be a service. Anyway, this removes the initial part of the patch and only uses the recovery way of reserving the ports. This still creates an annoying message sometimes, but I can't find the code path which creates them. Change-Id: Ib7d9ec5d00cbde7371d876c31c63b5312024a187 Reviewed-on: https://review.monogon.dev/c/monogon/+/2027 Reviewed-by: Lorenz Brun <lorenz@monogon.tech> Tested-by: Jenkins CI
This is the main repository containing the source code for the Monogon Platform.
This is pre-release software - take a look, and check back later!
Our build environment is self-contained and requires only minimal host dependencies:
/dev/kvm (if you want to run tests).Our docs assume that Bazelisk is available as bazel on your PATH.
Refer to SETUP.md for detailed instructions.
Build CLI and node image:
bazel build //metropolis/cli/dbg //:launch -c dbg
Launch an ephemeral test node:
bazel test //:launch -c dbg --test_output=streamed
Run a kubectl command while the test is running:
bazel-bin/metropolis/cli/dbg/dbg_/dbg kubectl describe node
Run full test suite:
bazel test -c dbg //...