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.

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

Automated backport of #3155: Fix SD error updating Openshift operator DNS instance #3156

Conversation

tpantelis
Copy link
Contributor

Backport of #3155 on release-0.14.

#3155: Fix SD error updating Openshift operator DNS instance

For details on the backport process, see the backport requests page.

This error was observed from the ServiceDiscovery controller:

"error updating Openshift DNS operator: no kind is registered
for the type v1.DNS in scheme
\"k8s.io/client-go/kubernetes/scheme/register.go:79\""

The Openshift operator types are added to the scheme used by the
controller manager but the GeneralClient needs to be set up with
the same scheme.

Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
@submariner-bot
Copy link
Contributor

🤖 Created branch: z_pr3156/tpantelis/automated-backport-of-#3155-upstream-release-0.14
🚀 Full E2E won't run until the "ready-to-test" label is applied. I will add it automatically once the PR has 2 approvals, or you can add it manually.

@submariner-bot submariner-bot added the ready-to-test When a PR is ready for full E2E testing label Jul 22, 2024
@tpantelis tpantelis merged commit 58af96b into submariner-io:release-0.14 Jul 22, 2024
42 of 47 checks passed
@submariner-bot
Copy link
Contributor

🤖 Closed branches: [z_pr3156/tpantelis/automated-backport-of-#3155-upstream-release-0.14]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated-backport ready-to-test When a PR is ready for full E2E testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants