Skip to content

OCPBUGS-23466: Let router use svc ips - #3218

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
enxebre:let-router-use-svc-ips
Nov 22, 2023
Merged

OCPBUGS-23466: Let router use svc ips#3218
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
enxebre:let-router-use-svc-ips

Conversation

@enxebre

@enxebre enxebre commented Nov 21, 2023

Copy link
Copy Markdown
Member

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #

Checklist

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 21, 2023
@openshift-ci-robot

Copy link
Copy Markdown

@enxebre: This pull request references Jira Issue OCPBUGS-23466, which is invalid:

  • expected the bug to target the "4.15.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #

Checklist

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

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.

@openshift-ci openshift-ci Bot added the area/control-plane-operator Indicates the PR includes changes for the control plane operator - in an OCP release label Nov 21, 2023
@openshift-ci

openshift-ci Bot commented Nov 21, 2023

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: enxebre

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci Bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed do-not-merge/needs-area labels Nov 21, 2023
@enxebre

enxebre commented Nov 21, 2023

Copy link
Copy Markdown
Member Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Nov 21, 2023
@openshift-ci-robot

Copy link
Copy Markdown

@enxebre: This pull request references Jira Issue OCPBUGS-23466, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.0) matches configured target version for branch (4.15.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (jiezhao@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

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.

@netlify

netlify Bot commented Nov 21, 2023

Copy link
Copy Markdown

Deploy Preview for hypershift-docs ready!

Name Link
🔨 Latest commit e4efc2f
🔍 Latest deploy log https://app.netlify.com/sites/hypershift-docs/deploys/655cf4a5471cb3000840d074
😎 Deploy Preview https://deploy-preview-3218--hypershift-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@enxebre
enxebre force-pushed the let-router-use-svc-ips branch from e4efc2f to 1b2fa99 Compare November 21, 2023 18:33

@csrwng csrwng left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, some comments, but generally lgtm

mode http
monitor-uri /haproxy_ready

resolvers coredns

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

delete this section

{{range .Backends }}
backend {{ .Name }}
server {{ .Name }} {{ .DestinationService }}.{{ $ns }}.svc.cluster.local:{{.DestinationPort}} check resolvers coredns init-addr last,libc,none
server {{ .Name }} {{ .DestinationServiceIP }}:{{.DestinationPort}} check resolvers coredns init-addr last,libc,none

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/resolvers coredns init-addr last,libc,none//

{{- if .HasKubeAPI }}
backend kube_api
server kube_api kube-apiserver.{{ $ns }}.svc.cluster.local:{{ .KASSVCPort }} check resolvers coredns init-addr last,libc,none
server kube_api {{ .KASDestinationServiceIP }}:{{ .KASSVCPort }} check resolvers coredns init-addr last,libc,none

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/resolvers coredns init-addr last,libc,none//

func (r byRouteName) Less(i, j int) bool { return r[i].Name < r[j].Name }

func generateRouterConfig(namespace string, routeList *routev1.RouteList, nameServerIP string) (string, error) {
func generateRouterConfig(routeList *routev1.RouteList, nameServerIP string, svcsNameToIP map[string]string) (string, error) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nameServerIP is no longer needed

@enxebre
enxebre force-pushed the let-router-use-svc-ips branch from 1b2fa99 to 1fae69c Compare November 21, 2023 19:57
@enxebre
enxebre force-pushed the let-router-use-svc-ips branch from 1fae69c to c185421 Compare November 21, 2023 19:58
@csrwng

csrwng commented Nov 21, 2023

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Nov 21, 2023
@openshift-ci-robot

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 4413eb8 and 2 for PR HEAD c185421 in total

@openshift-ci-robot

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD b1d19f7 and 1 for PR HEAD c185421 in total

@openshift-ci

openshift-ci Bot commented Nov 22, 2023

Copy link
Copy Markdown
Contributor

@enxebre: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@openshift-merge-bot
openshift-merge-bot Bot merged commit 27d0f8f into openshift:main Nov 22, 2023
@openshift-ci-robot

Copy link
Copy Markdown

@enxebre: Jira Issue OCPBUGS-23466: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-23466 has been moved to the MODIFIED state.

Details

In response to this:

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #

Checklist

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

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.

@enxebre

enxebre commented Nov 22, 2023

Copy link
Copy Markdown
Member Author

/cherrypick release-4.14

@openshift-cherrypick-robot

Copy link
Copy Markdown

@enxebre: #3218 failed to apply on top of branch "release-4.14":

Applying: Let router use svc ips
Using index info to reconstruct a base tree...
M	control-plane-operator/controllers/hostedcontrolplane/hostedcontrolplane_controller.go
M	control-plane-operator/controllers/hostedcontrolplane/hostedcontrolplane_controller_test.go
M	control-plane-operator/controllers/hostedcontrolplane/ingress/router.go
M	control-plane-operator/controllers/hostedcontrolplane/ingress/router_config.template
M	control-plane-operator/controllers/hostedcontrolplane/ingress/router_test.go
M	control-plane-operator/main.go
Falling back to patching base and 3-way merge...
Removing support/util/resolver_test.go
Removing support/util/resolver.go
Auto-merging control-plane-operator/main.go
Auto-merging control-plane-operator/controllers/hostedcontrolplane/ingress/router_test.go
CONFLICT (content): Merge conflict in control-plane-operator/controllers/hostedcontrolplane/ingress/router_test.go
Auto-merging control-plane-operator/controllers/hostedcontrolplane/ingress/router_config.template
CONFLICT (content): Merge conflict in control-plane-operator/controllers/hostedcontrolplane/ingress/router_config.template
Auto-merging control-plane-operator/controllers/hostedcontrolplane/ingress/router.go
CONFLICT (content): Merge conflict in control-plane-operator/controllers/hostedcontrolplane/ingress/router.go
Auto-merging control-plane-operator/controllers/hostedcontrolplane/hostedcontrolplane_controller_test.go
CONFLICT (content): Merge conflict in control-plane-operator/controllers/hostedcontrolplane/hostedcontrolplane_controller_test.go
Auto-merging control-plane-operator/controllers/hostedcontrolplane/hostedcontrolplane_controller.go
CONFLICT (content): Merge conflict in control-plane-operator/controllers/hostedcontrolplane/hostedcontrolplane_controller.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Let router use svc ips
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Details

In response to this:

/cherry-pick release-4.14

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.

@openshift-bot

Copy link
Copy Markdown

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-hypershift-container-v4.15.0-202311221354.p0.g27d0f8f.assembly.stream for distgit hypershift.
All builds following this will include this PR.

@openshift-merge-robot

Copy link
Copy Markdown
Contributor

Fix included in accepted release 4.14.0-0.nightly-2023-11-23-154014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/control-plane-operator Indicates the PR includes changes for the control plane operator - in an OCP release jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants