commit | 5b2ae5500a90dc48b9713095e5f1580b9c9646d9 | [log] [tgz] |
---|---|---|
author | Serge Bazanski <serge@monogon.tech> | Tue Aug 17 13:00:14 2021 +0200 |
committer | Sergiusz Bazanski <serge@monogon.tech> | Mon Aug 23 12:26:16 2021 +0000 |
tree | 1f6efbed2aa20716c18772bb30dbafacd6f07db3 | |
parent | 03758714f4b7be2a712831beecfdfcbf151b4c66 [diff] |
m/n/c/curator: listen on public gRPC This enables listening on CuratorPort (which was called NodeServicePort) using TLS node certificates. No service is yet running on the new gRPC listener. Change-Id: I436ac1ae9cbdb257419ad114262fc2a7516396b1 Reviewed-on: https://review.monogon.dev/c/monogon/+/288 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 that happens to be publicly available. Nothing to see here, please move along.
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 //...