Based on the forward strategy in https://pagure.io/fedora-infrastructure/issue/10386 (moving fedora containers to be hosted on quay.io) and the outcomes from a previous releng meeting we would like request for access to be able to create/modify containers under the following name in quay.io:
quay.io/fedora/fedora-coreos-kubevirt
quay.io/fedora/fedora-coreos
I imagine those namespaces would need to be created and then ACLs applied for us to push there and then credentials shared with us.
Maybe the next few weeks? 2022-06-01
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-trouble, medium-gain, ops
@humaton might know where this is?
xref: https://github.com/coreos/fedora-coreos-tracker/issues/1171
Metadata Update from @cverna: - Issue assigned to cverna
I have created an fcos team in the fedora organization where you can add members allowed to create new repositories.
fcos
I have created 2 empty repositories quay.io/fedora/fedora-coreos-kubevirt and quay.io/fedora/fedora-coreos
I have also created a robot account fedora+fcos with read+write permission to these 2 repositories and added the credentials to the bitwarden vault we used for other FCOS secrets.
fedora+fcos
Let me know if something else is needed
Metadata Update from @cverna: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
@humaton do you have a quay.io username ? So that I can give you admin access to the fedora organization, maybe @nirik too ?
Login to comment on this ticket.