Automated cherry pick of #121015: Add nil checks for hpa object target type values

[Lukasz-AWS]

Cherry pick of #121015 on release-1.26.

#121015: Add nil checks for hpa object target type values

For details on the cherry pick process, see the cherry pick requests page.

What type of PR is this?

/kind bug

What this PR does / why we need it:

The change to 1.26 is so the 1.26 controller is resilient to data it could encounter speaking to a 1.27 server #121015 (comment)

Fixes a bug where if the corresponding value (value, averageValue) of the the type of target (Value, AverageValue) is not set but the opposite type is, HPA object would pass validation but then cause kube-controller-manager to crash loop due to nil pointer dereference looking for that corresponding value. This PR adds a nil check to make sure kube-controller-manager doesn't crash. The change to fix the validation is being worked on here #120373

Which issue(s) this PR fixes:

N/A
Fixes #

Special notes for your reviewer:

Observed in 1.27 and 1.28. Cherry-picked to 1.26 so the 1.26 controller is resilient to data it could encounter speaking to a 1.27 server

Does this PR introduce a user-facing change?

NONE

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

[k8s-ci-robot]

Hi @Lukasz-AWS. 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/test-infra repository.

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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/test-infra repository.

[Lukasz-AWS]

/kind bug

[liggitt]

/ok-to-test
/lgtm
/approve
/cc @kubernetes/release-managers

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 788fd976b13fde20e24f4cacfebb05d54dd66db5

[Lukasz-AWS]

/retest

[Lukasz-AWS]

/retest

[saschagrunert]

/retest

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liggitt, Lukasz-AWS, saschagrunert

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:

• pkg/controller/podautoscaler/OWNERS [liggitt]

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

[saschagrunert]

/retest

[k8s-ci-robot]

@Lukasz-AWS: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubernetes-e2e-autoscaling-hpa-cpu	060f508	link	false	/test pull-kubernetes-e2e-autoscaling-hpa-cpu

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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/test-infra repository. I understand the commands that are listed here.

[pacoxu]

/retest