This release focused on testing, and fixing, any issues found when running Krill under various parent CAs (Apnic, Lacnic and RIPE NCC). ROAs were tested using routinator, OctoRPKI, FORT, RIPE NCC RPKI Validator 2.x and 3.x.
Furthermore, the CLI got a big overhaul aimed at making it easier to use, especially for users who manage one CA only. You can now use ENV variables to set defaults for the Krill instance to connect to, the token, and which CA you want to operate on.
We also added the
--api argument which will simply print out the API call that the CLI would have made, without executing it. We plan to add proper (OpenAPI) documentation for the API, but for the moment this can help to explore it.
Updated documentation can be found on Read the Docs.
- Despite our best efforts RIPE NCC RPKI Validator 3.1 is the only remaining RP we tested, which
does not seem to like our manifests. We will look into this again later. (#115)
- There appears to be a race condition that can cause commands to be processed twice. (#64)
- Showing the full history, or logging it in case of the above condition, uses too much memory. (#112)
- The CA and publication server can be out of sync after a re-start. (#116)
Work for the next release has already started. Release 0.3 will focus on (remote) publication, and will also solve the out-of-sync issue.