chore: add recommender vpa-object-namespace quick integration test

[phuhung273]

What type of PR is this?

/kind feature

What this PR does / why we need it:

• Quick integration test for recommender flags: vpa-object-namespace, ignored-vpa-object-namespaces

Which issue(s) this PR fixes:

Fixes #7699
Relates #7723

Special notes for your reviewer:

This PR doesn't include:

• A unified way to cleanup resources between tests. Right now each test script handle its resource deployment + cleanup
• Cleanup on failure
• Option to skip cleanup

I left some TODOs in the script

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: phuhung273
Once this PR has been reviewed and has the lgtm label, please assign raywainman for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• vertical-pod-autoscaler/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @phuhung273!

It looks like this is your first PR to kubernetes/autoscaler 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/autoscaler has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @phuhung273. Thanks for your PR.

I'm waiting for a kubernetes 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.

[adrianmoisey]

/ok-to-test

[omerap12]

Thanks for this PR! I have a few comments, though I haven’t tested it yet.

Could you create a directory under hack to store everything?
For example: autoscaler/vertical-pod-autoscaler/hack/integration-tests.

Once that's done, we can work on integrating it into our CI.

[omerap12]

I tested it, and it looks good! There is still more work to do, but that can be done later. This PR helps a lot with test coverage and makes it easier to add more tests in the future so overall I like it - thanks!
@adrianmoisey, can you take a look too?
Also, I think we should write this down somewhere so contributors know how to add tests easily.

[omerap12]

/remove-kind feature
/kind cleanup

[adrianmoisey]

I like the idea of having the quick tests, or, a way to execute a subset of e2e tests for taster feedback. What concerns me is that these tests use shell scripts, rather than ginkgo, to execute.
I'm not a big fan of having multiple ways of running e2e tests.
This also adds a bunch of duplication, since there are now extra YAML and shell files to maintain