Fix typos in the metric name for VPA In-Place update

[toVersus]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

I was looking over a recently merged #8115 and found a few typos in the metric names.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

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

[AEP] https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler/enhancements/4016-in-place-updates-support
Depends on: 
[KEP] https://github.com/kubernetes/enhancements/tree/25e53c93e4730146e4ae2f22d0599124d52d02e7/keps/sig-node/1287-in-place-update-pod-resources

[k8s-ci-robot]

Welcome @toVersus!

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

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.

[toVersus]

/cc @maxcao13 @raywainman @omerap12

[raywainman]

/ok-to-test

/lgtm

[adrianmoisey]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adrianmoisey, toVersus

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:

• vertical-pod-autoscaler/OWNERS [adrianmoisey]

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

[maxcao13]

I know this was merged already, but can someone explain the typo?

[adrianmoisey]

It's changing the upper case "u" in Updatable to lower case.
I don't know if Prometheus cares, but it seems out of place to have a single upper case character in the metric name, and in a name of something that is normally all lower case.

[maxcao13]

It's changing the upper case "u" in Updatable to lower case.
I don't know if Prometheus cares, but it seems out of place to have a single upper case character in the metric name, and in a name of something that is normally all lower case.

Ohh, I see. For some reason, I thought it was changing from lowercase to uppercase and that's why I got confused 😄. Thanks!

[adrianmoisey]

Haha, I was very nervous when you were asking, making me wonder if we missed something that you did intentionally