[cluster-autoscaler-release-1.30] backport Azure e2e tests

[nojnhuh]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

This PR backports the Azure e2e tests added by #6969 and related PRs to the master branch.

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.:

[nojnhuh]

/hold testing this will require some test-infra changes

[nojnhuh]

kubernetes/test-infra#33361 will enable the job to run (correctly) here. Let's merge that before this one so we can iterate here if needed.

[nojnhuh]

/test ?

[k8s-ci-robot]

@nojnhuh: The following commands are available to trigger optional jobs:

• /test pull-cluster-autoscaler-e2e-azure-1-30
• /test pull-kubernetes-e2e-autoscaling-vpa-full

Use /test all to run the following jobs that were automatically triggered:

• pull-cluster-autoscaler-e2e-azure-1-30

In response to this:

/test ?

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.

[nojnhuh]

/test pull-cluster-autoscaler-e2e-azure-1-30

[nojnhuh]

e2e job passed.
/hold cancel

@tallaxes Do you know the recommended way to fix the dependency error the unit test job is throwing? Based on this it looks like the release branches of cluster-autoscaler may not be fully module-aware:

git diff upstream/cluster-autoscaler-release-1.30 upstream/master -- hack/for-go-proj.sh

diff --git a/hack/for-go-proj.sh b/hack/for-go-proj.sh
index ec55ef23d..f44f997c4 100755
--- a/hack/for-go-proj.sh
+++ b/hack/for-go-proj.sh
@@ -19,7 +19,7 @@ set -o pipefail
 set -o nounset

 CONTRIB_ROOT="$(dirname ${BASH_SOURCE})/.."
-PROJECT_NAMES=(addon-resizer cluster-autoscaler vertical-pod-autoscaler)
+PROJECT_NAMES=(addon-resizer vertical-pod-autoscaler)

 if [[ $# -ne 1 ]]; then
   echo "missing subcommand: [build|install|test]"
@@ -43,12 +43,7 @@ esac

 for project_name in ${PROJECT_NAMES[*]}; do
   (
-    if [[ $project_name == cluster-autoscaler ]];then
-      export GO111MODULE=off
-    else
-      export GO111MODULE=auto
-    fi
-
+    export GO111MODULE=auto
     project=${CONTRIB_ROOT}/${project_name}
     echo "${CMD}ing ${project}"
     cd "${project}"
@@ -68,6 +63,10 @@ for project_name in ${PROJECT_NAMES[*]}; do
 done;

 if [ "${CMD}" = "build" ] || [ "${CMD}" == "test" ]; then
-  cd ${CONTRIB_ROOT}/vertical-pod-autoscaler/e2e
+  pushd ${CONTRIB_ROOT}/vertical-pod-autoscaler/e2e
   go test -mod vendor -run=None ./...
+  popd
+  pushd ${CONTRIB_ROOT}/cluster-autoscaler/
+  go test ./...
+  popd
 fi

[nojnhuh]

/hold for squash

[nojnhuh]

CI checks are passing now and I cleaned up the history here.

/hold cancel

[nojnhuh]

/cherry-pick cluster-autoscaler-release-1.29
/cherry-pick cluster-autoscaler-release-1.28
/cherry-pick cluster-autoscaler-release-1.27

[k8s-infra-cherrypick-robot]

@nojnhuh: once the present PR merges, I will cherry-pick it on top of cluster-autoscaler-release-1.29 in a new PR and assign it to you.

In response to this:

/cherry-pick cluster-autoscaler-release-1.29
/cherry-pick cluster-autoscaler-release-1.28
/cherry-pick cluster-autoscaler-release-1.27

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.

[k8s-ci-robot]

@nojnhuh: 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-cluster-autoscaler-e2e-azure	08108e3	link	false	/test pull-cluster-autoscaler-e2e-azure

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

[Bryce-Soghigian]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Bryce-Soghigian, nojnhuh, rakechill, tallaxes

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:

• cluster-autoscaler/cloudprovider/azure/OWNERS [Bryce-Soghigian,tallaxes]

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

[k8s-infra-cherrypick-robot]

@nojnhuh: new pull request created: #7245

In response to this:

/cherry-pick cluster-autoscaler-release-1.29
/cherry-pick cluster-autoscaler-release-1.28
/cherry-pick cluster-autoscaler-release-1.27

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.

[k8s-infra-cherrypick-robot]

@nojnhuh: new pull request created: #7246

In response to this:

/cherry-pick cluster-autoscaler-release-1.29
/cherry-pick cluster-autoscaler-release-1.28
/cherry-pick cluster-autoscaler-release-1.27

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.

[k8s-infra-cherrypick-robot]

@nojnhuh: new pull request created: #7247

In response to this:

/cherry-pick cluster-autoscaler-release-1.29
/cherry-pick cluster-autoscaler-release-1.28
/cherry-pick cluster-autoscaler-release-1.27

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.