Chainloop is a cloud-native application with two main server-side components (green boxes) and three dependencies (in red): an OpenID Connect (OIDC) identity provider, a PostgreSQL database, and a secrets storage backend.
The selection of what to use as an identity provider, database, or storage backend is up to the operator. In most cases, these are influenced by what cloud platform Chainloop is deployed to. For example, the table below shows a non-exhaustive configuration matrix of scenarios where, in many cases, operators leverage cloud-specific managed services to reduce operational overload and moving pieces.
We understand that operating Chainloop should be as easy as possible, a means to an end. That's why we strive to offer consistent, cloud-native support to our users, and today, we are happy to announce that our latest release adds support for Azure KeyVault.
In practice, this means that now, when you deploy Chainloop on Microsoft Azure, you can fully leverage Azure-managed services by not only using CloudSQL, as DB, and Azure Blob Storage for content addressable storage (CAS) but also Azure KeyVault for credentials handling.
This addition makes this deployment topology on par (and in some cases ahead :) of what we already support in other major cloud providers.
Congratulations, Azure users! 🎉
Please send feedback our way, and if you like what we do, give our GitHub repository a star :)