| commit | 049049626fe28957009c7957fba5e04bd928ae78 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Mon Nov 11 15:21:14 2019 +0100 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Mon Nov 11 15:21:14 2019 +0100 |
| tree | 7ffc478b5e0a44a50ff06a1ded7c031af2085d1e | |
| parent | f79bfac498914c90395c577f4a2f70956d9a5c56 [diff] |
Added kube-controlplane binary This adds a custom binary which contains all Kubernetes control plane components. This is necessary since every control plane binary by itself is around 130MiB and this combined one is only around 150MiB. This can be cut in half to around 70MiB as soon as Kubernetes can be built providerless by Bazel. I'm not entirely happy with the integration, we may need gazelle exclusions and a plan to deal with go mod since it can't resolve the dependencies in a reasonable way. Test Plan: Manual test with kubectl (this by itself is not runnable) Bug: T485 X-Origin-Diff: phab/D256 GitOrigin-RevId: d76702f2cd0d71463ff891e5a44eac7b66be07f0
This is the monorepo storing all of nexantic's internal projects and libraries.
We assume a Fedora 30 or 31 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.