| commit | 1de8b1845e75dc1e020df21b997b2d6fc66fb65e | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@monogon.tech> | Tue Dec 21 17:15:18 2021 +0100 |
| committer | Lorenz Brun <lorenz@monogon.tech> | Wed Dec 22 15:57:16 2021 +0000 |
| tree | 4a41005b1931aa13c3ed4a1b0732de31482a6eb8 | |
| parent | 367f759f54e59b24b55024c8070513f9f7e6f4c1 [diff] |
m/node: pass node identity into k8s This plumbs through the node identity to K8s as an identity.Node object and gets rid of the os.Hostname invocation that passed around this data out-of-band. It also changes everything in its path to use the newer identity.Node object instead of a plain string so that the Metropolis Identity CA is more accessible. Change-Id: I6db8e1db7e333c0ea364aefd61c27bf50acc25f3 Reviewed-on: https://review.monogon.dev/c/monogon/+/505 Reviewed-by: Sergiusz Bazanski <serge@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 //...