-
Notifications
You must be signed in to change notification settings - Fork 533
USHIFT-4377: introduce microshift ingress performance enhancement #1685
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
USHIFT-4377: introduce microshift ingress performance enhancement #1685
Conversation
|
Skipping CI for Draft Pull Request. |
|
@eslutsky: This pull request references USHIFT-4377 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
2b084b7 to
4b24145
Compare
ShaunaDiaz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some Qs from the docs side, thank you!
enhancements/microshift/microshift-router-configuration-performance.md
Outdated
Show resolved
Hide resolved
| **cluster admin** is a human user responsible for configuring a MicroShift | ||
| cluster. | ||
| 1. The cluster admin adds specific configuration for the router prior to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this an immutable configuration?
Can the user set it day 1 or day 2 after they've started MicroShift?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes,its router runtime configuration it can be changed on day 2.
| ## Graduation Criteria | ||
| Targeting GA for MicroShift 4.18 release. | ||
| ### Dev Preview -> Tech Preview |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we targeting Tech Preview in 4.18, or Dev?
| ### Removing a deprecated feature | ||
| N/A | ||
| ## Upgrade / Downgrade Strategy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these only for minor-version updates/downgrades? What about z-stream updates?
cfccfa8 to
bdf03cc
Compare
bdf03cc to
45f4583
Compare
45f4583 to
866d4d6
Compare
|
/test markdownlint |
enhancements/microshift/microshift-router-configuration-performance.md
Outdated
Show resolved
Hide resolved
enhancements/microshift/microshift-router-configuration-performance.md
Outdated
Show resolved
Hide resolved
3f9ac05 to
b4efa1f
Compare
|
lgtm, also did the compared test with the default-config.yaml file. /label qe-approved |
|
@eslutsky: This pull request references USHIFT-4377 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
4ad95cf to
2ed1309
Compare
| | new configuration | description | default | | ||
| | ------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | | ||
| | ingress.httpCompressionMimeTypes | list of MIME types that should have compression applied. <br>At least one MIME type must be specified.<br> | none | | ||
| | ingress.forwardedHeaderPolicy | specify when and how the Ingress Controller sets the `Forwarded`, `X-Forwarded-For`, `X-Forwarded-Host`, `X-Forwarded-Port`, `X-Forwarded-Proto`, and `X-Forwarded-Proto-Version` HTTP headers. | append | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if it matters, but "Append" is capitalized (like "Log", and "Respond"), in the PR for this EP
|
Given that we're just enabling the configuration options available in openshift, this suggestion might be directed to the upstream docs, but I think the docs should probably describe what reasonable values are for ingress configuration options, what effects they'll have on e.g. memory footprint and connection interruptions, etc - I think it might be worth considering putting guardrails on these values depending on what comes out during testing - WDYT? |
yes, its something we can in the future, default configuration should provide the best ingress performance/pod memory consumption balance. |
Signed-off-by: Evgeny Slutsky <eslutsky@redhat.com>
2ed1309 to
3c39fea
Compare
|
@eslutsky: 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-sigs/prow repository. I understand the commands that are listed here. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jerpeter1 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 |
No description provided.