[release-4.12] OCPBUGS-15251: Add protocolStrategy for upstreams in dnses.operator.openshift.io#1502
Conversation
…enshift.io protocolStrategy adds the ability to configure the force_tcp CoreDNS Corefile configuration for upstreams, which forces TCP for all upstream DNS requests. This is to resolve issues regarding problematic DNS upstreams as well as a potential UDP reliability problems.
|
@openshift-cherrypick-robot: Jira Issue OCPBUGS-6829 has been cloned as Jira Issue OCPBUGS-15251. Will retitle bug to link to clone. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Hello @openshift-cherrypick-robot! Some important instructions when contributing to openshift/api: |
|
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-15251, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/jira refresh |
|
@gcs278: This pull request references Jira Issue OCPBUGS-15251, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/jira refresh |
|
@gcs278: This pull request references Jira Issue OCPBUGS-15251, which is invalid:
Comment DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Slack Discussion about backporting |
|
/assign |
|
@gcs278 can you investigate the |
|
@candita will look into it. |
|
Backport looks correct, and justification for backport from Slack thread has been approved by team lead, PM, and manager. |
|
@gcs278 you'll need to check in to the verify-client-go failure. It may be that this can't be backported to 4.12 after all.
|
|
I spent sometime investigating, but it doesn't look like it's a failure that is specific to this PR, but more of a repo-level code generation issue. I asked forum-api-review here: https://redhat-internal.slack.com/archives/CE4L0F143/p1687540934599509 |
|
@gcs278 can you follow up on the slack thread regarding verify-client-go? |
|
/jira refresh |
|
@melvinjoseph86: This pull request references Jira Issue OCPBUGS-15251, which is valid. The bug has been moved to the POST state. 6 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/test verify-client-go |
|
I've filed OCPBUGS-16720 for the verify-client-go failures. |
|
/test verify-client-go |
|
@openshift-cherrypick-robot: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
@JoelSpeed thanks for following up with the Could I get you to apply approve and backport-risk-assessed to this PR? |
|
Do we have staff eng approval for backporting this? Typically backporting features into z streams has strict requirements, especially for going back a couple of releases |
@JoelSpeed I was slightly mistaken. For the 4.13 backport, @soltysh approved it, looks like he is on vacation though. PM has approved it in this Slack Thread. |
soltysh
left a comment
There was a problem hiding this comment.
/approve
/label backport-risk-assessed
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: candita, openshift-cherrypick-robot, soltysh The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/label cherry-pick-approved |
|
@melvinjoseph86: Can not set label cherry-pick-approved: Must be member in one of these teams: [openshift-staff-engineers] DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@gangwgr @wangke19 @xingxingxia Kindly help adding cherry-pick-approved label |
Friendly reminder |
|
/label cherry-pick-approved |
|
@openshift-cherrypick-robot: Jira Issue OCPBUGS-15251: Some pull requests linked via external trackers have merged: The following pull requests linked via external trackers have not merged: These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with Jira Issue OCPBUGS-15251 has not been moved to the MODIFIED state. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Fix included in accepted release 4.12.0-0.nightly-2023-09-08-181253 |
This is an automated cherry-pick of #1429
/assign gcs278