You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user of Zarf and Flux I want a Zarf package that simplifies the deployment of Flux, but keeps Registry1 as the source of the images that get run, so that I can have a simple way to deploy Flux without also needing to maintain a Utility Cluster.
Acceptance Criteria:
New Zarf example flux-from-iron-bank (or some other appropriate name) exists
It packages the manifests needed to deploy Flux, but not the images (they should just come from Iron Bank)
Nice-To-Have:
The Flux manifests are pulled automatically from Repo1 so they don't need to be frequently updated
Notes:
This example will be of limited usefulness until after the Native K8s Apply work is done. Once that is done we should be able to use it to deploy Flux to any cluster with ease.
The text was updated successfully, but these errors were encountered:
I don't really understand the value of this one. If you're just using Zarf to install a manifest and not care about images at all, why not use kubectl? Can we re-evaluate this one @RothAndrew?
As a user of Zarf and Flux I want a Zarf package that simplifies the deployment of Flux, but keeps Registry1 as the source of the images that get run, so that I can have a simple way to deploy Flux without also needing to maintain a Utility Cluster.
Acceptance Criteria:
flux-from-iron-bank
(or some other appropriate name) existsNice-To-Have:
Notes:
The text was updated successfully, but these errors were encountered: