Update default container registry to something other than Docker Hub (keep publishing images to Docker Hub)

k8ssandra / cass-operator

The DataStax Kubernetes Operator for Apache Cassandra

https://docs.datastax.com/en/cass-operator/doc/cass-operator/cassOperatorGettingStarted.html

Apache License 2.0

187 stars 66 forks source link

Update default container registry to something other than Docker Hub (keep publishing images to Docker Hub) #414

Open bradfordcp opened 2 years ago

bradfordcp commented 2 years ago

What is missing? Docker Hub has instituted pull limits for authenticated and anonymous users. This can lead to issues if a pull secret is not configured and used within Kubernetes.

Why do we need it? Users may run into the issue of images not being pulled due to hitting their rate limit

Cass Operator version:

Any

Anything else we need to know?: We should make the change to the major / minor branches in addition to master.

┆Issue is synchronized with this Jira Story by Unito ┆Issue Number: CASS-35

burmanm commented 2 years ago

We should not remove Docker Hub, it will break everything. We can publish to additional ones, but not remove Docker Hub.

burmanm commented 2 years ago

PR #412 pushes to Github Repository also (ghcr.io)

burmanm commented 2 years ago

Though I have to say, I don't understand how people hit limitations with cass-operator pulls.

bradfordcp commented 2 years ago

FWIW I'm not looking to remove Docker Hub. I should make that more clear in the ticket. There will just be a new default. The PR I'm hacking on just adds the new location in addition to Docker Hub.