| commit | 6e8f69c53a2c82f5a760ab2e8152218cc86f3430 | [log] [tgz] |
|---|---|---|
| author | Lorenz Brun <lorenz@nexantic.com> | Mon Nov 18 10:44:24 2019 +0100 |
| committer | Lorenz Brun <lorenz@nexantic.com> | Mon Nov 18 10:44:24 2019 +0100 |
| tree | 1556b56e0a0cdb5108c301dc88710b5b2d74ba1b | |
| parent | b7a18fd9be7732e9ed9b29f33b7f545916da207b [diff] |
Initial Kubernetes Control Plane This adds a minimum viable Kubernetes Control Plane consisting of a kube-apiserver, kube-controller-manager and kube-scheduler. It contains two small CAs for Kubernetes Identity management based on shared certificates and contains changes for exposing etcd via UNIX socket so that the apiserver can talk to it. Test Plan: Tested by manually calling Setup() and observing subsequent logs and connecting to the API server. Bug: T485 X-Origin-Diff: phab/D271 GitOrigin-RevId: e56f3e50eb9d33ea291289faa1aac3bebdeb3346
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.