| commit | fa5c2fccc528b40f216687e02f0c1cd004e013d6 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Mon Sep 28 13:32:12 2020 +0200 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Mon Sep 28 13:32:12 2020 +0200 |
| tree | f39c24f681176b7bbf36fe6af304c6902124f552 | |
| parent | 4efaa019244db96128941965aa72c0e1371b0d2d [diff] |
Use CoreDNS for everything and make directives dynamic This moves CoreDNS from Kubernetes to the network tree and uses it for OS-side resolution too. For this to work together with Kubernetes it now contains a dynamic directive system which allows various parts of the OS to register and unregister directives at runtime. This system is used to hook Kubernetes and DHCP-supplied DNS servers into the configuration. This also enables the hosts plugin to resolve the local hostname from within CoreDNS to avoid querying external DNS servers for that (T773). Test Plan: CTS covers K8s-related tests, external resolution manually tested from a container. Bug: T860, T773 X-Origin-Diff: phab/D628 GitOrigin-RevId: f1729237f3d17d8801506f4d299b90e7dce0893a
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.