| commit | 516d300df9a34da5b39944017cebf1b11897e7a0 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@monogon.tech> | Fri Oct 01 00:05:41 2021 +0200 |
| committer | Sergiusz Bazanski <serge@monogon.tech> | Tue Nov 16 14:39:15 2021 +0000 |
| tree | b045662801001e5c53412baa6d744346892830f0 | |
| parent | c6c092be9c8774192867620d1df41c6014e20de1 [diff] |
m/n/c/curator: implement Curator.RegisterNode This is the 'Register' call from the cluster lifecycle design document. We don't yet call it from node startup code, but we do exercise it in a Curator test. Change-Id: Ife617b148a25fc8aecb0ed15f78a758ca4538016 Reviewed-on: https://review.monogon.dev/c/monogon/+/423 Reviewed-by: Lorenz Brun <lorenz@monogon.tech>
This is the main repository containing the source code for the Monogon Project.
This is pre-release software - feel free to look around, and check back later for our first release!
Our build environment requires a working Podman binary (your distribution should have one).
Spinning up: scripts/create_container.sh
Spinning down: scripts/destroy_container.sh
Running commands: scripts/run_in_container.sh <...>
Using bazel using a wrapper script: scripts/bin/bazel <...> (add to your local $PATH for convenience)
This repository is compatible with the IntelliJ Bazel plugin, which enables full autocompletion for external dependencies and generated code. All commands run inside the container, and necessary paths are mapped into the container.
The following steps are necessary:
Install Google's Bazel plugin in IntelliJ. On IntelliJ 2020.3 or later, you need to install a beta release of the plugin.
Add the absolute path to your ~/.cache/bazel-monogon folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-monogon
Set "Bazel Binary Location" in Other Settings → Bazel Settings to the absolute path of scripts/bin/bazel. This is a wrapper that will execute Bazel inside the container.
Use File → Import Bazel project... to create a new project from .bazelproject.
After running the first sync, everything should now resolve in the IDE, including generated code.
Launch the node:
scripts/bin/bazel run //:launch
Run a kubectl command:
scripts/bin/bazel run //metropolis/cli/dbg -- kubectl describe
Run tests:
scripts/bin/bazel test //...