ImagePullError - Switch to DockerHub as Image Source

[yungxinkawaii]

Description:

We are currently encountering ImagePullBackOff when deploying images from the current image repository. This issue is affecting the deployment process and causing failures across multiple environments.

Steps to Reproduce:

1. Attempt to deploy the application using the current image repository (cr.fluentbit.io/fluent/fluent-bit).
2. Observe the failure and note the ImagePullBackOff in the logs.

Expected Behavior: The image should be successfully pulled and deployed without errors.
Actual Behavior: Deployment fails due to an ImagePullBackOff.

Error Logs:

Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  72s                default-scheduler  Successfully assigned fluentbit/fluent-bit-loki-5fm7j to k8s-rke2-w2
  Normal   BackOff    30s (x2 over 63s)  kubelet            Back-off pulling image "cr.fluentbit.io/fluent/fluent-bit:3.1.7"
  Warning  Failed     30s (x2 over 63s)  kubelet            Error: ImagePullBackOff
  Normal   Pulling    16s (x3 over 72s)  kubelet            Pulling image "cr.fluentbit.io/fluent/fluent-bit:3.1.7"
  Warning  Failed     9s (x3 over 64s)   kubelet            Failed to pull image "cr.fluentbit.io/fluent/fluent-bit:3.1.7": failed to pull and unpack image "cr.fluentbit.io/fluent/fluent-bit:3.1.7": failed to copy: httpReadSeeker: failed open: unexpected status code https://cr.fluentbit.io/v2/fluent/fluent-bit/manifests/sha256:a93d6119f67f804843f6d4d97dd8448389abed7e821e7513c5b8f387e57edfb9: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
  Warning  Failed     9s (x3 over 64s)   kubelet            Error: ErrImagePull

Suggested Resolution: To mitigate the issue, we should switch to using DockerHub as the image source. DockerHub is more reliable and can help avoid these errors. We can update the deployment configuration to pull images from DockerHub instead.