Abby Bangser
Abby Bangser
Promises and resources are reconciled based on events in Kubernetes including resource changes, Kratix controller restarts, and general time passing (defaults to 10hours). While resources will reconcile every 10 hours...
Kratix uses a utility image to run actions both before and after the Promise defined workflows. These actions used to be limited to just creating works and therefore the image...
With Kratix being a Kubernetes controller, it is expected that it could reconcile at any point. The most common triggers are: 1. Changes 2. Restarts of the controller It is...
There was some question in the slack about the impact of community vs "TAG" derived work. We want to encourage people to post their opinions (so long as they are...
In #219 we introduced the tracking and scheduling of regular reconciliations for Promise workflows. This story should provide the same functionality for resource requests. If a resource request exists, it's...
Kratix workflows are able to write documents to the `/kratix/output` directory and have those documents written out to the relevant destinations/statestores. This write process is triggered after a work is...
The current implementation is a single HTTP request (https://github.com/syntasso/kratix/blob/0314320eec4c1f0d3a625ffbac717004287a1f31/lib/fetchers/url.go#L17). This is something that will work _a lot_ of the time, but not _all_ of the time. Some basic resiliency issues...
In order to securely connect to cloud resources from a Kratix Workflow users may want to use cloud specific service accounts. In all three major clouds (AWS, GCP, Azure) they...
I believe this is due to this issue/fix: https://github.com/cert-manager/cert-manager/issues/3717#issuecomment-1515135268 We will need to move from static files and use a helm template possibly.