#90 Guidelines for quay usage for CentOS SIG
Opened 2 months ago by pingou. Modified 2 months ago

I have opened an infra ticket asking if there were guidelines about the use of the CentOS repository on quay.io for SIG [1].

I was told to ask the board to set the expectations, so here I am :)

For the record, here were the questions I've asked:
What's the current recommendation for SIGs wanting to use quay for images? Is there a mechanism in place for quay to provide access to a subset of the repository? Should each SIG create their own space? If so, are there best practices on how to mark that repository as being "official"?

[1] https://pagure.io/centos-infra/issue/1000


For the record, the Hyperscale SIG is currently using Quay for our container image builds: https://quay.io/repository/centoshyperscale/centos

This is documented at https://sigs.centos.org/hyperscale/content/containers/ (usage) and https://sigs.centos.org/hyperscale/internal/containers/ (releng / build).

So what we (I) did for the Hyperscale SIG accounts was that we created the accounts with our SIG name:

  • Pagure/GitLab: centos-sig-hyperscale
  • Quay: centoshyperscale
  • Twitch: centoshyperscale

... and so on.

These accounts/groups have their primary email address set to our SIG alias email so that account resets and recovery will go to something that the Project can redirect to someone else in the event everyone is gone.

Login to comment on this ticket.

Metadata