Skip to content

CFE-651: Release notes for AWS Load Balancer Operator#52292

Merged
snarayan-redhat merged 1 commit intoopenshift:enterprise-4.12from
xenolinux:ingress-CFE-616
Nov 23, 2022
Merged

CFE-651: Release notes for AWS Load Balancer Operator#52292
snarayan-redhat merged 1 commit intoopenshift:enterprise-4.12from
xenolinux:ingress-CFE-616

Conversation

@xenolinux
Copy link
Contributor

@xenolinux xenolinux commented Oct 31, 2022

This PR adds the information about sorting the ingress rules and setting the `EnableIPTargetType` flag to false.

Version(s): 4.12

Issue: https://issues.redhat.com/browse/CFE-651

Link to docs preview: https://52292--docspreview.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-12-release-notes.html#ocp-4-12-nw-aws-load-balancer-operator

QE review:

  • QE has approved this change.

Additional information:

@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 31, 2022
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Oct 31, 2022

🤖 Updated build preview is available at:
https://52292--docspreview.netlify.app

Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/4012

@xenolinux xenolinux changed the title CFE-616: Sort Ingress rules based on the strategy CFE-636: Sort Ingress rules based on the strategy Oct 31, 2022
Copy link

Choose a reason for hiding this comment

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

This needs the under AWS Load Balancer Operator (new section)

Copy link

Choose a reason for hiding this comment

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

Similar to the ExternalDNS section

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Addressed

Copy link

Choose a reason for hiding this comment

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

Suggested change
In {product-title} 4.12, the Ingress Controller now implements the Kubernetes ingress specification for multiple matches. If multiple paths within an Ingress match a request then, the longest matching path gets the precedence. If two paths still match, paths with an exact path type over a prefix path type gets the precedence.
In {product-title} 4.12, the AWS Load Balancer controller now implements the Kubernetes ingress specification for multiple matches. If multiple paths within an Ingress match a request then, the longest matching path gets the precedence. If two paths still match, paths with an exact path type over a prefix path type gets the precedence.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Addressed

@xenolinux xenolinux force-pushed the ingress-CFE-616 branch 2 times, most recently from 3e119f9 to f7bbe46 Compare October 31, 2022 14:16
@xenolinux xenolinux changed the title CFE-636: Sort Ingress rules based on the strategy CFE-651: Sort Ingress rules based on the strategy Oct 31, 2022
@xenolinux
Copy link
Contributor Author

/label peer-review-needed

@openshift-ci openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Oct 31, 2022
@bergerhoffer
Copy link
Contributor

/label peer-review-in-progress

@openshift-ci openshift-ci bot added the peer-review-in-progress Signifies that the peer review team is reviewing this PR label Oct 31, 2022
@bergerhoffer bergerhoffer added this to the Planned for 4.12 GA milestone Oct 31, 2022
Copy link
Contributor

@bergerhoffer bergerhoffer left a comment

Choose a reason for hiding this comment

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

Just a few suggestions!

Copy link
Contributor

Choose a reason for hiding this comment

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

  • Should "ingress" be capitalized in the first sentence?
  • The phrase "gets the precedence" sounds odd to me. I think saying "takes precedence" is a more common phrase, so that's what I'd recommend (two places in this line).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Addressed

@bergerhoffer
Copy link
Contributor

/label peer-review-done
/remove-label peer-review-needed
/remove-label peer-review-in-progress

@openshift-ci openshift-ci bot added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Oct 31, 2022
@xenolinux
Copy link
Contributor Author

/label merge-review-needed

@openshift-ci openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Nov 1, 2022
@xenolinux
Copy link
Contributor Author

/remove-label merge-review-needed

@openshift-ci openshift-ci bot removed the merge-review-needed Signifies that the merge review team needs to review this PR label Nov 1, 2022
@xenolinux xenolinux force-pushed the ingress-CFE-616 branch 2 times, most recently from 8bf3781 to 2ecb1c8 Compare November 14, 2022 08:03
@xenolinux xenolinux changed the title CFE-651: Sort Ingress rules based on the strategy CFE-651: Release notes for AWS Load Balancer Operator Nov 14, 2022
@xenolinux
Copy link
Contributor Author

@lihongan Would you please review this PR?

@lihongan
Copy link

It looks good. Thank you @xenolinux

Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
The AWS Load Balancer Operator sets the `EnableIPTargetType` flag to `false`. The AWS Load Balancer controller disables the support for services and ingress resources for `target-type` and `ip`.
The AWS Load Balancer Operator sets the `EnableIPTargetType` feature gate to `false`. The AWS Load Balancer controller disables the support for services and ingress resources for `target-type` `ip`.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Addressed

@alebedev87
Copy link
Contributor

@xenolinux : Forgot to mention. The upstream version will be updated to 2.4.4 (openshift/aws-load-balancer-operator#79), this is worth mentioning in the release notes.

Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
In {product-title} 4.12, the AWS Load Balancer controller now implements the Kubernetes Ingress specification for multiple matches. If multiple paths within an Ingress match a request, the longest matching path takes the precedence. If two paths still match, paths with an exact path type over a prefix path type takes the precedence.
In {product-title} 4.12, the AWS Load Balancer controller now implements the Kubernetes Ingress specification for multiple matches. If multiple paths within an Ingress match a request, the longest matching path takes the precedence. If two paths still match, paths with an exact path type take precedence over a prefix path type.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Addressed

@alebedev87
Copy link
Contributor

/lgtm

@xenolinux xenolinux added the merge-review-needed Signifies that the merge review team needs to review this PR label Nov 23, 2022
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 23, 2022
@snarayan-redhat snarayan-redhat added the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Nov 23, 2022
@snarayan-redhat snarayan-redhat merged commit 3c91226 into openshift:enterprise-4.12 Nov 23, 2022
@snarayan-redhat snarayan-redhat removed merge-review-in-progress Signifies that the merge review team is reviewing this PR merge-review-needed Signifies that the merge review team needs to review this PR labels Nov 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.12 lgtm Indicates that a PR is ready to be merged. peer-review-done Signifies that the peer review team has reviewed this PR size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants