What are examples of OKRs you set for your technical teams? Do they always line up to business objectives or are they sometimes siloed?

I usually try to stay away from all sorts of dogmas. OKR is simply a framework. It defines a goal and outlines specific, measurable actions for tracking the progress towards achieving it. The framework can be used for different purposes (e.g. personal, business) and applied at different levels (e.g. individual, team, org). Of course, when you apply OKR in business settings working with groups of people storytelling becomes very important. Everybody benefits from understanding the context, the purpose, the strategic plan alignment, etc. But I would not obsess about it.

I don't see why a technical team's OKR should not be linked to the business outcome. Even the seemingly purely technical stuff should be helping the business as a whole - improving the resilience, reducing costs or addressing some business risk... If there is no value for the business, why would you set such objective?