I’m going to start to create a hand-curated list of interesting things that has been and will be happening with Kro.

This will be notable pull requests that have been merged. Interesting blogs that might be of relevance. Information on what we are planning to do next and all kinds of news related to Kro.

Let’s dive in to the first episode of… This week in Kro!

Read this in old-timey anchor news voice.

Today, I’m happy to announce to you that v0.10.0.rc0 has been cut! Yes! You heard right! Get it while it’s hot! It contains a lot of goodies so hang on to your butts while we go through the most interesting ones.

This release contains the most massive update the RGD engine, and it contains several fixes that have been long plaguing the community. Fixes such as, invalid long node-ids and instance-name labels. You can use as long as a node-id that you want without having to worry about the maximum 63 character label length. Further, RGD schema changes have gotten a beefing up with more validation rules. This one might catch you if you don’t pay attention! But most important of all… Graph CRD has landed!

KREP-024 has been implemented! It was a herculean effort to get it in over the course of several weeks of test runs, reviews and fixes. It is one of the most tested paths in the entire code base, and yet! There might be still dragons lurking in it (as the number of “fix” PRs show), so proceed with caution. Today, you need a flag to enable it. Please read the Documentation carefully (It is available by selecting main version on the Kro website).

Please check out the Release page for more concrete changes linked up above.

Some up-coming interesting additions that people are working on are in no particular order:

  • KREP-025 CEL Time library is getting lots of thoughts accumulated and is bound to be an interesting addition for people who would hate to be woken up on a sunday morning by a failed certificate rotation attempt.
  • KREP-021 Kro CLI has been revived and is being pushed forward.
  • Deletion Policy for individual resources has been created and is under review. The issues has been talked about and tentatively accepted during a community call, but, naming being one of the hardest things in software, how we call the policy is up for debate.
  • Cycle detection optimization this one might look tiny, but it actually increases the performance of cycle detection by a LOT.
  • CEL Anywhere I’m sure everyone thought at some point “Hey, why can’t I use a CEL function there?” right? Well, now you can.
  • Allow referring to CRDs that do not exist yet is an issue that pops up in various forms like defer for schemas or a more ergonomic way of referencing a CRD. This has been solved by Graphs! Yet another reason why you should check them out.

In other news:

Jesse Butler mentioned in last community meeting that he would like to re-visit the usage of KREPs in the Kro ecosystem. This came from the problem that he believe KREPs got a bit out of hand and people use them for bike-shedding ideas around a concept and thus the pull request and the discussions explode quickly. They, however, seem to be no longer so useful after a while and the idea gets abandoned because it gets nowhere and the person who opened the KREP gets discouraged from engaging further.

This seems like a good time to review this idea and figure out how to better handle architectural decisions and ideas.

Eddie Moya, keeps updating his amazing set of complex RDG examples to provide the community with a nice set of not-so-basic-usage scenarios over at his Codeberg Repository for Gitea RGD.

And this is all for this week folks! Hope to see you again next time.

Have a lovely rest of the Sunday.

Gergely.