Added sample playbooks for AKS

[caohai]

Purpose

• Added sample playbooks for azure_rm_aks module
  • aks_create.yml: create an AKS cluster
  • aks_scale.yml: scale an existed AKS cluster by changing node count

Does this introduce a breaking change?

• [ ] Yes
• [x] No

Pull Request Type

What kind of change does this Pull Request introduce?

• [ ] Bugfix
• [x] Feature
• [ ] Code style update (formatting, local variables)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Documentation content changes
• [ ] Other... Please describe:

How to Test

• Install ansible

$ pip install ansible[azure]

• [Optional] Install ansible role

$ ansible-galaxy install Azure.azure_preview_modules
$ pip install -r ~/.ansible/roles/Azure.azure_preview_modules/files/requirements-azure.txt

• Get the sample playbook

git clone https://github.com/Azure-Samples/ansible-playbooks.git
cd ansible-playbooks
git checkout [branch-name]

• Test the code

  cd azure_rm_aks
  ansible-playbook aks_create.yml
  ansible-playbook aks_scale.yml

What to Check

Verify that the playbook is successfully run.

Other Information

[msftclas]

All CLA requirements met.

[kyliel]

How do you get resource group name? And don't list the complete SSH key in your sample.

[caohai]

@kyliel

• For resource group name, I'm following the convention of most sample playbooks in this repo.[Examples: vm_create_ssh] I'm not sure how resource group name is retrieved, @yuwzho can you give some explaination?
• I will remove the ssh key. Thought should include complete key like in vm_create_ssh

[kyliel]

vm_create_ssh should be fixed too.

[yuwzho]

@kyliel @caohai The resource group is passed to playbook dynamically when running the test.

And the SSH, I don't think this is a problem writing in the playbook, since the public key can only be used paired with secret one.

[caohai]

@yuwzho Should I add back ssh-key or just keep it as it is?

[yuwzho]

@caohai I m not sure whether the invalid SSH can successfully create an AKS, could you please have a try? Otherwise, you can store the key in env, and retrieve it in the playbook