Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracker for cleanups possible after RHCOS moves to FCOS pipeline #3134

Open
1 of 6 tasks
jlebon opened this issue Oct 24, 2022 · 2 comments
Open
1 of 6 tasks

Tracker for cleanups possible after RHCOS moves to FCOS pipeline #3134

jlebon opened this issue Oct 24, 2022 · 2 comments

Comments

@jlebon
Copy link
Member

jlebon commented Oct 24, 2022

This is a tracker for all the cleanups we should be able to do once we've fully moved over RHCOS to the new pipeline.

  • delete cosa push-container; we only use cosa push-container-manifest now for all our containers
  • delete upload-ami; we use pure cosa buildextend-aws --upload now with support for granting to additional users, scheduling AWS tests and marking the AMIs public: scripts: drop upload-ami openshift/os#1074
  • delete cosa buildextend-extensions; this was the legacy way to publish extensions
  • make digest required again in images (see cmd-push-container-manifest: change image key schema #3129) (though this is more dependent on branching on 4.12)
  • delete cosa build-extensions-container backcompat alias
  • delete cosa buildextend-legacy-oscontainer; we don't need to build or ship the legacy oscontainer anymore
@jlebon jlebon changed the title coreos-assembler cleanups possible after RHCOS moves to FCOS pipeline Tracker for cleanups possible after RHCOS moves to FCOS pipeline Oct 24, 2022
@dustymabe
Copy link
Member

@jlebon bump

The RHCOS and FCOS share the same pipeline code now.

@jlebon
Copy link
Member Author

jlebon commented Apr 18, 2023

I think we're still dependent on the legacy oscontainer for now. https://issues.redhat.com/browse/MCO-392 tracks its removal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants