Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

openshift operator hup failed because pods can not reach registry.redhat.io because of dns resolving #29444

Open
ahmedharb01 opened this issue Jan 16, 2025 · 0 comments
Open

openshift operator hup failed because pods can not reach registry.redhat.io because of dns resolving #29444

ahmedharb01 opened this issue Jan 16, 2025 · 0 comments

Comments

@ahmedharb01
Copy link

hello folks,
i have the issue blew because my cluster is an air gaped and i enable cluster wide proxy to install some operators from operator hup
how to fix the dns resolving.
the following error from pod events
Failed to pull image "registry.redhat.io/odf4/ocs-metrics-exporter-rhel9@sha256:14c75bac0e6cc0a2b39816614501452e39e3eb49ccc65af3437462546a312499": pinging container registry registry.redhat.io: Get "https://registry.redhat.io/v2/": dial tcp: lookup registry.redhat.io on 192.168.137.102:53: server misbehaving
@ahmedharb01 ahmedharb01 changed the title openshift operator hup failed because can not reach registry.io because of dns resolving openshift operator hup failed because pods can not reach registry.redhat.io because of dns resolving Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ahmedharb01