Use quay images for cilium

[olemarkus]

a) again I got a request for this over docker rate limiting
b) Since with containerd, docker credentials are not valid for image pulls outside of kubelet, docker.io images will hit rate limiting
c) upstream use quay by default

cilium with hubble already has a dependency on cert-manager, which is hosted on quay so quay is to some extent a dependency anyway.

[hakman]

@olemarkus Any thoughts about doing this the same way we do for Calico?
372fde0

[olemarkus]

Was considered and decided against: #10204

[hakman]

Was considered and decided against: #10204

I guess we can revisit that. The decision was in the context of us doing an API change soon.
Generic string replace in image urls could be a solution, but I don't see anyone interested in doing that.
Docker to Quay will generate the same amount of requests the other way around when Quay goes down.

[johngmyers]

Upstream default is a powerful argument.

For kOps 1.22, local image registries will be a lot easier to manage.

[johngmyers]

/lgtm

[hakman]

Upstream default is a powerful argument.

I agree.

For kOps 1.22, local image registries will be a lot easier to manage.

Still harder than setting the image version or registry.

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [hakman]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment