-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Remove ostree commit to Pulp upload features from Image Builder
-
False
-
None
-
False
-
Testable
-
To Do
-
RHIN-1335 - Image Builder pushes OSTree commits to Hosted Pulp
-
-
- Currently the Edge service downloads the tarball from IB's storage (S3) and uploads it to the edge service storage before making it available to the user.
- osbuild-composer can, currently, push ostree commits straight to pulp, but the implementation is lacking (notably, auth).
- For the long term, we will not be using pulp's ostree capabilities because everything is moving to image mode RHEL / bootc / containers.
- The new plan is to have the edge service download the tarball from IB's storage (like it already does) but instead of uploading it to the edge service's S3 storage, it will push to pulp. That way we can drop pulp ostree support from osbuild-composer and decommission the edge service along with the pulp support when the time comes to fully migrate to bootc containers.
The pulp-ostree upload functionality should be removed from osbuild-composer as soon as the edge service starts pushing ostree commits to pulp itself.
- is blocked by
-
HMS-2796 Edge API creates a secure Pulp OSTree repo and distribution
-
- In Progress
-