Conversation
squat
force-pushed
the
update_ci
branch
7 times, most recently
from
c2b96ce to
47b2697
Compare
squat
force-pushed
the
update_ci
branch
2 times, most recently
from
9bb5265 to
926ab79
Compare
The tooling to build Kilo is out of date and is preventing CI from running. This is, in turn, is preventing reviewing and merging PRs, leading the project to stagnate. This commit overhauls the build-system for Kilo, locks every single piece of tooling in a flake.lock file, enables dependabot to promote automatic updates to the code, and uses Nix for reproducible builds. Signed-off-by: squat <lserven@gmail.com>
Signed-off-by: squat <lserven@gmail.com>
Signed-off-by: squat <lserven@gmail.com>
Signed-off-by: squat <lserven@gmail.com>
Signed-off-by: squat <lserven@gmail.com>
Signed-off-by: squat <lserven@gmail.com>
If the kgctl path is not passed explicitly via an environment variable, then we need to resolve the path. Additionally, in more recent versions of k8s, the taint on control-plane nodes has changed names so we need to update our code to correctly untaint them. Signed-off-by: squat <lserven@gmail.com>
Signed-off-by: squat <lserven@gmail.com>
squat
force-pushed
the
update_ci
branch
6 times, most recently
from
401e2cf to
83f5b5a
Compare
The first issue is not so bad: cloudflare/boringtun#447 The second issue is severe: cloudflare/boringtun#348 This one is problematic because Kilo uses the WireGuard socket to detect configuration drift for the `kilo0` interface. Since boringtun always returns empty configuration, Kilo thinks that there is always configuration drift, resulting in reconfigurations of the interface every sync-interval seconds, which causes the interface to drop existing connections. This commit fixes the issues by switching from boringtun to the more maintained, upstream userspace WireGuard implementation wireguard-go. Furthermore, this commit locks the manifests to specific tags. Signed-off-by: squat <lserven@gmail.com>
Currently, the e2e tests do not exit if the adjacency or curl pods fail to come up. The tests will continue running for a long time and fail. These changes cause the tests to exit early. Signed-off-by: squat <lserven@gmail.com>
Signed-off-by: squat <lserven@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The tooling to build Kilo is out of date and is preventing CI from
running. This is, in turn, is preventing reviewing and merging PRs,
leading the project to stagnate. This commit overhauls the build-system
for Kilo, locks every single piece of tooling in a flake.lock file,
enables dependabot to promote automatic updates to the code, and uses
Nix for reproducible builds.
Signed-off-by: squat lserven@gmail.com