CA: add artifacts for dev testing of cluster-autoscaler on AKS

[charliedmcb]

What type of PR is this?

/kind documentation

What this PR does / why we need it:

This PR adds the required artifacts, and documentation for testing of cluster-autoscaler changes within a dev environment on an AKS cluster.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

While this is mostly meant to support the https://github.com/Azure/autoscaler repo dev environment, I think this is valuable to have upstream in the https://github.com/kubernetes/autoscaler repo for others to see the process for testing in a dev environment, and can be leveraged as a base for setting up ones own tests.

Testing:

• For testing, I setup a codespace within azure/autoscaler, transferred to the main branch of this repo, and then used the artifacts to setup a running instance of autoscaler on the aks cluster in my codespace.
• Same steps as I've documented in the README

Does this PR introduce a user-facing change?

NONE

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

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: charliedmcb / name: Charlie McBride (6a28f58, 225dcfa, 2d79167, 15d77b0)

[k8s-ci-robot]

Welcome @charliedmcb!

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

[Shubham82]

Hi @charliedmcb
you have to sign the CLA before the PR can be reviewed.
See the following document to sign the CLA: Signing Contributor License Agreements(CLA)

[Shubham82]

To check EasyCLA

/easycla

[rakechill]

lgtm

[charliedmcb]

Hi @charliedmcb you have to sign the CLA before the PR can be reviewed. See the following document to sign the CLA: Signing Contributor License Agreements(CLA)

Thanks! I have completed the CLA.

[charliedmcb]

/easycla

[comtalyst]

/ok-to-test

[comtalyst]

/easycla

[comtalyst]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: charliedmcb, comtalyst, rakechill

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 [comtalyst]

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