Files
Martin HoffmannandGitHub c277854eed Refactor the application call flow. (#1361)
This PR refactors how requests are processed in Krill. It creates a
clear distinction between the HTTP server running async on a Tokio
runtime and the core of Krill running as regular sync code on a thread
pool.

This means that those portions of the core that were previously async,
notable the HTTP requests to remote parents and publishers, end up
blocking a thread now. For most things this should be fine. For
potentially long-running tasks, we have a separate thread pool so they
won’t block all of Krill.
2026-04-02 11:59:18 +02:00

1.7 KiB
Raw Permalink Blame History

Rust Crate Status GitHub Actions Build Status Docker Pulls Documentation Status

Discuss on Discourse Mastodon Follow

Krill

Krill is a Resource Public Key Infrastructure (RPKI) daemon, featuring a Certificate Authority (CA) and publication server, written in Rust. If you have any feedback, we would love to hear from you. Dont hesitate to create an issue on Github or post a message on our forum.

For more information please refer to the documentation.

Public Krill Testbed Service

In case you want to try out Krill, or test new Krill releases, then you may want to use our public Krill testbed service. You can read more about this service in this blog post.