Set Cluster API Provider Packet packages to public

[cprivitere]

Organization or Repo

kubernetes-sigs/cluster-api-provider-packet

User affected

No response

Describe the issue

We would like to have the Github Container Registry be a source for Cluster API Provider packet images (in addition to quay.io and docker.io). Can you please set the visibility of the Cluster API Provider Packet packages to public?

Thanks.

[displague]

This would give users more choice in image repositories which has proven to be a valuable as image repository service providers change their policies.

There are other Kubernetes-Sigs projects (including cluster-api related projects) using public GHCR images. https://github.com/orgs/kubernetes-sigs/packages?tab=packages&q=cluster-api

[cprivitere]

/auto-cc

[cprivitere]

/woof

[k8s-ci-robot]

@cprivitere:

In response to this:

/woof

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[mrbobbytables]

We would like to have the Github Container Registry be a source for Cluster API Provider packet images (in addition to quay.io and docker.io). Can you please set the visibility of the Cluster API Provider Packet packages to public?

@cprivitere We looked into this in a general issue here: #4514
and unfortunately we can't enable public GHCR repos =/

(copied response from here: #4514 (comment))

We looked into it and unfortunately we can't enable the github package functionality for public use.
Essentially github does not give any granual permissions over repos and which ones can be public or private. It's an all or none thing meaning anyone can create public packages or no one can. Packages also exist outside of github's regular permission system, we cannot create custom roles or anything that could better manage access.

If/when GitHub updates it, we can revisit - but for now it's not something we're going to move forward with enabling. =/

[cprivitere]

Thanks for the decision and details.