Skip to content

add optional nodeSelector for VPA operator#2423

Merged
johannes94 merged 3 commits intomainfrom
jmalsam/fix-vpa-rosa-hcp
Sep 3, 2025
Merged

add optional nodeSelector for VPA operator#2423
johannes94 merged 3 commits intomainfrom
jmalsam/fix-vpa-rosa-hcp

Conversation

@johannes94
Copy link
Copy Markdown
Contributor

@johannes94 johannes94 commented Sep 3, 2025

Description

On ROSA HCP the default node selector for the VPA is not working because there are no master nodes. To fix that this PR adds an optional nodeSelector value for the subscription.

Checklist (Definition of Done)

  • Unit and integration tests added
  • Added test description under Test manual
  • Documentation added if necessary (i.e. changes to dev setup, test execution, ...)
  • CI and all relevant tests are passing
  • Add the ticket number to the PR title if available, i.e. ROX-12345: ...
  • Discussed security and business related topics privately. Will move any security and business related topics that arise to private communication channel.
  • Add secret to app-interface Vault or Secrets Manager if necessary
  • RDS changes were e2e tested manually
  • Check AWS limits are reasonable for changes provisioning new resources
  • (If applicable) Changes to the dp-terraform Helm values have been reflected in the addon on integration environment

Test manual

TODO: Add manual testing efforts

# To run tests locally run:
make db/teardown db/setup db/migrate
make ocm/setup
make verify lint binary test test/integration

@johannes94 johannes94 changed the title allow configuring node selector for VPA deployment add optional nodeSelector for VPA operator Sep 3, 2025
@johannes94 johannes94 requested a review from ludydoo September 3, 2025 08:43
node-role.kubernetes.io/acscs-infra: ""

verticalPodAutoscaler:
vertical-pod-autoscaler:
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.

Is the renaming from verticalPodAutoscaler to vertical-pod-autoscaler intentional?

Copy link
Copy Markdown
Contributor Author

@johannes94 johannes94 Sep 3, 2025

Choose a reason for hiding this comment

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

Yes, because otherwise the values won't get piped through properly to the subchart. That is because the subchart is named vertical-pod-autoscaler already

@johannes94
Copy link
Copy Markdown
Contributor Author

/retest

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Sep 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: johannes94, ludydoo

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

@johannes94 johannes94 merged commit 37a8580 into main Sep 3, 2025
15 checks passed
@johannes94 johannes94 deleted the jmalsam/fix-vpa-rosa-hcp branch September 3, 2025 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants