| commit | 8e3b8fc9c4ccf5f92179c249de692e38a92d6ee0 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Tue May 19 14:29:40 2020 +0200 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Tue May 19 14:29:40 2020 +0200 |
| tree | 0cb705a7be0e42ac642cef771edab856f6676098 | |
| parent | 8da5377d65930ff0a4085449c61f09fcfe64ec02 [diff] |
Port kubernetes package to supervisor This replaces the ad-hoc goroutine and process management previously in the kubernetes package with a nice supervisor-based implementation which should make it easier to understand and more reliable. It also prevents creation of more ad-hoc launching code for future features (like CSI & Provisioning). Since porting SmalltownNode is rather involved I just instantiated a new supervision tree in the Kubernetes main service and wired it up to the old interface. Once we port SmalltownNode we can just remove the legacy Start() method and directly call Run(). Test Plan: Passes Bazel tests, Kubernetes functionality was manually tested by running `bazel run //core/cmd/dbg -- kubectl run -i --image alpine:edge sh` to verify that Kubernetes still works properly. Automated tests for this are being worked on. X-Origin-Diff: phab/D534 GitOrigin-RevId: 001de38eaa5c7ee661bf5db9a7c3d0125c1b6af2
This is the monorepo storing all of nexantic's internal projects and libraries.
We assume a Fedora host system provisioned using rW, and IntelliJ as the IDE.
For better reproducibility, all builds are executed in containers.
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. All commands run inside the container, and necessary paths are mapped into the container.
We check the entire .ijwb project directory into the repository, which requires everyone to use the latest version of both IntelliJ and the Bazel plugin, but eliminates manual setup steps.
The following steps are necessary:
Install Google's official Bazel plugin in IntelliJ.
Add the absolute path to your ~/.cache/bazel-nxt folder to your idea64.vmoptions (Help → Edit Custom VM Options) and restart IntelliJ:
-Dbazel.bep.path=/home/leopold/.cache/bazel-nxt
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.
Open the .ijwb folder as IntelliJ project.
Disable Vgo support for the project.
Run a non-incremental sync in IntelliJ
The plugin will automatically resolve paths for generated files.
If you do not use IntelliJ, you need to use the scripts/bazel_copy_generated_for_ide.sh script to copy files locally.