Skip to content

OCPBUGS-54225: Bump socks5 proxy, konnectivity proxy, http proxy, token minter memory requests #5897

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

Merged
merged 2 commits into from
Apr 16, 2025

Conversation

Evan-Reilly
Copy link
Contributor

@Evan-Reilly Evan-Reilly commented Mar 25, 2025

What this PR does / why we need it:

The steady-state memory utilization of socks5 proxy, konnectivity proxy, http proxy, and token minter containers is approximately ~30Mi. This PR bumps apiserver-token-minter, init-client-token-minter, client-token-minter, cloud-token-minter, token-minter, konnectivity-proxy, konnectivity-proxy-socks5, konnectivity-proxy-https, socks5-proxy, http-proxy container requests to 30Mi to reflect this usage. The total persistent (non-init container) memory increase per HCP is ~200Mi.

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 #

https://issues.redhat.com/browse/OCPBUGS-54225

Checklist

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

Sorry, something went wrong.

@openshift-ci openshift-ci bot requested review from csrwng and enxebre March 25, 2025 18:06
@openshift-ci openshift-ci bot added area/control-plane-operator Indicates the PR includes changes for the control plane operator - in an OCP release area/hypershift-operator Indicates the PR includes changes for the hypershift operator and API - outside an OCP release needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. and removed do-not-merge/needs-area labels Mar 25, 2025
Copy link
Contributor

openshift-ci bot commented Mar 25, 2025

Hi @Evan-Reilly. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@Evan-Reilly Evan-Reilly changed the title Bump socks5-proxy, konnectivity-proxy, http-proxy, client-token-minter memory requests OCPBUGS-54225: Bump socks5-proxy, konnectivity-proxy, http-proxy, client-token-minter memory requests Mar 25, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Mar 25, 2025
@openshift-ci-robot
Copy link

@Evan-Reilly: This pull request references Jira Issue OCPBUGS-54225, 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.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

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

In response to this:

What this PR does / why we need it:

The steady-state memory utilization of socks5-proxy, konnectivity-proxy, http-proxy, and client-token-minter containers is approximately ~30Mi. Bump memory requests to reflect Given this usage.

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 openshift-eng/jira-lifecycle-plugin repository.

Sorry, something went wrong.

@openshift-ci-robot
Copy link

@Evan-Reilly: This pull request references Jira Issue OCPBUGS-54225, which is valid.

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

In response to this:

What this PR does / why we need it:

The steady-state memory utilization of socks5-proxy, konnectivity-proxy, http-proxy, and client-token-minter containers is approximately ~30Mi. Bump memory requests to reflect this usage.

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 openshift-eng/jira-lifecycle-plugin repository.

Sorry, something went wrong.

@Evan-Reilly Evan-Reilly force-pushed the bump-container-memory branch from f8c821c to 6410ee0 Compare March 25, 2025 18:27
Copy link
Contributor

@rtheis rtheis left a comment

Choose a reason for hiding this comment

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

@Evan-Reilly please rebase to pick up #5876 since there is another container to update.

@rtheis
Copy link
Contributor

rtheis commented Mar 26, 2025

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Mar 26, 2025
@rtheis
Copy link
Contributor

rtheis commented Mar 26, 2025

@Evan-Reilly please investigate the test failures.

@Evan-Reilly
Copy link
Contributor Author

Each of these seems to fail with the following.

ERRO[2025-03-26T12:48:55Z] Some steps failed:                           
ERRO[2025-03-26T12:48:55Z] 
  * could not run steps: step hypershift-operator failed: error occurred handling build hypershift-operator-amd64: the build hypershift-operator-amd64 failed after 2m29s with reason DockerBuildFailed: Dockerfile build strategy has failed. 

However, I attempted a make docker-build locally and it built successfully, so I'm not quite sure yet what I'm missing here.

@rtheis
Copy link
Contributor

rtheis commented Mar 27, 2025

/retest

2 similar comments
@rtheis
Copy link
Contributor

rtheis commented Mar 27, 2025

/retest

@rtheis
Copy link
Contributor

rtheis commented Mar 28, 2025

/retest

Copy link
Contributor

@rtheis rtheis left a comment

Choose a reason for hiding this comment

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

@Evan-Reilly there appears to be a lot more changes needed functionally and to test data. The v2 code path also needs to be updated. Please search for 10Mi and change everything applicable to these containers.

@rtheis
Copy link
Contributor

rtheis commented Apr 1, 2025

/retest-required

@rtheis
Copy link
Contributor

rtheis commented Apr 3, 2025

/ok-to-test

@Evan-Reilly Evan-Reilly force-pushed the bump-container-memory branch from f6f556c to b6b8ae6 Compare April 7, 2025 13:51
@rtheis
Copy link
Contributor

rtheis commented Apr 11, 2025

/ok-to-test

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6efaf27 and 2 for PR HEAD ba89ff5 in total

@rtheis
Copy link
Contributor

rtheis commented Apr 11, 2025

/retest

1 similar comment
@rtheis
Copy link
Contributor

rtheis commented Apr 11, 2025

/retest

@rtheis
Copy link
Contributor

rtheis commented Apr 12, 2025

/retest-required

@rtheis
Copy link
Contributor

rtheis commented Apr 12, 2025

/retest

2 similar comments
@rtheis
Copy link
Contributor

rtheis commented Apr 13, 2025

/retest

@Evan-Reilly
Copy link
Contributor Author

/retest

@bryan-cox
Copy link
Member

/override "Red Hat Konflux / hypershift-operator-main-on-pull-request"

@bryan-cox
Copy link
Member

/override "Red Hat Konflux / hypershift-operator-main-enterprise-contract / hypershift-operator-main"

Copy link
Contributor

openshift-ci bot commented Apr 14, 2025

@bryan-cox: Overrode contexts on behalf of bryan-cox: Red Hat Konflux / hypershift-operator-main-on-pull-request

In response to this:

/override "Red Hat Konflux / hypershift-operator-main-on-pull-request"

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.

Copy link
Contributor

openshift-ci bot commented Apr 14, 2025

@bryan-cox: Overrode contexts on behalf of bryan-cox: Red Hat Konflux / hypershift-operator-main-enterprise-contract / hypershift-operator-main

In response to this:

/override "Red Hat Konflux / hypershift-operator-main-enterprise-contract / hypershift-operator-main"

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.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6c62eaa and 2 for PR HEAD ba89ff5 in total

@bryan-cox
Copy link
Member

/retest

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD c99fd69 and 1 for PR HEAD ba89ff5 in total

@rtheis
Copy link
Contributor

rtheis commented Apr 15, 2025

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD e513976 and 2 for PR HEAD ba89ff5 in total

@rtheis
Copy link
Contributor

rtheis commented Apr 15, 2025

/retest

1 similar comment
@rtheis
Copy link
Contributor

rtheis commented Apr 16, 2025

/retest

Copy link
Contributor

@rtheis rtheis left a comment

Choose a reason for hiding this comment

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

/lgtm

Copy link
Contributor

openshift-ci bot commented Apr 16, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Evan-Reilly, rtheis, sjenning

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

The pull request process is described here

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

/retest-required

Remaining retests: 0 against base HEAD e513976 and 2 for PR HEAD ba89ff5 in total

Copy link
Contributor

openshift-ci bot commented Apr 16, 2025

@Evan-Reilly: all tests passed!

Full PR test history. Your PR dashboard.

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.

@openshift-merge-bot openshift-merge-bot bot merged commit cddcc2f into openshift:main Apr 16, 2025
16 of 18 checks passed
@openshift-ci-robot
Copy link

@Evan-Reilly: Jira Issue OCPBUGS-54225: All pull requests linked via external trackers have merged:

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

In response to this:

What this PR does / why we need it:

The steady-state memory utilization of socks5 proxy, konnectivity proxy, http proxy, and token minter containers is approximately ~30Mi. This PR bumps apiserver-token-minter, init-client-token-minter, client-token-minter, cloud-token-minter, token-minter, konnectivity-proxy, konnectivity-proxy-socks5, konnectivity-proxy-https, socks5-proxy, http-proxy container requests to 30Mi to reflect this usage. The total persistent (non-init container) memory increase per HCP is ~200Mi.

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 #

https://issues.redhat.com/browse/OCPBUGS-54225

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 openshift-eng/jira-lifecycle-plugin repository.

Sorry, something went wrong.

@openshift-cherrypick-robot

@openshift-ci-robot: #5897 failed to apply on top of branch "release-4.18":

Applying: Bump socks5 proxy, konnectivity proxy, http proxy, token minter memory requests
Using index info to reconstruct a base tree...
M	control-plane-operator/controllers/hostedcontrolplane/cno/clusternetworkoperator.go
M	control-plane-operator/controllers/hostedcontrolplane/ingressoperator/ingressoperator.go
M	control-plane-operator/controllers/hostedcontrolplane/kas/kms/aws.go
M	control-plane-operator/controllers/hostedcontrolplane/oapi/deployment.go
M	control-plane-operator/controllers/hostedcontrolplane/oapi/oauth_deployment.go
M	control-plane-operator/controllers/hostedcontrolplane/oauth/params.go
M	control-plane-operator/controllers/hostedcontrolplane/olm/operator.go
M	control-plane-operator/controllers/hostedcontrolplane/olm/packageserver.go
M	control-plane-operator/controllers/hostedcontrolplane/registryoperator/reconcile.go
A	control-plane-operator/controllers/hostedcontrolplane/v2/assets/cluster-network-operator/deployment.yaml
M	control-plane-operator/controllers/hostedcontrolplane/v2/kas/kms/aws.go
M	hypershift-operator/controllers/hostedcluster/hostedcluster_controller.go
M	hypershift-operator/controllers/hostedcluster/internal/platform/aws/aws.go
A	karpenter-operator/controllers/karpenter/manifests.go
A	karpenter-operator/manifests/operator.go
M	support/controlplane-component/konnectivity-container.go
A	support/controlplane-component/token-minter-container.go
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): support/controlplane-component/token-minter-container.go deleted in HEAD and modified in Bump socks5 proxy, konnectivity proxy, http proxy, token minter memory requests. Version Bump socks5 proxy, konnectivity proxy, http proxy, token minter memory requests of support/controlplane-component/token-minter-container.go left in tree.
Auto-merging support/controlplane-component/konnectivity-container.go
CONFLICT (modify/delete): karpenter-operator/manifests/operator.go deleted in HEAD and modified in Bump socks5 proxy, konnectivity proxy, http proxy, token minter memory requests. Version Bump socks5 proxy, konnectivity proxy, http proxy, token minter memory requests of karpenter-operator/manifests/operator.go left in tree.
CONFLICT (modify/delete): karpenter-operator/controllers/karpenter/manifests.go deleted in HEAD and modified in Bump socks5 proxy, konnectivity proxy, http proxy, token minter memory requests. Version Bump socks5 proxy, konnectivity proxy, http proxy, token minter memory requests of karpenter-operator/controllers/karpenter/manifests.go left in tree.
Auto-merging hypershift-operator/controllers/hostedcluster/internal/platform/aws/aws.go
Auto-merging hypershift-operator/controllers/hostedcluster/hostedcluster_controller.go
Auto-merging control-plane-operator/controllers/hostedcontrolplane/v2/kas/kms/aws.go
Auto-merging control-plane-operator/controllers/hostedcontrolplane/registryoperator/reconcile.go
Auto-merging control-plane-operator/controllers/hostedcontrolplane/olm/packageserver.go
Auto-merging control-plane-operator/controllers/hostedcontrolplane/olm/operator.go
Auto-merging control-plane-operator/controllers/hostedcontrolplane/oauth/params.go
Auto-merging control-plane-operator/controllers/hostedcontrolplane/oapi/oauth_deployment.go
Auto-merging control-plane-operator/controllers/hostedcontrolplane/oapi/deployment.go
Auto-merging control-plane-operator/controllers/hostedcontrolplane/kas/kms/aws.go
Auto-merging control-plane-operator/controllers/hostedcontrolplane/ingressoperator/ingressoperator.go
Auto-merging control-plane-operator/controllers/hostedcontrolplane/cno/testdata/zz_fixture_TestReconcileDeployment_Private_apiserver_connectivity__proxy_apiserver_address_is_unset.yaml
Auto-merging control-plane-operator/controllers/hostedcontrolplane/cno/clusternetworkoperator.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Bump socks5 proxy, konnectivity proxy, http proxy, token minter memory requests

In response to this:

@bryan-cox: The following backport issues have been created:

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.18

In response to this:

/jira backport release-4.18

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.

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.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: hypershift
This PR has been included in build ose-hypershift-container-v4.19.0-202504160650.p0.gcddcc2f.assembly.stream.el9.
All builds following this will include this PR.

@rtheis
Copy link
Contributor

rtheis commented Apr 16, 2025

@Evan-Reilly please manually cherry-pick your fix to 4.18.

@Evan-Reilly
Copy link
Contributor Author

Manual cherry-pick PR created here: #6052

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 area/hypershift-operator Indicates the PR includes changes for the hypershift operator and API - outside an OCP release jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. 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. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants