Skip to content
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

4. Adding Support For VPA and Auto Mode in CreateExperiment [KRUIZE-VPA Integration] #1415

Merged
merged 3 commits into from
Dec 13, 2024

Conversation

shekhar316
Copy link
Contributor

Description

This PR adds auto and recreate modes required for VPA in createExperiment for Local Monitoring.

Type of change

  • Bug fix
  • New feature
  • Docs update
  • Breaking change (What changes might users need to make in their application due to this PR?)
  • Requires DB changes

How has this been tested?

Tested on both the ResourceHub cluster.

Test Configuration

Kubernetes clusters tested on: ResourceHub (OpenShift)

Checklist 🎯

  • Followed coding guidelines
  • Comments added
  • Dependent changes merged
  • Documentation updated
  • Tests added or updated

Signed-off-by: Shekhar Saxena <[email protected]>
@shekhar316 shekhar316 added this to the Kruize 0.3 Release milestone Dec 9, 2024
@shekhar316 shekhar316 requested a review from dinogun December 9, 2024 19:50
@shekhar316 shekhar316 self-assigned this Dec 9, 2024
@shekhar316 shekhar316 changed the title 4. Adding Support For VPA and Auto Mode in CreateExperiment [KRUIZE-VPA Integration] 4. [Testing - In Progress] Adding Support For VPA and Auto Mode in CreateExperiment [KRUIZE-VPA Integration] Dec 10, 2024
@shekhar316 shekhar316 changed the title 4. [Testing - In Progress] Adding Support For VPA and Auto Mode in CreateExperiment [KRUIZE-VPA Integration] 4. Adding Support For VPA and Auto Mode in CreateExperiment [KRUIZE-VPA Integration] Dec 10, 2024
Copy link
Member

@bharathappali bharathappali left a comment

Choose a reason for hiding this comment

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

LGTM

Comment on lines 46 to 49
} else if (kruizeObject.getMode().equalsIgnoreCase(AnalyzerConstants.RECREATE)) {
setLocal_monitoring(true);
} else if (kruizeObject.getMode().equalsIgnoreCase(AnalyzerConstants.AUTO)) {
setLocal_monitoring(true);
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe a switch case would be more appropriate here

Signed-off-by: Shekhar Saxena <[email protected]>
Comment on lines 51 to 52
case AnalyzerConstants.RECREATE:
case AnalyzerConstants.AUTO:
Copy link
Contributor

Choose a reason for hiding this comment

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

Please combine this with MONITOR as currently they are all the same

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure dino! I have updated the code to use switch case block and combined the RECREATE and AUTO cases with the MONITOR case.

Signed-off-by: Shekhar Saxena <[email protected]>
@dinogun
Copy link
Contributor

dinogun commented Dec 13, 2024

auto and recreate are not monitor modes technically so we need to change this but that requires a design discussion. We can do this as a short term solution for testing VPA. Longer term these two modes have to have their own separate category.

Copy link
Contributor

@dinogun dinogun left a comment

Choose a reason for hiding this comment

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

LGTM for VPA alpha support

@dinogun dinogun merged commit 69abe0b into kruize:mvp_demo Dec 13, 2024
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants