Shulou(Shulou.com)05/31 Report--

This article shows you how KEDA migrates the container image to the GitHub container registry, which is concise and easy to understand, which will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

We provide a variety of ways to deploy KEDA [1] in your cluster, including using Helm chart [2], Operator Hub [3], and the original YAML specification.

These deployment options depend on the container image we provided on Docker Hub [4], and Docker Hub is the industry standard for public container images.

However, we found that Docker Hub is no longer the best place for our container image and is migrating to the GitHub container registry (preview).

Why make such a change? Docker Hub is introducing rate limiting and mirror retention

In the past few years, Docker Hub has become the industry standard for hosting public container images. This has become a major burden for Docker to manage all traffic and has decided to make some changes by 2020:

Anonymous mirrors pulling unused images that are rate-limited will no longer be retained

Because we want to make sure that our end users can use KEDA without any problems, we want anyone to use them without any restrictions.

For more information, see Docker's FAQ [5] and our questions on GitHub [6].

Gain insight into the adoption of KEDA

As maintainers, we find it difficult to measure KEDA adoption to see how many end users are using older versions of KEDA and how they have grown over time.

Docker Hub provides a vague image of the total pull count for each container, but it does not provide in-depth details about the label and the growth of the pull count over time.

However, in the GitHub container registry, each tag provides out-of-the-box metrics, which allows us to better understand what customers are using and make better decisions when we no longer support a given version.

Bring our products closer to home

Finally, we want to bring our products closer to home on GitHub. By making more use of the GitHub ecosystem, we believe that this integration will only improve and integrate more closely with our version.

What changes have been made?

Our container image is being published on the GitHub container registry [7] for end users to pull.

Because of this, the name of our container image is changing:

When does the new component image (GitHub container registry) and the old image (Docker Hub) Metrics Serverghcr.io/kedacore/keda-metrics-apiserverkedacore/keda-metrics-apiserverOperatorghcr.io/kedacore/kedakedacore/keda take effect?

Starting with v2.2, we have started publishing new container images to the GitHub container registry in parallel on Docker Hub.

This allows customers to immediately migrate to our new registry and use our artifacts there.

Once GitHub's container registry becomes generally available (GA), we will no longer release new versions in Docker Hub.

What is the impact on the end user?

If you are using one of our deployment options, the end user will not be affected.

Since v2.2, we use the GitHub container registry by default, so you can rest assured that you can use it.

If you use your own deployment mechanism, you will have to extract the container image from the GitHub container registry.

The above is how KEDA migrates the container image to the GitHub container registry. Have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.