| commit | bb7db92ee6e788b576e22ece70914e0321a785f7 | [log] [tgz] |
|---|---|---|
| author | Serge Bazanski <serge@nexantic.com> | Thu Apr 30 12:43:10 2020 +0200 |
| committer | Serge Bazanski <serge@nexantic.com> | Thu Apr 30 12:43:10 2020 +0200 |
| tree | 1f4fee21a390625bd9766d0394e3076cf7e34d48 | |
| parent | 547b33f2b38dba41f2c171f8730ff5093b267eaf [diff] |
Add all dependencies for Kubernetes worker Adds Kubelet, CNI plugins, containerd, runc and gVisor using a pre-baked list of dependencies generated using scripts/gazelle-deps/sh. This moves all dependencies of gVisor, Kubernetes, runc, etc into the same 'namespace' of Bazel external repositories, giving us ease of accessing code as libraries, and benefits when it comes to version auditing. The gazelle-deps.sh script is a temporary solution that will be replaced ASAP, see T725. This unblocks T486. This is an alternative to D389. Test Plan: `bazel build //core:image` runs and picks up the new binaries X-Origin-Diff: phab/D487 GitOrigin-RevId: a28a25071fa2ae76b272d237ce9af777485065ff
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.