Yoke already integrates with ArgoCD via CMP plugins.
We now want to also integrate with Flux.
Discussion can be found here: https://cloud-native.slack.com/archives/CLAJ40HV3/p1746729397106679
Implementation:
Two approached are possible and we may want to perform both for different reasons.
- Extend the ATC to support a Generic Flight resource
- Create a Flux Controller integrating with other Flux Toolkit controllers and resources such as OCIRepositories and their Notifications Setup.
Option 1 could serve as a core basis for users wanting to deploy flights in a server-side way without wanting to create CRDs via Airways for reuse. This option trivially integrates with Gitops patterns such as ArgoCD and Flux, but do not fully integrate with their internal bells and whistles. This approach is valid but should come with warning around security.
Option 2 is more complex but of more value for Flux users. Before work can be started on this, a more comprehensive design will need to be drawn up as my comprehension of the flux ecosystem is still murky at best.
Yoke already integrates with ArgoCD via CMP plugins.
We now want to also integrate with Flux.
Discussion can be found here: https://cloud-native.slack.com/archives/CLAJ40HV3/p1746729397106679
Implementation:
Two approached are possible and we may want to perform both for different reasons.
Option 1 could serve as a core basis for users wanting to deploy flights in a server-side way without wanting to create CRDs via Airways for reuse. This option trivially integrates with Gitops patterns such as ArgoCD and Flux, but do not fully integrate with their internal bells and whistles. This approach is valid but should come with warning around security.
Option 2 is more complex but of more value for Flux users. Before work can be started on this, a more comprehensive design will need to be drawn up as my comprehension of the flux ecosystem is still murky at best.