Skip to content

Conversation

@eslutsky
Copy link
Contributor

No description provided.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 23, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 23, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@eslutsky eslutsky changed the title introduce microshift ingress performance enhancement USHIFT-4377: introduce microshift ingress performance enhancement Sep 23, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 23, 2024

@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.

Details

In 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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 23, 2024
@eslutsky eslutsky force-pushed the microshift-ingress-performance branch 3 times, most recently from 2b084b7 to 4b24145 Compare September 23, 2024 13:37
Copy link
Contributor

@ShaunaDiaz ShaunaDiaz left a 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!

**cluster admin** is a human user responsible for configuring a MicroShift
cluster.
1. The cluster admin adds specific configuration for the router prior to
Copy link
Contributor

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?

Copy link
Contributor Author

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
Copy link
Contributor

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
Copy link
Contributor

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?

@eslutsky eslutsky force-pushed the microshift-ingress-performance branch 16 times, most recently from cfccfa8 to bdf03cc Compare October 8, 2024 09:55
@eslutsky eslutsky marked this pull request as ready for review October 8, 2024 09:55
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 8, 2024
@eslutsky eslutsky force-pushed the microshift-ingress-performance branch from bdf03cc to 45f4583 Compare October 8, 2024 13:22
@eslutsky eslutsky force-pushed the microshift-ingress-performance branch from 45f4583 to 866d4d6 Compare October 8, 2024 14:06
@eslutsky
Copy link
Contributor Author

eslutsky commented Oct 9, 2024

/test markdownlint

@eslutsky eslutsky force-pushed the microshift-ingress-performance branch 2 times, most recently from 3f9ac05 to b4efa1f Compare October 10, 2024 13:19
@ShudiLi
Copy link
Member

ShudiLi commented Nov 4, 2024

lgtm, also did the compared test with the default-config.yaml file.

/label qe-approved
thanks

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Nov 4, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 4, 2024

@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.

Details

In 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.

@eslutsky eslutsky force-pushed the microshift-ingress-performance branch 2 times, most recently from 4ad95cf to 2ed1309 Compare November 4, 2024 13:55
@jerpeter1 jerpeter1 self-assigned this Nov 8, 2024
| 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 |
Copy link
Member

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

@jerpeter1
Copy link
Member

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?

@eslutsky
Copy link
Contributor Author

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>
@eslutsky eslutsky force-pushed the microshift-ingress-performance branch from 2ed1309 to 3c39fea Compare November 18, 2024 11:26
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 18, 2024

@eslutsky: 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-sigs/prow repository. I understand the commands that are listed here.

@jerpeter1
Copy link
Member

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 18, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 18, 2024

[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

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 the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 18, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 7accb68 into openshift:master Nov 18, 2024
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. 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. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants