| commit | a959cbd12c29b62045f02b1d22cdf1e36c0261a4 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Thu Jun 17 15:56:51 2021 +0200 |
| committer | Sergiusz Bazanski <serge@nexantic.com> | Tue Jul 20 12:02:29 2021 +0000 |
| tree | 7f44cdf24c3c02f7d9ba866a2d37275673a0dd11 | |
| parent | 0d93777cf32dd0d0f6f8d75d8396f7140cff9d13 [diff] |
metropolis/node/core/cluster: use curator This refactors the cluster manager. It removes all etcd storage functionality (which now lives in the curator) and otherwise dusts things off slightly (some file renames, some comments to reflect the now clarified and limited scope of the cluster manager). Change-Id: Ic62d8402c0618fb5e0e65966b0d732a2cab564e0 Reviewed-on: https://review.monogon.dev/c/monogon/+/188 Reviewed-by: Lorenz Brun <lorenz@nexantic.com>
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 //...