Attention Iron Bank Customers: On March 27, 2025, we are moving SBOM artifacts from the Anchore Scan job to the Build job to streamline the container hardening pipeline. If you currently download SBOMs from the Anchore Scan job, you can still get them from the Build job and from other sources, including IBFE and image attestations.
Project 'platform-one/big-bang/bigbang' was moved to 'big-bang/bigbang'. Please update any links and bookmarks that may still have the old path.
If someone installs the latest version of the flux cli client 1.18.0, it doesn't like IronBank flux's API versions, or maybe it's the version of the APIs in the BB helm chart?/maybe those are what actually need to get updated:
https://github.com/fluxcd/flux2/discussions/1916
The above link explains changes about flux's breaking change, it looks like it it has a few nice updates, I'm particularly looking forward to the reliability improvements:
Detect and report drift between the desired state (git, s3, etc) and cluster state reliably.
Reconcile empty sources including pruning of all the resources previously applied.
Should this ticket be repurposed to update the api references so the newer version of flux cli can be used? or is this just the IB image reference and what I'm proposing a separate ticket, I suspend since it's a breaking change it'd be the kind of thing where maybe both should be done at the same time.
This ticket involves several risks. Just updating the flux version is not enough. The docker flux API needs to be updated. The IB APIs and other BB APIs need to be changed too from v1 to v2. This adds more complexity and risks to this issue. We need to have a spike/discovery sprint and plan out how to move forward with this ticket. Therefore, I am removing this issue from Milestone 1.19.0.