| commit | 78fd97294dbc8bbf5ef1a490b2d7b7ad96fddcae | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Mon Jul 13 17:01:42 2020 +0200 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Mon Jul 13 17:01:42 2020 +0200 |
| tree | 7ae5efa88e132d538d9ec185e6abddd9f46a0570 | |
| parent | cca74b6b61a165e2d1679847731902eaed04bd94 [diff] |
Kubernetes volume & stamping fixes This reenables the projected and downwardapi volume types, both of which are necessary for the CTS to pass and are derivatives of the configmap volume which we already support. This also fixes an issue where the stamping definitions for Kubernetes were not present on our main Kubernetes binary, which broke the CTS. Test Plan: Volumes will be covered by CTS (writing our own tests would be duplicate work), version was manually tested to be correct in `bazel run //core/cmd/dbg -- kubectl get nodes` since stamping is hard to test for. X-Origin-Diff: phab/D584 GitOrigin-RevId: 403b6c845bc399fdd44ec3ba4ca26e2512a5bc98
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)
Launch the node:
bazel run //:launch
Run a kubectl command:
bazel run //core/cmd/dbg -- kubectl describe
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.